- From: Keld J|rn Simonsen <keld@dkuug.dk>
- Date: Thu, 02 Sep 1993 20:32:07 +0200
- To: Masataka Ohta <mohta@necom830.cc.titech.ac.jp>, jerman-blazic@ijs.si (Borka Jerman-Blazic)
- Cc: wg-char@rare.nl, ietf-charsets@INNOSOFT.COM
Masataka Ohta writes: > > >> And again RFC 1345 is ISO 10 646 based!! > > > >It's character mnemonic, except for Han characters, is 10646 based. > > > > So, what is wrong with what I have said. > > RFC 1345 is not based on 10646. The base code in RFC 1345 is the 10646 DIS2. RFC 1345 describes amongst other things a method for representing 10646 in a number of coded character sets. I am in the process of updating rfc1345 to correspond to the finished 10646. > > I have seen some countries complaining > > about RFC1345 not to be applicable for their languages because is not > > readable. But, we are not supposed to discuss here MIME and MNEMONICS? There are many things that are not readable, including hex representations of characters, and transformed encodings of 10646. mnemonic is a way to repesent 10646 as some form of string in plain ascii - which you sometimes can read with minor hazzle, sometimes you have to look it up in tables, but in any case you have the possiblity to look up in tables the character from the ascii string. This is not possible with any other encoding of 10646. > We are not supposed to discuss here on specifically on RFC 1345, at all. RFC 1345 techniques should be amongst the discussion items allowed here, It is one of the ways to represent 10646. It handles a lot of character sets. Keld --Boundary (ID uEbHHWxWEwCKT9wM3evJ5w)
Received on Thursday, 2 September 1993 11:34:26 UTC