Read a UTF-8 encoded file with Stream automation and wrong Charset = IBM855įinally, I’ll let you download the objects and the files I used in the examples here. Read a UTF-8 encoded file with Stream automation and correct Charset = UTF-8 Read a IBM855 encoded file with Stream automation and correct Charset = IBM855 Read a IBM855 encoded file with Stream automation and wrong Charset = UTF-8 Read a UTF-8 encoded file with File variable Read a IBM855 encoded file with File variable To make sure that all the ASP.NET pages have utf-8 encoding for every embedded resources, you can add the following in your every ASP. Saving all resources files to utf-8 type should change the setting to utf-8. Finally, I test all on a NAV 2009 R2 Russian Native Demo Database.īelow some comments to understand the results: Code Check if any of the resource files could still be using VS encoding Windows 1252 for your JavaScript files. Then, I will use two Russian text files with different encoding: UTF-8 and IBM855 (OEM 855). In the example below, I will use a Russian Windows Server (change English to Russian):

Check that your OS supports the needed language,.

In fact, this Dll is available on every windows machine and it offers a an interesting object: Stream. The solution I personally prefer is to use “Microsoft ActiveX Data Objects 2.8 Library” automation.

Use some third party tools: but this will create dependency and it will cause a headache to maintain your NAV platform.

Ansi-Ascii converter: but you need to add new characters in the codeunit as they come up,.

In fact, when you google (bing) you will find two main answers: In order to import/export encoded files we usually use some workarounds. We all know that Microsoft Dynamics NAV 2009 R2 Classis Client supports ANSI only (code page 1252 or depends on your windows localization).

P.S: If you’re still using Microsoft Dynamics NAV 2009 R2 Classic Client or a previous version, then you may want to continue reading this blog post.

Sha1 to ascii text encoding windows