Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 310 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Foreign language characters in US HTML not rendered properly in NAV2016
rsaritzky
Member Posts: 469
Hi all,
We have built an email engine that takes templates stored in HTML and uses the NAV SMTP codeunit (CU400) to build and send emails to customers. We have a large number of Spanish-speaking customers and send out emails written in Spanish.
The HTML templates are built by our marketing and accounting department users, using Microsoft Word and saving the templates as HTML.
I am having a problem with foreign language characters such as "accented" characters or the n with a "tilde" over the letter (I don't know how to type these characters in this forum message, so I've attached a file with an example.)
For example, instead of an an accented "o", the email message (or printout) will print an upper case "A" with a tilde over it followed by a 2 spaces. So the word "cordon" appears as "cordA n".
In NAV2009, the emails send and print with the proper rendering of the special characters - this is happening only in NAV2016.
So far, my only solution has been to bring up the HTML file in a text-based HTML editor and replace all accented "o" characters with the HTML equivalent of "ó". This of course is very cumbersome.
I haven't been able to find an HTML "WYSIWIG" editor that will allow me to make these changes easily - I have tried BlueGriffon, Kompozer and TinyMCE - they all have the issue of as soon as you open a file that has the HTML codes for foreign characters, it will replace those HTML codes with the character equivalents.
Has anyone had to deal with this issue in NAV2013-2016? Any solutions?
A document is attached with a more detailed example.
Thx
Ron
We have built an email engine that takes templates stored in HTML and uses the NAV SMTP codeunit (CU400) to build and send emails to customers. We have a large number of Spanish-speaking customers and send out emails written in Spanish.
The HTML templates are built by our marketing and accounting department users, using Microsoft Word and saving the templates as HTML.
I am having a problem with foreign language characters such as "accented" characters or the n with a "tilde" over the letter (I don't know how to type these characters in this forum message, so I've attached a file with an example.)
For example, instead of an an accented "o", the email message (or printout) will print an upper case "A" with a tilde over it followed by a 2 spaces. So the word "cordon" appears as "cordA n".
In NAV2009, the emails send and print with the proper rendering of the special characters - this is happening only in NAV2016.
So far, my only solution has been to bring up the HTML file in a text-based HTML editor and replace all accented "o" characters with the HTML equivalent of "ó". This of course is very cumbersome.
I haven't been able to find an HTML "WYSIWIG" editor that will allow me to make these changes easily - I have tried BlueGriffon, Kompozer and TinyMCE - they all have the issue of as soon as you open a file that has the HTML codes for foreign characters, it will replace those HTML codes with the character equivalents.
Has anyone had to deal with this issue in NAV2013-2016? Any solutions?
A document is attached with a more detailed example.
Thx
Ron
Ron
0
Answers
There is proberly a conversion happening somewhere, that is not needed anymore or need to be changed.
Writing you HTML through a .Net stream writer allows you to encode as you please.