Hello Markus!
I'm very glad to hear your clarification :-)
Still there's something that bothers me:
Details.pod
=head2 Encoding Names
Encoding names are case insensitive. White space in names is ignored.
In addition an encoding may have aliases. Each encoding has one
"canonical" name. The "canonical" name is chosen from the names of
the encoding by picking the first in the following sequence:
=over 4
=item * The MIME name as defined in IETF RFCs.
=item * The name in the IANA registry.
=item * The name used by the organization that defined it.
=back
Supported.pod
The "canonical"
name is chosen from the names of the encoding by picking
he first in the following sequence:
o The MIME name as defined in IETF RFCs.
o The name in the IANA registry.
o The name used by the organization that defined it.
So if we're speaking of encodings as Encode understands them
probably it is better to speak of the canonical names?
And they seem to be MIME names? So ISO-?
MK> Just for the record: The correct way to spell an ISO standard is to
MK> have a space between ISO and its number. Correct: ISO 8859-1.
MK> Other spellings such as ISO-8859-1 or ISO_8859-1 are merely
MK> workarounds for situations, where spaces are inconvenient.
MK> That's why MIME uses ISO-8859-1. In documentation, if you refer
MK> to the encoding, not its MIME name, please write ISO 8859-1.
To my worst confusion I had an impression that the real canonical
name is the name of the .enc file which is different from
both from MIME names and from 'ISO 8859-1' :-/
Anyone to help me out?
- Anton
