I was not clear enough. By localizable I want the Editor to be able to edit them. Not with the language files.

Punch the question up!

Don't you have any guess how to achive that? It's rather out of the box in our customers previous CMS.

It don't have to be a category. It can be something custom that will display depending on a language selected. Are we waiting for somebody to write an property (plugin) like that?

Hi Krzysztof!

There is no support to localize any entities defined in the administrative interface so this needs to be done through the localization files. I know that there are plug-ins that makes it possible to edit the content of the language files inside of the administrative interface so perhaps this is an option for the customer?

@Linus

Thanks, can you maybe point me to any plugin?

Not sure if there are more than one out there but this seems to be one:

http://blog.mathiaskunto.com/2011/09/04/allowing-web-administrators-to-dynamically-update-episerver-language-files/

I just happen to have implemented this plugin today,.. took me 1 hour.

I put the LanguageFileEditor folder under <root>/Edit/Plugins.

Then i made sure all usages of LanguageManager.Instance.Directory are replaced (used for getting the folder where multilanguage files are, but is now obsolete). I changed it to something like this: string.Concat(HttpRuntime.AppDomainAppPath, "lang")

As last you need to check if all paths are set correctly. This is sometimes a bit tricky, what i did was check network in my browser for what files it tries to GET/POST and fix accordingly.

Good luck!