- From: Martin J. Dürst <mduerst@ifi.unizh.ch>
- Date: Thu, 28 Aug 1997 18:25:11 +0200 (MET DST)
- To: kenzat@microsoft.com
- Cc: Kenichi Handa <handa@etlken.etl.go.jp>, Erik van der Poel <erik@netscape.com>, Kohji SHIBANO <shibano@tiu.ac.jp>, ietf-charsets@INNOSOFT.COM
Hello Kenzaburo, I have read your draft announced recently (draft-rfced-info-tamaru-00.txt). I think providing a possibility to include JIS 212 into iso-2022-jp is a good idea. Actually, this already has been done, in a somewhat wider framework. Please look for iso-2022-jp-2 in the IANA charset registry. Maybe this is too wide for your purposes. In this case, it is probably better to define something new (such as iso-2022-jp-1, iso-2022-jp-3, or iso-2022-jp-212), because most current implementations that know about iso-2022-jp will not react gracefully if they receive JIS 212 characters. Also, iso-2022-jp, in its current version, has been included as Appendix 2 (normative) in JIS X 0208:1997. A sudden change of the meaning of the label would only lead to confusion. At last, there is the IETF definition and the registration procedures for charset (currently being worked on). I don't think that these allow, or should allow, such drastic changes/additions to an existing "charset" as you are proposing. I am forwarding this mail to authors of the RFCs for iso-2022-jp and iso-2022-jp-2, to the chair of the JIS 208 commitee, as well as to the charset list where discussions about new charsets are taking place. With kind regards, Martin. ---- Dr.sc. Martin J. Du"rst ' , . p y f g c R l / = Institut fu"r Informatik a o e U i D h T n S - der Universita"t Zu"rich ; q j k x b m w v z Winterthurerstrasse 190 (the Dvorak keyboard) CH-8057 Zu"rich-Irchel NEW TEL: +41 1 63 543 16 S w i t z e r l a n d NEW FAX: +41 1 63 568 09 Email: mduerst@ifi.unizh.ch ---- --Boundary (ID uEbHHWxWEwCKT9wM3evJ5w)
Received on Thursday, 28 August 1997 09:27:54 UTC