Creating a custom culture

Ozgur Ozguven asked on September 4, 2015 13:02

Hi folks

I want to create new custom culture, something like 'English - International'. In the Localisation app via Admin UI, the 'New culture' form enforces the CultureCode to be a supported Microsoft.NET culture. So, I can't do what I want to do there.

I then tried cloning an existing culture and this way I managed to create my new custom culture, English - International (en-INT). Is this OK / supported? Will it get lost on future upgrades or updates?

If someone can please clarify.. Many thanks.


Recent Answers

Brenden Kehren answered on September 4, 2015 13:55

It will not get lost in upgrades. The reason it forces you to do it with a valid code is because browsers are dependent on it. There are other reasons, I'm sure but I'm not fully aware of them all.

0 votesVote for this answer Mark as a Correct answer

Lukas Martinak answered on September 5, 2015 18:17

I would definitely recommend using only valid .net cultures as it can be used as a thread's culture, as a source for formatting date/time values or comparison with browser/windows regional settings.

Why would you want to use any non-standard culture? What's the story behind and the ultimate goal here?

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.