-={ vrijdag, 11 maart 2016, 16:42:40 +0100 }=-

Hey Kees!

 KvE> There is a LATIN-8 in the list of aliases supported by iconv

I only show a LATIN-9 as per;

  :read !iconv -l | grep LATIN-[[:digit:]]
LATIN-9//

or

  :read !grep LATIN-[[:digit:]] /usr/lib/gconv/gconv-modules
alias LATIN-9//  ISO-8859-15//

which is more telling methinks.

 KvE> and execute iconvconfig to create the cachefile,
 KvE> all your pains will be over. ;)

Not my pain.  I don't require such a 'fix' but if I did then I'd take it up
with the people responsible for the alias.

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

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

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

 KvE> A Mse once bit my sister...

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

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

Life is good,
Maurice

... Don't cry for me I have vi.
--- GNU bash, version 4.3.42(1)-release (x86_64-unknown-linux-gnu)