From owner-freebsd-doc  Tue Sep  3 20:01:11 1996
Return-Path: owner-doc
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id UAA17190
          for doc-outgoing; Tue, 3 Sep 1996 20:01:11 -0700 (PDT)
Received: from silvia.HIP.Berkeley.EDU (ala-ca14-20.ix.netcom.com [204.32.168.84])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA17185
          for <doc@freebsd.org>; Tue, 3 Sep 1996 20:01:07 -0700 (PDT)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.5/8.6.9) id UAA10130; Tue, 3 Sep 1996 20:00:53 -0700 (PDT)
Date: Tue, 3 Sep 1996 20:00:53 -0700 (PDT)
Message-Id: <199609040300.UAA10130@silvia.HIP.Berkeley.EDU>
To: jfieber@indiana.edu
CC: jkh@time.cdrom.com, hanai@astec.co.jp, doc@freebsd.org
In-reply-to: <Pine.BSI.3.95.960903212527.7948B-100000@fallout.campusview.indiana.edu> (message from John Fieber on Tue, 3 Sep 1996 21:40:36 -0500 (EST))
Subject: Re: Warning: SGML doc changes
From: asami@freebsd.org (Satoshi Asami)
Sender: owner-doc@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

 * The obvious problem is combining different encodings.  I gather
 * if we restrict the non-japanese text to USASCII we should not run
 * into conflicts with EUC-J.  Thats fine for english and japanese,
 * but would be a hassle for other european languages who would be
 * better with the ISO 8859-x or KOI8 encodings.

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
use a stateful encoding (JIS for Japanese), but then we'll have a much
larger task of fixing tools to handle these.

And I'm sure our European (save Brits :) friends will have something
to say about restricting their code space to US-ASCII. :>

Satoshi

P.S. Of course there's also Unicode, but nobody uses that in the CJK
     world....