[Top] [All Lists]

Re: Ambiguity on 8859-* and bi-directionality

1994-07-13 05:15:06
Masataka Ohta writes:

It seems to me that thee definitions on ISO-8859-* are ambiguous 
in RFC1521 and draft-ietf-822ext-mime-imb-00. Perhaps, ISO-8859-* 
is intended to be used with 8 bit without designating escape sequences. 
But there is no such description. 
It is perfectly possible to encode text with ISO 8859/1 with pure 7
bit as:

   "ASCII_string" ESC - A "8859/1_right_part_string" ESC ( B "ASCII_string"

Can't I call the encoding "ISO-8859-1"? Or must MUAs supporting
"ISO-8859-1" be able to decode the above stateful encoding? Or,
shall we call the encoding "US-ASCII"? But, if we can call any 7
bit encoding "US-ASCII", why there is "ISO-2022-JP"?

To disambigufy, you can just simply say

      announcer of 4/3 is, though omitted, assumed

It is correct that ISO 9959-1 can be coded in 7-bit only,
with G0/G1 bannouncing, and this was never intended in MIME,
with the  charset=iso-8859-1 specification. The intention
was to refer to the charset RFC, where iso-8859-1 and the other
8859-series charset names are defined. making a reference to
RFC1345 for the charset definitons would clear up this problem.

Keld Simonsen