MK> Just thought you might want to know that your reply to Michiel - "MSGID: MK> 2:280/5003.4 534c0d05", "REPLY: 2:280/5555 534c067a" - got corrupted when MK> you quoted his utf-8 characters and then saved it as per your "CHRS: MK> LATIN-1 2" which they aren't. They still show as valid utf-8 characters MK> but not the original codes as Michiel sent them.
I am aware, that I make a mess of UTF-8, but at the moment I am not striving to get that correct. As you can see, I use golded on Linux system. Getting the 8 bit conversions correct was already a challenge and even there I get more or less different results depending on the terminal emulator used.
I do have a longterm goal to support UTF-8, but don't hold your breath. There are some attempts in the source of golded to implement iconv and use the wide character version of curses. I don't know if diving into that code is feasable, or that starting with a clean slate is better. Both are a bit over my abillities, but who knows.
MK> I've made this identical mistake before which is why I wanted to test MK> a MK> few 8-bit messages in this echo to see if I was doing it correctly as per MK> fts-5003. Anyhow it is just the quoted stuff that got grunged. None of MK> that was latin-1 in the original and it still isn't despite it looking a MK> mess.
I have seen them, the 8 bit messages came out well. If you want them returned, just say so.
Kees
--- FPD v2.9.040207 GoldED+/LNX 1.1.5 * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
