Products

Solutions

Resources

Partners

Community

About

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 PacksA guide to using and configuring localizationA guide to using and configuring localization
Previous
 
Next
New Post
12/7/2006 5:01 PM
 

OK, sorry - this isn't one.

But I'd really like to have one -  the current documentation is way out of date and, maybe I'm missing something, but there have been some major changes to the way localization works and I can't seem to find any references to them.

Are the globalization settings in config still required?

Do I need both Locales.xml and locales.xml.config and ditto for the portals files?

Are the portal local files just for exclusion of languages?

How do times work nowadays - this was always a real drag trying to get a system time (different to hosting servers) - I'd run a few tests myself if I knew what was meant to happen.

My apologies if this is all out there and I've goofed on my searches . but if there is an idiots guide could somebody point me at it.

Pleeeease.

 
New Post
12/8/2006 3:53 AM
 
you do not need to edit locales.xml manually, it is managed by the framework using locales.xml.config. Portal files are for enabling/disabling languages and managed by the framework as well. Globalization setting in web.config is still used.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
12/8/2006 8:08 AM
 

leupold wrote
you do not need to edit locales.xml manually, it is managed by the framework using locales.xml.config.

If you look at my previous post then, perhaps not the right way, but the only way I managed to get it to work was to delete the US setting in locales (I think there was another poster that came up with the solution).  How can you set a fallback language from the framework?

What is the impact on changing the default culture in web.config - do the culture and UI culture settings have an impact or are they overidden by the locales settings always?

 
New Post
12/8/2006 8:14 AM
 


Michael Washington
http://ADefWebserver.com
www.ADefHelpDesk.com
A Free Open Source DotNetNuke Help Desk Module
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsLanguage PacksLanguage PacksA guide to using and configuring localizationA guide to using and configuring localization


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