On 04 Jan 14 23:45, Maurice Kinal wrote to Nicholas Boel:
MK> Hey Nicholas!
NB>> Since my messages are proper UTF-8, it should be a level 4 NB>> kludge, according to the FTSC document
MK> Understood. Another obvious flaw in FTSC documentation. No surprise MK> about that here. They still haven't bothered upgrading up to 1989 MK> standards why would the above come as a surprise to anyone? I won't MK> even mention the obsoleted FTN datetime stamp. Not even Microsoft MK> will go out on a limb for that one and they have a shoddy record when MK> it comes to standards, especially ones they claim to support under the MK> guise of 'backwards compatibilty'. What a bad joke that turned out to MK> be eh?
Sorry. I don't see an error in the FTSC documentation in that regard, but that would be more of a flaw in either Golded or the translation tables it uses.
NB>> The few times he does post UTF-8 messages
MK> Where? I'd muchly appreciate seeing one.
Try the original message he replied to you asking what was wrong with FTS-5003.001. It was only a few days ago or so. I saw that one had a "CHRS: UTF-8 4" kludge on it.
NB>> Unless I use CP866 as my default codepage, his workaround and NB>> translation table will not work here.
MK> Oh those Russians! Wait a minute ... he isn't Russian. What kind of MK> operation is he running there?!?!?!?!
Sorry about that. That was my fault - a bad typo. I meant CP850.
Regards, Nick
--- GoldED+/LNX 1.1.5-b20130910 * Origin: Dark Sorrow | darksorrow.us (1:154/701)
