Hello James,
On Saturday March 07 2020 19:47, you wrote to me:
Non ASCII characters without a CHRS: line makes garbage...
"Incoming messages without "CHRS" control lines should be considered
as being written in the area's default character set (normally
ASCII, IBM codepage 437"
I do not know where you got that, but FTS-5003 says something different:
=== quote FTS-5003 ===
Incoming messages without "CHRS" control lines should be considered
as being written in pure ASCII, but may be treated as being written
in some default character set or character encoding scheme. Such as
IBM codepage 437, IBM codepage 866 or UTF-8. It is recommended that
message readers offer the user the option of manually selecting a
different character set or encoding scheme for these messages on a
per-area, per-message or other basis.
=== end quote FTS-5003 ===
Those characters are IBM codepage 437 when they are hitting my system, which means that the characters are in compliance.
In complience with what? AFAIK, there is no default character encoding defined for this area.
But it does look like you're getting a UTF8 version of them somehow.
My reader is configured to use UTF-8 as the default.
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin:
http://www.vlist.eu (2:280/5555)