X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Thu, 14 May 2009 19:26:25 +0200
From:	Corinna Vinschen <vinschen AT redhat DOT com>
To:	newlib AT sourceware DOT org, cygwin AT cygwin DOT com
Subject:	Re: [Fwd: [1.7] wcwidth failing configure tests]
Message-ID:	<20090514172625.GA20688@calimero.vinschen.de>
Reply-To:	newlib AT sourceware DOT org
Mail-Followup-To:	newlib AT sourceware DOT org, cygwin AT cygwin DOT com
References:	<20090512165404 DOT GW21324 AT calimero DOT vinschen DOT de> <416096c60905120956n5521929bm69586f5e6325a994 AT mail DOT gmail DOT com> <20090512173153 DOT GY21324 AT calimero DOT vinschen DOT de> <3f0ad08d0905140858j17c7b374paa649f18ef18178d AT mail DOT gmail DOT com>
MIME-Version:	1.0
In-Reply-To:	<3f0ad08d0905140858j17c7b374paa649f18ef18178d@mail.gmail.com>
User-Agent:	Mutt/1.5.19 (2009-02-20)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On May 15 00:58, IWAMURO Motonori wrote:
> 2009/5/13 Corinna Vinschen <vinschen AT redhat DOT com>:
> >> http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c
> >
> > This looks nice.
> 
> Do you import Markus Kuhn's wcwidth implementation?
> 
> >> Trouble is, there's the thorny issue of the "CJK Ambiguous Width"
> >> category of characters, which consists of things like Greek and
> >> Cyrillic letters as well as line drawing symbols. Those have a width
> >> of 1 in Western use, yet with CJK fonts they have a width of 2. That's
> >> why Markus Kuhn's code includes the mk_wcswidth_cjk() variant.
> >
> > We should use the standard variation alone, imho.
> 
> I don't think so.
> 
> 1) It is very very inconvenient for me :-)
> (Now, I apply the local patch of CJK width support to cygwin1.dll in
> my environment.)
> 
> 2) Unicode Standard Annex #11
> http://www.unicode.org/unicode/reports/tr11/ recommends:
> > 5 Recommendations
> (snip)
> > When processing or displaying data
> (snip)
> > Ambiguous characters behave like wide or narrow characters depending
> > on the context (language tag, script identification, associated
> > font, source of data, or explicit markup; all can provide the
> > context). If the context cannot be established reliably, they should
> > be treated as narrow characters by default.
> 
> The recommendation is independent of legacy encoding.
> 
> I think that a new locale category that specifies the "context" is necessary.
> Because the "context" influences only the display or text layout.
> 
> However, there is no such standard now.
> 
> Therefore, I propose to use *_cjk() when the language part of LC_CTYPE
> is 'ja', 'ko', 'vi' or 'zh'.

That would be fine with me, but tests for the actual language are not
used anywhere in newlib, so that's something very new.  Can we check in my patch for the time being and
extend it with the CJK variation later?  I will not be available for the
next two weeks, but I'd be glad if at least the default variation can go
in so I can create another Cygwin test release before I'm offline.


Corinna

-- 
Corinna Vinschen
Cygwin Project Co-Leader
Red Hat

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -