Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsLanguage PacksLanguage Packslowercase vs. uppercaselowercase vs. uppercase
Previous
 
Next
New Post
9/12/2005 5:57 PM
 

In looking at the localization page, it seems consistent that the language abbreviation is lowercase, and the country abbreviation is uppercase.  But when the name of the language is spelled out, there seems to be an inconsistency.  For example, for Spanish, es-ES is described as español, but for es-MX and es-UY it is Español.  For Portuguese, pt-PT is português and pt-BR is Português.

Is there some specific convention that should be observed?  Is this convention part of the original language pack?  Or is it built into DNN?  Will loading a language pack override any convention built into DNN?  For example, the locale "català (català)" is built into DNN even though there is currently no Catalan language pack available.  Will the lowercase convention it currently observes be overridden by any future Catalan language pack?

 

 
New Post
9/13/2005 2:46 AM
 

sjcmp,

I also observed this behaviour but this is something we cannot control. The list of available locales is generated by the .Net Platform, and it's the framework that returns that list of names in that strange mix of uppercase and lowercase. So either this is corrected in ASP.NET 2.0 or I don't have a good solution for it.

The fact the list has many more locales than available lang packs is a wrong question: the list will include all supported locales for the current framework. We don't have any idea of what lang packs are available nor will it be a good idea to limit to them (how would you create a new one then?).

 


Vicenç Masanas
Banyoles, Girona - Spain

Disgrafic.com    PSD to DNN
 
New Post
9/13/2005 11:52 AM
 

I wasn't asking why there are more locales than language packs.  I am surprised you interpreted that from my post.  My question was should the language packs conform to the naming convention provided by ASP.NET, and are any problems created when they do not?

 

 
New Post
9/13/2005 3:00 PM
 
sjcmp wrote

I wasn't asking why there are more locales than language packs.  I am surprised you interpreted that from my post. 

Well I take that interpretation for this sentence from your previous post:

sjcmp wrote
For example, the locale "català (català)" is built into DNN even though there is currently no Catalan language pack available.

 

Anyway, as I already said this is not built into DNN but just a list of asp.net supported locales.

sjcmp wrote

My question was should the language packs conform to the naming convention provided by ASP.NET, and are any problems created when they do not?

 

I not sure I follow you here. The fact is DNN is using asp.net naming convention for the list of locales, that's way "català" looks this way. This is actually returned from a call to (localization.vb line 997):

 Dim info As CultureInfo = CultureInfo.CreateSpecificCulture(...)

and then using info.NativeName as the text.


Vicenç Masanas
Banyoles, Girona - Spain

Disgrafic.com    PSD to DNN
 
New Post
9/13/2005 4:35 PM
 

My purpose for the statement

For example, the locale "català (català)" is built into DNN even though there is currently no Catalan language pack available.

was to determine if the uploading of a language pack changed the nomenclature of the entry in the locale.  Since there was no Catalan language pack, the appearance of that locale in the list would not be influenced by any installed pack.  The question was whether something exists in the language pack that would be able to control how those entries appeared in the locale list.  Your implication is that they do not.

I finally did the obvious thing and looked at a clean install of 3.1.1 and saw that the same lowercase vs. uppercase discrepancies existed without having any language packs installed (in my previous statements I was using my main web site as my reference which has several  language packs installed).  So the next question is, why is ASP.NET inconsistent in how it displays the variations of the same language (such as using uppercase Português for pt-BR and lowercase português for pt-PT)?  French, English, and German are consistent in their cases, but Spanish and Portugese are not.

 

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsLanguage PacksLanguage Packslowercase vs. uppercaselowercase vs. uppercase


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out