From xemacs-m  Fri May 30 00:29:41 1997
Received: from mail1-im.etl.go.jp (mail.etl.go.jp [192.50.105.9])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id AAA14503
	for <xemacs-beta@xemacs.org>; Fri, 30 May 1997 00:29:36 -0500 (CDT)
Received: from etlpom.etl.go.jp (etlpom.etl.go.jp [192.31.200.9]) by mail1-im.etl.go.jp (8.8.5/3.5Wpl1-96112918) with ESMTP
	id OAA05798; Fri, 30 May 1997 14:00:52 +0900 (JST)
Received: from etlken.etl.go.jp (etlken.etl.go.jp [192.31.197.11]) by etlpom.etl.go.jp (8.8.5/3.5Wpl4-ETL_MASTER) with SMTP id OAA28269; Fri, 30 May 1997 14:00:47 +0900 (JST)
Received: by etlken.etl.go.jp (SMI-8.6/6.4J.6-ETL.SLAVE)
	id OAA11101; Fri, 30 May 1997 14:02:19 +0900
Date: Fri, 30 May 1997 14:02:19 +0900
Message-Id: <199705300502.OAA11101@etlken.etl.go.jp>
From: Kenichi Handa <handa@etl.go.jp>
To: morioka@jaist.ac.jp
CC: steve@miranova.com, mrb@Eng.Sun.COM, xemacs-beta@xemacs.org, Kazu@Mew.org,
        ksakai@netwk.ntt-at.co.jp
In-reply-to: <199705140544.OAA15563@mikan.jaist.ac.jp> (message from
	=?ISO-2022-JP?B?GyRCPGkyLBsoQiAbJEJDTkknGyhC?= / MORIOKA Tomohiko on
	Wed, 14 May 1997 14:44:36 JST)
Subject: Re: emacs-mule as a coding system name for Emacs' internal format
References:  <199705140544.OAA15563@mikan.jaist.ac.jp>

I'm very sorry for this very late response.

   From: =?ISO-2022-JP?B?GyRCPGkyLBsoQiAbJEJDTkknGyhC?= / MORIOKA Tomohiko <morioka@jaist.ac.jp>
   Date: Wed, 14 May 1997 14:44:36 JST

   handa> Another matter is that he also requested to have coding systems
   handa> of more informative names.  For instnace, as for the current
   handa> name of "CODING", make "REGION-CODING" as the real name and
   handa> make "CODING" the alias of it.

     Coding-system of mule is not basically closed character set.
   shift_jis or big5 is closed so japanese-sjis or chinese-big5 aren't so
   strange.  However `iso-8859-1' of mule can include JIS X0208, or
   `iso-2022-jp' can include ISO 8859-1.

     In addition, `japanese-iso-2022-jp' or `chinese-cn-gb2312' seem
   strange.  If such kind of systematic naming is required, I propose
   following:

       CODING-SYSTEM-NAME = SCRIPT-(-ENCODING)(-VARIANT)

       SCRIPT = SCRIPT_PRIM(-SCRIPT_MINOR)

       SCRIPT_PRIM = amharic | arabic | chinese | cyrillic | devanagari |
		     greek | japanese | korean | lao | latin | thai |
		     tibetan | ...

       SCRIPT_MINOR = <natural number> | gb | ...

       ENCODING = 7bit ; ISO 2022 based 7bit encoding
		| euc  ; ISO 2022 based 8bit encoding (default)
		| <other encoding name (ex. sjis, big5, viscii, tis620)>

       VARIANT = irv ; ISO 646 IRV (may be omitted)
	       | ms ; Microsoft extension
	       | eten ; big5-eten
	       | other variant name (ex. jisx0201)

It seems to be a good idea.  Perhaps, we had better have "iso-7bit"
and "iso-8bit" in ENCODING instead of "7bit" and "euc".

---
Ken'ichi HANDA
handa@etl.go.jp

