[ckan-dev] Translation issues

[Sean Hammond]

> 1) Translating on the fly
>
> We allow people to edit text such as the about page - this should be
> translated or at least have a version for each language - this is
> already broken if ckan.site_about config is used.  Where would be the
> place to keep this? How would it be accessed - maybe we just have a
> different version that can be administered when the language is selected
> - this would be fairly easy as far as the system config is concerned.
>
> 2) Translating Field Titles
>
> In resource view page we have additional fields these should be
> translated - some we know some are user defined - We probably want the
> know ones translated as normal but how about the custom ones? - This
> feels it would need a custom system to administer

The multilingual extension in core could be extended to translate these 
fields, it currently translates things like dataset and group titles and 
other metadata fields, tags, etc. Seems sensible at first glance.

I wonder if the multilingual extension could handle things like the 
about text as well.