In fact, I would like to create a worlwide site with 2 distincts ways for navigate :

1) the country
2) the language

I already have more than 200 different language contents / ressources. For the first step, I will use about 80 languages. (part of ISO 639 2/3).
If I'm not wrong, the CultureInfo Class provide only 62 distincts languages.

So, I cannot make  :   80 languages * 90 country = 7200 localisations  and  I have to realize a separate country navigation with no direct link to contents.

 For future evolution on localization, it will be great to have a ressource file wich can be modified and freely add specific language like 'breton:bre', 'corsican', 'occitan' , 'Basque' ( French example).

=> What will be the better way to modify DNN ?
=> Can the DNN Framework accept empty country : [en]-    or  [bre]-   instead of  [en]-[US] ?

Thx a lot !

Richard

Are you sure, AFAIK the procedure also checks whether any locale starting with "de" is available (from memory, i'd have to check the code to verify)

DNN Blog | Twitter: @erikvb | LinkedIn:

Hi,

This issue is still a problem for global / worlwide localization :

1) the contents or datas for a worlwide site don't need to be localized with locale (10 for 'en-XX', 19 for 'es-XX') but only need to be localized with neutral culture ('en', 'es', 'fr', 'de').

2) The Microsoft culture has 62 neutrals cultures instead of 188 languages in ISO Code. For example, the corsican people (beautiful french island) will be interessed to write and read content in their language ('co')

I've just tried to put a neutral language in the locales.xml file, but this is provide an error :

DotNetNuke.Services.Exceptions.PageLoadException: Culture 'fr' is a neutral culture. It cannot be used in formatting and parsing and therefore cannot be set as the thread's current culture. --->

How can we do that in DNN, is there any enhancement since the last posts to take care of it ?
I suggest to create

Thx a lot again

Richard