|Number of votes:||0|
I’m currently working on a gadget who’s target audience is EPiServer CMS Editors. I thought therefore that it would probably be a good idea to make it internationalizable so editors can view the gadget in localized languages.
The obvious way to do this is to use the standard .NET resource model. However, as I only plan to ship the gadget with English and Swedish localization it became apparent that this was going to be a bit of a pain for others to provide a localization using a language of their choice.
Love it or hate it, this is where the EPiServer CMS model becomes really useful. All someone needs to do to localize to another language is find the correct sections in the site’s existing language files, copy them and change the text to the new language.
I decided to use the CMS XML language file model to internationalize my gadget. Maybe it’s really obvious to some people how you would go about doing this but I wasn’t so sure so I’ve written a code example which can be found here on the shiny new EPiServer World Code section.