09 Apr 16 17:26, you wrote to me:

 MK>>> so-called latin-1 has been misidentified as iso-8859-1 by many (too
 MK>>> many). [...] BTW latin1 is iso-8859-1.

 ml>> the above seems contridictory... is it??

 MK> Nope.  latin1 is not equal to latin-1.

semantics... they're both the same as far as other's are concerned...

[...]
 MK> will exit with;

 MK>   iconv: conversion to `latin-1' is not supported
 MK>   Try `iconv --help' or `iconv --usage' for more information.

so one program fails to alias the two together and instead quits instead of
doing the conversion and emittimg a warning about the dash in the name...
that's not a very good barometer to be using...

 MK> When researching the problem I came across some references to cp1252
 MK> but nobody would go out on a limb over it.  If you search IANA they
 MK> produce output for LATIN-1 but no insight about conversion to any
 MK> particular 8-bit encoding.  From observations it seems to me that the
 MK> Windows people use cp1252 for latin-1.  Björn Felton comes to mind
 MK> but I've seen others totally get it wrong when they assume iso-8859-1.

especially here where you say that IANA labels it as latin-1 with the dash and
that winwhatever folks likely use cp1252 as latin-1... again, with a dash...

 MK> Anyhow the bottomline here is to avoid it like the plague.  Besides
 MK> cp1252 works with iconv so it isn't like there isn't a suitable
 MK> encoding that will work when targetting most 8-bit charset users these
 MK> days.

you do what you have to do, i guess... others of us still have to work with
older stuff and deal with that as well as today's mess...

)\/(ark

Always Mount a Scratch Monkey

... 14. Keep a picture of your first fish, first car, and first girl/boyfriend.
---