KvE> The character however is represented by xc3b8, so he conversion KvE> table is not consulted for xF8, but for xC3 and xB8.
The above is the wrong way to handle that. The actual utf-8 code is *not* 0xc3b8 but instead 0x0f8 or U+00F8 depending on your output in any half-decent utf-8 capable application. The little endian hex output should be c3b8 though but that is a limitation imposed by an 8-bit character application including a shell such as bash.
I find this link quite handy when looking up utf-8 codes; http://www.utf8-chartable.de/. Note the below cut and paste for this particular character;
U+00F8 ø c3 b8 LATIN SMALL LETTER O WITH STROKE ^^^^^ I took the liberty of adding the '^' character under the hex output column. The best explanation as to what utf-8 is all about can be found here; http://en.wikipedia.org/wiki/UTF-8
KvE> Yes and to most of Fidonet it is still a mistery what your sister KvE> was bitten by.
I guess they'll have to wait to find out until they are up to standards eh? ;-)
Kids these days. :::sigh:::
Life is good, Maurice
... A Møøse once bit my sister ... --- GNU bash, version 4.2.45(2)-release (x86_64-unknown-linux-gnu) * Origin: Pointy Stick Society - Ladysmith BC, Canada (1:153/7001.0)
