MK> Not really surprising since it cannot edit utf-8 either. However MK> converting the 'M├╕├╕se' to latin-1 beforehand shouldn't pose any MK> problems. Both '├╕' characters are valid iso-8859-1 characters (0xf8). MK> Not so with many codepages but for sure iso-8859-1 and a few others MK> although the hex code might be different. I checked both iso-8859-1 and MK> cp1252 and they both convert to 0xf8. The rest of my messages have been MK> pure 7-bit ascii which shouldn't be an issue with any codepage.
Your remarks made me look into the Golded translation table. The o slash character is indeed in the translation table and as such it should look o.k.
However the conversion table assumes the UTF-8 o / to be represented by xF8. This however is the Unicode code point, whatever that may mean. The character however is represented by xc3b8, so he conversion table is not consulted for xF8, but for xC3 and xB8
KvE>> because when a replay reaches you the moose is still in utf-8
MK> Yep. I can confirm that. For the record it looks perfect. I'll be sure MK> to let my sister know too. ;-)
Yes and to most of Fidonet it is still a mistery what your sister was bitten by. ;)
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)
