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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Accentuated (accented) characters problemAccentuated (accented) characters problem
Previous
 
Next
New Post
4/7/2007 7:27 AM
 

Hi all, before all I wish you happy Easters :-) If somebody is stuck in work like me and solve strange coding problems, maybe he or she could help me :-) I can't say that my following question is an unsolveable problem, but if some solution exists, it will greatly improve my efficiency in DNN 4.x module developmnet.

We are developing DNN 4/ASP.NET 2.0 modules in Czech language. The problem is following: if I use some accented characters in some control at module frontend - ascx file, or in module code (*.vb), DotNetNuke will remove them at runtime. For example, if I set "Text" property of Label control (in Visual Studio 2005 Pro at design time) to eg. "Přihlášen:", after adding this module to some DNN pane, at runtime text control label becomes "Pihláen:", DNN removes characters ř and š. Of course, I can use Localization.GetString function to get correct translated text, but using Localization.GetString function for each control (labels, validators, grid column labels etc.) brings a lot coding... I don't want to have this module localised to another language, it will be always czech.

Yes, I use UTF-8 encoding and yes, ascx modules used outside DNN (not inherited from DotNetNuke.Entities.Modules.PortalModuleBase) works normaly - doesn't strip accented charas.

Does somebody have simillar problem? Thank you very much for solution.

 
New Post
4/8/2007 4:27 AM
 

This is not a DNN problem, but an encoding one. I've seen this behaviour a lot in VS.NET. Make sure your file incoding (VS.NET -> File menu -> Save As... -> Save with Encoding...) is correct.

Also you don't have to use Localization.GetString() for all the labels, this is just necessary for messages set in code. On you ascx you would normaly use "resourcekey=" and point to a resource entry in the resource file.


Vicenç Masanas
Banyoles, Girona - Spain

Disgrafic.com    PSD to DNN
 
New Post
4/8/2007 7:07 AM
 

Thank you very much! I found with big surprise that I had set encoding to Windows-1250

How to quickly present self as lama :-))

Thank you again :-)

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Accentuated (accented) characters problemAccentuated (accented) characters problem


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