- From: Masataka Ohta <mohta@necom830.cc.titech.ac.jp>
- Date: Thu, 02 Sep 1993 13:18:04 +0900 (JST)
- To: KLENSIN@INFOODS.MIT.EDU (John C Klensin)
- Cc: jerman-blazic@ijs.si, wg-char@rare.nl, ietf-charsets@INNOSOFT.COM
> >UTF-2 is ASCII compatible, 8 bit oriented encoding scheme of 32 bit UCS4. > > Something is either "ASCII compatible", or it is "8 bit oriented", but > it can't be both. UTF-2 is the latter, and requires encoding to be > used over a 7bit ASCII transmission channel. OK. UTF is ASCII compatible on 8 bit transparent text transport. Right? On most of the Internet, ASCII text is transmitted on such transport. Right? The major exception was mail and news. But with 821ext and 822ext, mails can now handle 8 bit. Recent Bnews and Cnews are 8 bit transparent and many community (Russian, Korean etc.) relies on it so that it is the defacto standard. Then, what we should do is 1) to have some ASCII compatible encoding assuming such transport 2) identify protocols which do not have support such transport 3) develop the general frame work to extend non-transpartent protocols Right? Masataka Ohta --Boundary (ID uEbHHWxWEwCKT9wM3evJ5w)
Received on Wednesday, 1 September 1993 21:23:32 UTC