Hello Maurice!

 MK> For the record, I do see LATIN-1 as a subset of Unicode as well as
 MK> extended ISO 8859-1 Latin-1 for Windows 3.0 but neither of these show up
 MK> in the current version of glibc here which is probably a good thing.

 Whatever suits you.

 KvE>> It looks good here, but will probably be a mess when it gets
 KvE>> converted back to LATIN-1

 MK> It looks bad before converting since it never got converted to utf8 in the
 MK> first place.  I see it here as;

 KvE>> A Mse once bit my sister...

 It was generated as UTF and pasted into the messages, but luit converted
 it right back to ISO 8859-1 .

 MK> Note that the characters in question show up in your message as 8 bit
 MK> characters and not utf8 ones so the conversion process failed.

 MK> I am sure if you convince those truly responsible for ISO standards
 MK> that
 MK> the LATIN-1 alias *should* be attached to ISO-8859-1 then it will be
 MK> properly taken care of but I am also sure that it will create a conflict
 MK> with proprietary character set(s) already claiming the alias as theirs.
 MK> Personally I choose to continue ignoring the issue since I never had an
 MK> issue with it in the first place.  If it ever matters then LATIN1 works
 MK> fine and always has for ISO-8859-1.  No?

 What's in a name?

Kees

--- GoldED+/LNX 1.1.5