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 PacksResx file encoding and DNN robustnessResx file encoding and DNN robustness
Previous
 
Next
New Post
11/14/2006 7:21 AM
 

I deal with the following regularly: when distributing modules, the resource files are normally UTF-8 encoded and this is specified in the declaration. Then people edit stuff and save and send me files and I edit them and save and etc etc. In short: the file passes through numerous systems and accidentally is no longer UTF-8 encoded. This is not noticable to the naked eye as most editors load these text-based files as is, and save them. The main problem, though, is that DNN invariably breaks as dotnet cannot read an xml file that specifies UTF-8 encoding in the declaration and is not really thus encoded. You get a nice unhelpful message saying Object reference not set to an instance of an object. at DotNetNuke.Services.Localization.Localization.LoadResource etc etc. The reason that it can go unnoticed by me, the developer, is that I don't load in all locales for every page before it leaves the lab. I rely on outside sources to deliver the resx files and this sometimes leads to this issue.

Proposal:

1. Make DNN localization a little more robust. It should not bomb out when dotnet can't read the resx file. It should gracefully retreat to our beloved us-EN localization as it would if the resx file wasn't there.

2. A repair tool. This would check all resource files for any anomalies including the one I mentioned and propose fixes.

Whaddaya think?

Peter


Peter Donker
Bring2mind http://www.bring2mind.net
Home of the Document Exchange,
the professional document management solution for DNN
 
New Post
11/14/2006 7:31 AM
 

Peter,

ad 1. agree

ad 2. there is already the resource file verifier, it should list files with issues (from my experience, if there are issues with a file, it needs manual attention, therfore I am not sure, if auto-repair would be possible).

Please tell people not to use an external text editor to localize your modules, but DNN's built in language editor. this will ensure, that only valid keys are contained and preserve the correct file format.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsLanguage PacksLanguage PacksResx file encoding and DNN robustnessResx file encoding and DNN robustness


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