Re: local chars displayed as numbers

[Kenichi Handa]

In article <address@hidden>, Richard Stallman <address@hidden> writes:

> I get text in the mail in windows-1252, maybe not every day but often
> enough.

>     (1) Keep the curren code.
>     (2) Cancel the change for windows-1252.
>     (3) Cancel the change for windows-1252, and implement the \0
>       byte detection now (before the release).

> Could you state what the effects would be of each option?

>     (1) Keep the curren code.

A file containing a windows-1252 char that doesn't appear in
iso-8859-1 is detected as windows-1252.  Bad effect is that
some (or many) binary files are also detected as
windows-1252.

>     (2) Cancel the change for windows-1252.

A file containing a windows-1252 char that doesn't appear in
iso-8859-1 is detected as raw-text.

>     (3) Cancel the change for windows-1252, and implement the \0
>       byte detection now (before the release).
I think this option is not good.  Instead...

Reiner Steib <address@hidden> writes:

> (6) Implement null-byte detection (to prevent binary files
>    mis-detected as windows-12xx), keep the current code (windows-1252)
>    and add windows-1254/1255 accordingly.

I think that change results in the best behavior.

---
Kenichi Handa
address@hidden