X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.5 required=5.0 tests=AWL,BAYES_00
X-Spam-Check-By:	sourceware.org
Message-ID:	<4B13D7A6.7030407@towo.net>
Date:	Mon, 30 Nov 2009 15:33:10 +0100
From:	Thomas Wolff <towo AT towo DOT net>
User-Agent:	Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: cyg1.7 - DOS character remapping: change request.
References:	<4B0B21E0 DOT 3050909 AT tlinx DOT org> <4B0B5433 DOT 8020603 AT byu DOT net> <4B0B610D DOT 6080709 AT tlinx DOT org> <20091124085022 DOT GR29173 AT calimero DOT vinschen DOT de> <20091124090646 DOT GS29173 AT calimero DOT vinschen DOT de> <4B10FA45 DOT 6060605 AT tlinx DOT org> <4B111536 DOT 7090904 AT byu DOT net> <4B12F787 DOT 3050006 AT tlinx DOT org> <416096c60911292339v2ea3dc4et508ffe98a725efea AT mail DOT gmail DOT com>
In-Reply-To:	<416096c60911292339v2ea3dc4et508ffe98a725efea@mail.gmail.com>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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

Andy Koppe wrote:
> 2009/11/29 Linda Walsh:
>   
>>        I'm aware that this would reserve the 'display forms'
>> of those chars and map them them to their real forms when
>> interpreted within cygwin.  I don't see this to be a problem.
>>     
> But it is a problem. It would make it impossible to use the wide forms
> of those deadly chars in Cygwin filenames.
>
> Btw, does anyone know why those wide ASCII chars exist in the first place?
<http://unicode.org/mail-arch/unicode-ml/Archives-Old/UML018/0289.html>
sheds some light on the issue.
Their nature as kind of presentation forms might slightly support 
Linda's view. However, like the other presentation forms, they have in 
fact their own Unicode code points which makes the round-trip 
counter-argument strong.
> Do they occur in East Asian character sets?
>   
They are actually listed in all CJK character sets (checking i18n data). 
Whether this was really used or not, it makes their view as 
"presentation forms" weaker.

>> _I_ use those [wide ASCII chars] in filesnames,
>> and know of no compatibility problems having them
>> treated as 'real' ascii characters under cygwin --
>> since I am just using them for 'display' purposes
>> in file names like like "Music:the group:title 1/3".
>>     
> Sounds like you've found a good solution there already. The wide forms
> show up correctly in Explorer, Cygwin, and via Samba, don't they?
>
> To make them more convenient to use, you could add them to your
> keyboard layout using Microsoft's Keyboard Layout Creator, e.g. with
> AltGr+':' for the wide colon.
>   
Sounds like a good proposal. On the other hand, I can also understand Linda.
Trying to conciliate, what about a $CYGWIN option to map pathname ":" to 
filesystem fullwidth "：" etc?
To meet concerns of unambigous filename representation, it could also be 
a one-way option, so mapping back filesystem "：" to itself, and the 
Interix code to ASCII ":".

Thomas

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

- Raw text -