X-XP-NTP: 30
X-XP-Charset: IBM437
F-TO: Michiel van der Vlist
LEN: 2589
My original message had IBM437.
But, it arrived bearing an IBMPC kludge on the local NNTP side. :(
So, it appears that it left the bossnode with the IBMPC kludge as
well. :(
But, it arrived bearing an IBMPC kludge on the local NNTP side. :(
So, it appears that it left the bossnode with the IBMPC kludge as
well. :(
@CHRS: UTF-8 2^
Not all. Just the one in question, for the present.
JamNNTP has bugs as well in delaing with UTF-8. See above. Also,
AFAIK, it assumes that the header is always Latin-1.
@CHRS: UTF-8 2
And now?
X-XP-Charset: IBM437
My original message had IBM437.
But, it arrived bearing an IBMPC kludge on the local NNTP side. :(
So, it appears that it left the bossnode with the IBMPC kludge as
well. :(
https://www.compart.com/en/unicode/charsets/IBM437
https://www.iana.org/assignments/character-sets/character-sets.xhtml
For August... which one please, mate?
The problem has been identified in the code. There is a deliberate
change of ibm437 to ibmpc before packing. There is no buggyness.
The only buggyness is the rapid jumping to conclusions and the final solutions by select few people.
Sheesh.
Hello Tommi!
** On Tuesday 09.06.20 - 17:31, Tommi Koivula wrote to August Abolins:
Stop using OpenXP if you want to study kludges.
ROTFL. (Oooops, now I need help to get up!)
Granted, I heard that oxp was adapted for ftn, but it works quite well
afaik.
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 37:34:43 |
Calls: | 97 |
Files: | 4,642 |
Messages: | 217,283 |