ietf-822
[Top] [All Lists]

Re: recommended encoding for RFC-XXXX

1991-10-23 10:19:27
  Base64 encoding of IS-10646 (whenever it happens) would be vastly
superior in its multilingual capabilities and would completely remove
all of the concerns about Asian language support that strongly remain
with regards to any of the alternatives to IS-10646 encodings.

Why? I see no base for that statement.
As far as I see, there are 3 ways of encoding 10646:

1. base64
2. quoted-printable
3. mnemonic

1. base64 will be totally incomprehensible, also for Kanji.

2. quoted-printable will be somewhat readable on unextended HW for ASCII,
but only ascii. It will be gibberish for the rest, also for Kanji.

3. mnemonic will be somewhat readable for a lot of characters,
but not for Kanji. Japanese (and other CJK) will be able to see
that it is a Kanji character. Kana will be somewhat readable.
Characters not having a mnemonic wil have a name like ?uxxxx -
giving the 10646 hex code point.

So for unextended viewers of encoded 10646M, base64 will be the worst,
(in contradiction to what you claim), quoted-printable will be a
little better and mnemonic will be better for almost everyone, and
not worse for anybody.

Keld
,

<Prev in Thread] Current Thread [Next in Thread>