On 04 Jan 14 19:36, Maurice Kinal wrote to Nicholas Boel:
NB>> should definitely NOT be showing up as "UTF-8 2"
MK> Agreed. However I still see your UTF-8 characters as UTF-8 characters MK> despite the above.
Which is why I'm asking about it. Since my messages are proper UTF-8, it should be a level 4 kludge, according to the FTSC document (even though it's unnecessary in reality).
NB>> the Win32 version that Michiel uses
MK> I have yet to see any evidence of it truly working despite it getting MK> the kludge right. Have you?
As a matter of fact I have. The few times he does post UTF-8 messages, it does in fact include the 4th level. Unless I use CP866 as my default codepage, his workaround and translation table will not work here.
He had told me that it is the tables that translate from other things to UTF-8 that set that level parameter anyway, which I have all of them in place and have tried whatever "trick" he and Stas added into his version of Golded (which was basically setting a double level parameter in the tables.. one for reading, and one for writing.. ie: "2 4"). My question in the GOLDED echo was if that was implemented over all platforms, or just done for Michiel's version. I'm awaiting an answer on that one.
Anyway, I'll try to keep the Golded related stuff in that echo, and the kludge stuff and/or the necessity of some of it in this one. Rather hard to do when you're talking about two different things in one instance, though. Pair that with the fact that quite a few developers read/write in this echo, I assumed there would be a better possibility of feedback and discussion than the mostly dead echo for Golded support. YMMV.
Regards, Nick
--- GoldED+/LNX 1.1.5-b20130910 * Origin: Dark Sorrow | darksorrow.us (1:154/701)
