Erik (living in Japan) writes:
Another approach would be to acknowledge that what we are really
trying to support are the national ISO 646 variants. So you might give
the Content-Type a name like this:
ISO-646-<registration-number>
E.g.
ISO-646-4 (for the United Kingdom)
Comments? Keld?
I don't think that the main thing is support for national ISO 646 variants.
The main thing is support for other characters/letters than ASCII.
And then support for the character sets that is used on the machines
that the users use... Be it latin1, latin2, Greek, national ISO 646
variant, japanese encoding, IBM codepages ..., and hopefully
without loss of interoperability and without information loss.
I would rather stick to the more general naming than ISO-646-4,
such as ISO-IR-4 - as I think the 8-bit sets may become extremely
important. The ISO-IR-nr is not my invention, BTW, but an EWOS PT
recommendation - as mentioned earlier.
Keld