Once even one non ASCII character slips in, the script that guesses
the encoding gets confused and decides the whole post must be Big5
or whatever.
On Sat, 17 Jan 2026 11:05:15 -0500, Maria Sophia wrote:
Once even one non ASCII character slips in, the script that guesses
the encoding gets confused and decides the whole post must be Big5
or whatever.
The native Windows character set is a kind of a weird one: it?s called ?UTF-16?, and it?s not something that anybody in their right mind
would design software to use. But I think that?s the fundamental root
of the problem.
Windows ended up with it for historical reasons, and it?s too late to
change now. But I suppose the occasional hiccup like this is
considered a small price to pay for all the benefits that the
Microsoft OS brings you ...
On Mon, 1/19/2026 12:55 AM, Lawrence D?Oliveiro wrote:
"Note
The native Windows character set is a kind of a weird one: it?s called
?UTF-16?, and it?s not something that anybody in their right mind
would design software to use. But I think that?s the fundamental root
of the problem.
New Windows applications should use Unicode to avoid the inconsistencies
of varied code pages and for ease of localization"
... [etc]
| Sysop: | Jacob Catayoc |
|---|---|
| Location: | Pasay City, Metro Manila, Philippines |
| Users: | 5 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 20:51:56 |
| Calls: | 117 |
| Calls today: | 117 |
| Files: | 367 |
| D/L today: |
559 files (257M bytes) |
| Messages: | 70,875 |
| Posted today: | 26 |