X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 	tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <3f0ad08d0906060242t275a78e7tb9913bf78d1c5e83@mail.gmail.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> 	 <200905201652 DOT n4KGqYGm000509 AT mail DOT bln1 DOT bf DOT nsn-intra DOT net> 	 <200906051625 DOT n55GP6t3028411 AT mail DOT bln1 DOT bf DOT nsn-intra DOT net> 	 <3f0ad08d0906060242t275a78e7tb9913bf78d1c5e83 AT mail DOT gmail DOT com>
Date: Sat, 6 Jun 2009 18:46:11 +0900
Message-ID: <3f0ad08d0906060246y39cde70fma459b3ec3d894d13@mail.gmail.com>
Subject: Re: [Fwd: [1.7] wcwidth failing configure tests]
From: IWAMURO Motonori <deenheart AT gmail DOT com>
To: cygwin AT cygwin DOT com, newlib AT sourceware DOT org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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

I oppose your proposal because I think that it is useless for us.

2009/6/6 Thomas Wolff <towo AT towo DOT net>:
> the intention is that the "codepage" information should be the same
> for all locales having thbe "UTF-8" (or any other) charmap.  So you
> cannot freely change width information among locales with the same
> charmap.

I don't think that there is such a restriction.
The standard of the character doesn't provide for the width of the
character as a standard.

> Also, if ja_JP.UTF-8 would mean "CJK width", how would you specify a
> working locale setting for a terminal that does not run a CJK width
> font but should yet use other Japanese settings? E.g. with rxvt
> which does not support CJK width.

Oh, we ALWAYS have a hard time in this problem VERY VERY VERY much.

case1: We use only the application that treats the width of the
character without locale.
case2: We make the patch that solves the character width problem, and
throw it out up-stream.
case3: We make the patch, and apply it locally.
case4: We tearfully give up the correct display of the screen.
case5: We tearfully give up using the application.

I selected case5 for rxvt.

> Thus you could define e.g.
>        ja_JP DOT UTF-8 AT cjk
> or
>        ja_JP DOT UTF-8 AT cjkwidth
> to indicate CJK width properties. I guess this is the most compliant way to go.

I don't think that it is the good idea because:

- It is "a cygwin-specific solution (or workaround)".
- In NetBSD, the change to which wcwidth of East Asian Ambiguous
Characters returns 2 by CJK locale is planned.

# to be continued.
-- 
IWAMURO Motnori <http://vmi.jp/>

--
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/