This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [Fwd: [1.7] wcwidth failing configure tests]


2009/6/13 Corinna Vinschen <vinschen@redhat.com>:
>> I'm not sure which "standard" you are referring to.
>
> The problem appears to be that there is no standard for the handling
> of ambiguous characters.

Yes, but the guideline exists.
http://cygwin.com/ml/cygwin/2009-05/msg00444.html
> 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.

> Define the default for ja, ko, and zh to use width = 2, with a
> @cjknarrow (or whatever) modifier to use width = 1.

I think it is good idea.
-- 
IWAMURO Motnori <http://vmi.jp/>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]