MK> The above is the wrong way to handle that. The actual utf-8 code is *not* MK> 0xc3b8 but instead 0x0f8 or U+00F8 depending on your output in any MK> half-decent utf-8 capable application. The little endian hex output MK> should be c3b8 though but that is a limitation imposed by an 8-bit MK> character application including a shell such as bash.
Just for the record, if your messages was sent around coded in UTF code code points, your message would be unreadable on systems that are unaware of UTF-8. However all character op to 0x7e are presented properly. What I get presented in LATIN-1 0xc3 = Capital A tilde, 0xb3 = Cedilla As 0xc3 and 0xb3 are not in de translation table, nothing is converted.
MK> I find this link quite handy when looking up utf-8 codes; MK> http://www.utf8-chartable.de/. Note the below cut and paste for this MK> particular character;
MK> U+00F8 ├╕ c3 b8 LATIN SMALL LETTER O WITH STROKE MK> ^^^^^ MK> I took the liberty of adding the '^' character under the hex output MK> column. The best explanation as to what utf-8 is all about can be found MK> here; MK> http://en.wikipedia.org/wiki/UTF-8
Ik know, I consulted the same web pages.
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)
