From erik@sran8.sra.co.jp Fri Apr  5 09:45:55 1991
Received: from mcsun.EU.net by dkuug.dk via EUnet with SMTP (5.64+/8+bit/IDA-1.2.8)
	id AA06724; Fri, 5 Apr 91 09:45:55 +0200
Received: from srawgw.sra.co.jp by mcsun.EU.net with SMTP;
	id AA13415 (5.65a/CWI-2.80); Fri, 5 Apr 91 09:45:25 +0200
Received: from srava.sra.co.jp by srawgw.sra.co.jp (5.64WH/1.4)
	id AA05661; Fri, 5 Apr 91 16:45:50 +0900
Received: from sran8.sra.co.jp by srava.sra.co.jp (5.64b/6.4J.6-BJW)
	id AA00975; Fri, 5 Apr 91 16:44:57 +0900
Received: from localhost by sran8.sra.co.jp (4.0/6.4J.6-SJ)
	id AA21054; Fri, 5 Apr 91 16:41:45 JST
Return-Path: <erik@sran8.sra.co.jp>
Message-Id: <9104050742.AA21054@sran8.sra.co.jp>
Reply-To: erik@sra.co.jp
From: Erik M. van der Poel <erik@sra.co.jp>
To: unicode@Sun.COM, wg15rin@dkuug.dk
Subject: Re: shortcomings in XPG locale (was Sort sequence)
Date: Fri, 05 Apr 91 16:41:44 +0900
Sender: erik@sran8.sra.co.jp
X-Charset: ASCII
X-Char-Esc: 29

Bill Tuthill writes:
> 1. There is no LC_BIDI database to store direction information.
> 	Did X/Open ever think about Hebrew and Arabic?

While we're at it, we might as well consider vertical printing, as is
sometimes used in Japan. So maybe we should call it LC_DIRECTION, or
LC_TEXTDIRECTION, or maybe just include it in LC_CTYPE?

By the way, I assume you mean that this info will tell the software
where to start printing, and in which direction to print it.


> 2. Input methods for disambiguating Japanese, Korean etc. are not
> 	codified in any LC_INPUT file.
> 
> 3. LC_FONT (or whatever) for supporting extended character sets
> 	and typography is missing.
> 
> 4. For Indic languages (and any heavily composed script), there
> 	is no LC_COMPOSE database.

Could you elaborate on these? Please cc wg15rin as above.


Erik M. van der Poel                                      erik@sra.co.jp
Software Research Associates, Inc., Tokyo, Japan     TEL +81-3-3234-2692