fusion locale file (split by widget)

[poulet1212]

Right about now, the localization in fusion is done in these directory (json and php), for example: fusion\text\en That mean all localized strings are put there. When developing a widget in Fusion, the only way to achieve localization, is to modify those files, what is not so fine.

Wouldn't it be nice to have a structure like this, for example a folder: -org.osgeo.mapguide.[widget name] -> Localized Strings for [widget] would be there.

and so on for all widgets and future extensions? We would have this way independent files for different components.

[chrisclaydon]

If you write your own widget, you should be able to control where the strings come from. So you shouldn't be tied to using the same file as the main Fusion components.

In the file fusion.js, Fusion adds its own set of strings into the OpenLayers i18n handling as follows:

OpenLayers.Util.extend(OpenLayers.Lang[this.locale], Fusion.Strings[this.locale]);

I haven't tried it, but an individual widget should be able to make a similar call to add its own set of strings, if it is going to use the OpenLayers localization methods.

[poulet1212]

thank you Chris for the answer. I didn't knew that, I'll try this for my widget and then let you know. Through this ticket I was wondering if it wasn't better that all widget access their own locale file, for a scalability purpose.

[jbirch]

This would be more likely to get attention in the Fusion Trac instance: ​http://trac.osgeo.org/fusion/ or on the fusion mailing lists...

[jbirch]

Closing due to lack of follow-up. Re-open if still a concern or, better yet, take up on the Fusion mailing list.