smithsson68@gmail.com
Optimizely
Aug 5, 2010
visibility 5262
star star star star star
(0 votes)

Using EPiServer CMS language files from Online Center Gadgets

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.

Aug 05, 2010

Comments

error Please login to comment.
Latest blogs
No name

Jagmeet Kaur | Nov 19, 2026 |

What the CMS 13 MCP Server Actually Does When You Write Properties

This post covers the setup gotchas, what each

Adnan Zameer | Nov 19, 2026 |

Pick images from Optimizely DAM straight into rich text

Rich text editors in Optimizely CMS (SaaS), and in CMS 13.7.0 on sites that use the Content Manager, have a new image button. It puts images from t...

Stuart Greig | Nov 18, 2026

Setting up the TinyMCE image picker, and DAM images in Graph and the CMS REST API

The new TinyMCE image and video pickers put images and video from the CMS and from Optimizely DAM straight into rich text, in Optimizely CMS (SaaS)...

Stuart Greig | Nov 18, 2026