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 PacksGeneral observations about locales in .net and dotnetnukeGeneral observations about locales in .net and dotnetnuke
Previous
 
Next
New Post
10/13/2005 9:05 AM
 

Sorry, I've overread dash 4 of the Gemini item.

Sounds great!

 

Sebastian


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
10/13/2005 9:36 AM
 
vmasanas wrote

Erik, you should be really bored ...

Yeah i have that sometimes.... however, i needed this list for my language selector, in the next version the flags i provide will be locale specific instead of country specific, so a catalan flag will finally be possible.

vmasanas wrote

 vmasanas wrote
Answers:
- neutral locales: I think we definetely need to explore that option.

Ouch! It this really needed after latest changes in language detection? See http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=1996

Indeed you are right.. the original post was from before we came up with the new procedure though....

vmasanas wrote
- language names not correctly rendered: On my system I have a couple more not rendering correctly. I this due to the fact that the given culture's name cannot be displayed in the original native name of the culture in some systems depending on your SO configuration.

 http://msdn.microsoft.com/library/en-us/cpref/html/frlrfSystemGlobalizationCultureInfoClassNativeNameTopic.asp

The value of this property is the same, regardless of the language version of the .NET Framework.

The culture's full name might not display properly if the system is not set to display the culture's language correctly. For example, if the CultureInfo.Name is "ja-JP" for Japanese (Japan), CultureInfo.NativeName does not display correctly on a system that is set to English only. However, multilingual operating systems, such as Windows 2000, display NativeName correctly.

Hmm, that does not explain the fact that when i copy the list to excel (from the page source), all languages display fine. And the list in my original post also displays fine in my browser (its not an image). So there is nothing wrong with my system's capabilities of displaying foreign languages. What i meant is that in the dropdownlist some languages do not render correctly. Maybe thats a problem of the browser, maybe of the dropdownlist, maybe of my windows. Maybe there should at least be an option to change the way languages are displayed (for instance displayName instead of NativeName.

cheers,

Erik


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
11/8/2005 10:59 AM
 

On the topic of the dropdown list, my observation is this:  I need to have the language support from MS installed for those languages that do not appear correctly.  I think the choice was made to display the names of the culture-language in their 'Native' names, rather than the other option 'English' name.  Now, being a somewhat limited being, I've changed the dropdown list to actually display both.  I elongated the textbox width to accomodate it, but it works for me.  What would be useful is if these display formats had some kind of localization that allowed folks to display a combination of their prefferred language and native name.  That's not possible using the MS implemenation only, so it would have to be some additional code.  The trouble I had with using just the Native name in the display is that I really couldn't tell which one to pick - because I can't translate them.  Some of the languages that use script characters, as in Chinese, Arabic, and others were just impossible for me to understand.

Oh, well, that's just a short take. 

 
New Post
11/12/2005 5:56 PM
 

Phil, you're right on the fact that some names don't display well. I've always thought that if you can't se them well is because you don't have the appropiated languages support installed on the machine so this is actually not that of a problem. Even if you could see the name, trying to use it would cause you trouble.

If someone needs the Chinese language you can be sure he will be able to correctly read the name because he will have all the needed stuff on the machine to read it.

Have you tried to read that page http://www.microsoft.com/japan/ ? The same problem is here, and this is not an IE problem, but you don't having the correct support for the language. So I'm not that sure we should really bother by this issue anymore.

Providing a double list "Native name - English Name" doesn't seem very good to me, as you will see the same unreadable chars.


Vicenç Masanas
Banyoles, Girona - Spain

Disgrafic.com    PSD to DNN
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsLanguage PacksLanguage PacksGeneral observations about locales in .net and dotnetnukeGeneral observations about locales in .net and dotnetnuke


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