Jump to content
Muxe Inc Forums
Sign in to follow this  
Crimso

Error In Encoding

Recommended Posts

Crimso    0

Symbol "No" (Number) in Windows encoding is on the wrong place. If you will open file xlt\test.txt in Notepad you will see this symbol on the 19 row, 27 character (code F9), but in the NDN it's on the 30 place (code FC).

I don't quite understand, how should I edit .xlt file to set it in the right place, please help me someone!

And second question: what .xlt file should I edit to replace standard Win-encoding in NDN (that which turning on by pressin F8 key, not by Ctrl-F8) ?

 

Thank you!

I used DN OSP before, and just recently discover for myself this version of DN. It is very interesting version, and I just happy that it still developing.

But this little mis-encoding is very unpleasant, as I often edit files with this symbol...

Share this post


Link to post
Share on other sites

Hello Crimso,

 

sorry for the late reply.

 

The problem with these symbols (characters > 127) is that every language can redefine them.

 

For example, I created a new XLT file for this release to be able to display the german windows

codepage correctly:

õä÷ö³ü▀ß─ÄÍÖ▄Ü

 

(Umlauts and ß)

 

I suspect the current implemented WIN codepage to be specifically for russian users,

or am I wrong? We should probably try to get a default WIN charset from the

operating system in the country setup.

 

The WIN codepage is fixed and built into NDN.

As long as I don't get the default table from the OS this problem remains for any user,

using a different codepage than russian.

 

Your only choice right now is to create your own .xlt file.

 

What country codepage are you using?

MAybe this is a bug in the russian implementation of the current WIN codepage.

 

Stefan / AH

Share this post


Link to post
Share on other sites
Crimso    0

Hello Stefan!

 

Thank you for answer.

I forgot that there can be people not only from Russia who use Dos Navigator :D

Yes, I use that russian charset for russian users ;) and it seems that default WIN charset is slightly differs from standard Win-1251 charset.

Please, look at the picture

ftp://ftp2.granit.ru/temp/Image3.jpg

First table is seen from NDN, second from Notepad and third is from DN OSP. You can find that two last tables has similar marked parts, but in that from NDN symbol "No" stand in another place.

It would be very great if this symbol will be placed on the right place in default WIN charset, because it prevents (at least me) from using NDN in some cases...

 

P.S. Are you That Same Stefan Who Made The NDN ? :) If yes, then take my respects - it is became to be the very great program!

 

 

Share this post


Link to post
Share on other sites

Hi Crimso and again sorry for the late reply.

 

I am quite busy at the moment. :)

I have saved the image and the link to this thread.

I cannot work on this at the moment but I have added this to the todo list.

 

Yes, it is me.

I have taken over the work from Necromancer 5 years ago.

 

Thank you for your support and comments,

Stefan / AH

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×