Your default charset may vary from CP437 AKA ASCII, AKA AMIGA,I'm sure others will correct you too, but ASCII is *not* AKA CP437.
CP850 AKA
(albeit FTS-5003.001 says ASCII),AKA CP437.
Hello, Rob!
Saturday February 24 2024 15:43, from Rob Swindell -> Nil Alexandrov:
Your default charset may vary from CP437 AKA ASCII, AKA AMIGA,I'm sure others will correct you too, but ASCII is *not* AKA CP437.
CP850 AKA
(albeit FTS-5003.001 says ASCII),AKA CP437.
My bad, CP437 AKA extended-ASCII. I actually like this topic of different encoding according to fts-5003. IMHO, the supported level field of CHRS kludge is pretty much useless and might be ignored by software cause the identifier aka charset name itself includes the details of how it is sent over the wire. BTW, can we do UTF-16? UTF-32? Level makes no sense.
I don't think UTF-16 or UTF-32 is supported in FTN. Nor should it be, IMHO.
Hello Rob,
On Saturday February 24 2024 17:28, you wrote to Nil Alexandrov:
I don't think UTF-16 or UTF-32 is supported in FTN. Nor should it be, IMHO.
UTF-16 and UTF-32 have NULL bytes in the encoded stream. This conflicts with the use of the NULL byte as the "end of text" in Fidonet.
Sysop: | Xerxes |
---|---|
Location: | Azle, Texas |
Users: | 131 |
Nodes: | 10 (0 / 10) |
Uptime: | 111:19:14 |
Calls: | 3,193 |
Calls today: | 3 |
Files: | 195 |
U/L today: |
0 files (0K bytes) |
D/L today: |
0 files (0K bytes) |
Messages: | 366,398 |
Posted today: | 0 |