Date: Wed, 04 Sep 1996 12:36:48 +0900 From: Hanai Hiroyuki <hanai@astec.co.jp> To: asami@freebsd.org Cc: jfieber@indiana.edu, jkh@time.cdrom.com, doc@freebsd.org Subject: Re: Warning: SGML doc changes Message-ID: <9609040336.AA07720@adjanta.astec.co.jp> In-Reply-To: Your message of "Tue, 3 Sep 1996 20:00:53 -0700 (PDT)" References: <199609040300.UAA10130@silvia.HIP.Berkeley.EDU>
index | next in thread | previous in thread | raw e-mail
I've also checked John's Web page for Japanese verion of Handbook and I think there is no problems on the new tools. > I'm afraid this could be quite confusing, 'cause Chinese and Korean > can also be encoded in EUC and there is nothing in there to > distinguish. The only way to mix multiple multi-byte languages is to Yes, I'm afraid that too. > use a stateful encoding (JIS for Japanese), but then we'll have a much > larger task of fixing tools to handle these. Yes, it's too hard. Also, another point is the SGML declaration. When we write some documents(SGML instances) in EUC, sections of BASESET and DESCSET for EUC part in the SGML declaration should be like... BASESET "ISO Registration Number 87//CHARSET JIS X 0208 Japanese Character Set//ESC 2/6 4/0 ESC 2/4 2/9 4/2" DESCSET 128 127 128 255 1 UNUSED In practice, SGML parsers such as sgmls, nsgmls.. can handle Japanese characters correctly without above part in the SGML declaration if 8-bits code is not forbidden. So, this is not an actual problem but a political problem ;-> -----H.Hanai hanai@jp.freebsd.orghelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9609040336.AA07720>