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

HomeHomeUsing DNN Platf...Using DNN Platf...Language and In...Language and In...Static localization does not workStatic localization does not work
Previous
 
Next
New Post
2/20/2011 1:45 PM
 
I use DNN 5.6.1 with the default language set to fr-CA and using en-US language packs. I have my localized pages set up in both language. This part seems to be working fine. 

I have a module that uses Static localization (localization.GetString("myString", localresourceFile)) with one instance on the fr-CA page and another one on the en-US page. The french instance appears in french (as expected) but the instance on the en-US page also appears in french. I have checked in the the page_load method of the module and confirmed that the current culture in the en-US page is properly set to en-US.


I have three resx files:
myFile.ascx.resx - In french
myFile.ascx.fr-CA.resx  - also in french
myFile.ascx.en-US.resx - in English.

What am I missing?

Jean Sylvain
 
New Post
2/20/2011 2:11 PM
Accepted Answer 
myfile.ascx.resx should be system language, which is always en-US by default you need to create myfile.ascx.fr-FR.resx (and myfile.ascx.fr-CA.resx) for your French translations

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
2/20/2011 5:19 PM
 
Thank you Sebastian. I wasn't aware of this behavior.

Jean
 
New Post
2/21/2011 2:06 PM
 
Made some additionnal tests and it seems that DNN will use the user's prefered culture to process modules using GetString for localization. Am I right? Such a behavior renders the language selector useless for registered users. Is there a way to overide this???

Jean
 
New Post
2/21/2011 3:29 PM
 
for authenticated user, UI language (which is implemented by static localization) is derived from preferred language in his profile, while for unauthenticated users it is synchronized with content language. You may use Advanced Control Panel from www.oliverhine.com to provide an UI option for setting UI language.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Language and In...Language and In...Static localization does not workStatic localization does not work


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