Custom Languages

[nquandt]

Similar to #14736

Say I have a site that needs to support the French language in most countries. but the products sold in the countries vary by included details. In the cms I'd like to have a single tree site structure, and define the supported regions and translation on each node. Given the current tight coupling of language to ICU CultureInfo, the language/region pairings are restricted to those supported by ICU (CLDR).

ICU/CLDR is not meant for defining business language/region pairs, but for UTF-8 translations for data serialization given a sort of (dialect) of a language (typically in a specific region, though CLDR is a tree where language is fallback). So supporting a region would most likely choose to utilize an existing utf8 culture.

Could it make sense to allow for defining a language by a "locale" name (or some other term) and a providing CultureInfo (given that CultureInfo is for UTF8 globalization but not necessarily business level region/language goals)? This code would also act as a deliminator in routing.

e.g.

fr-US -> CultureInfo("fr") -> .com/fr-US/mypage
fr-MX -> CultureInfo("fr")-> .com/fr-MX/mypage

OR (if my assumption is that most US French speakers are more likely utilizing Canadian standards

fr-US -> CultureInfo("fr-CA") -> .com/fr-US/mypage

Umbraco-CMS/src/Umbraco.Web.BackOffice/Controllers/LanguageController.cs

Line 119 in 62bc748

ModelState.AddModelError("IsoCode", "The language " + language.IsoCode + " already exists");

Mock ->

[nquandt]

There is already a thread for this I realize