Hi all,

I have a question regarding custom locales.

I have noticed that it is possible to add custom locales to the 'Multilingual Locales' folder in the Data tab when you import a language resource. The process is to simply export the language resources and add a column with a new language code for the header. This does not need to be an existing locale and it seems that you can add any text that you like (as long as it follows the RFC 1766 standard). The result is that the custom locale shows up as an unknown language.

For example, if you add a new column with the header 'new' and import the resource the locale 'new - Unknown Language (new)' is added.

I have done some testing and it seems like the custom locale works the same as with a known locale. You can still use the SetCurrentLocale function and the translations occur as expected.

We have a use case where we need to be able to apply custom translations for different clients and I was wondering if this might be a good way of adding custom translations without changing the default translations. For example, we might offer an application in Spanish, but one of our clients require that certain phrases be translated differently from standard Spanish to apply to their business lingo.

My question is therefore, is there any reason to not use this functionality to add custom translations. Am I missing something where some browsers might not like it when you use an unknown locale.

Kind regards

Stefan