delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,SPF_PASS |
X-Spam-Check-By: | sourceware.org |
Message-ID: | <4B12F787.3050006@tlinx.org> |
Date: | Sun, 29 Nov 2009 14:36:55 -0800 |
From: | Linda Walsh <cygwin AT tlinx DOT org> |
User-Agent: | Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.8.1.23) Gecko/20090812 Lightning/0.9 Thunderbird/2.0.0.23 ThunderBrowse/3.2.6.5 Mnenhy/0.7.6.666 |
MIME-Version: | 1.0 |
To: | "cygwin AT cygwin DOT com" <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> |
In-Reply-To: | <4B111536.7090904@byu.net> |
X-Stationery: | 0.4.10 |
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 |
Eric Blake wrote: > Rather than complaining, write a patch to prove your point. Patches speak > much louder than rants on open source projects. But I won't be the one > writing the patch. ---- I already supplied code in the first email. It's a matter of using those constants instead of the ones being used. Corinna Vinschen wrote: >> According to Linda Walsh on 11/28/2009 3:24 AM: > >>> Any other standards group I know of is going UTF-8. All of the >>> linux distributions I know are going UTF-8. I'd like to see Cygwin >>> go that way too. > > I don't understand this one. What on earth are you think we're doing? > Do you really understand the sense of the mapping? --- You are trying to allow use of the commonly usable '7 banned chars' (under DOS) that are occasionally used on Unix. No? The UTF-8 is referring to the fact that the substitute chars I'm referring to would be viewable on platforms using UTF-8 -- as the unicode values in UTF-16 are directly convertible to UTF-8 platforms (which such wouldn't be the case to platforms using not Unicode-based platforms). > But that mapping doesn't make sense. Instead of mapping valid, but > forbidden characters into a range which doesn't contain valid > characters, the valid characters are then mapped onto other valid > characters. How are you going to ever map them back? When is a > FULLWIDTH QUOTATION MARK actually a QUOTATION MARK and not really a > FULLWIDTH QUOTATION MARK? You're covering perfectly valid characters > and make them unusable. Besides, we have not only to map the few > characters you're talking about, the U+f0XX range is also used to > map invalid UTF-8 chars. ---- 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. There are no applications that currently use those values because cygwin 1.5 didn't support either the real ascii values OR the unicode values. It's a matter of seeing those file names, produced by 1.7 as semi valid values when viewed in explorer and when they are viewed on linux servers. _I_ use those values 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". In linux and windows, I'm using them as display forms. I put quotes around the filesnames so whether they are converted to real ascii forms under cygwin or stored as visual display forms is of no consequence. I don't see a problem. And the patch is just changing the hex values used to the ones I supplied in my original posting. Am I indicating an understanding of the problem and implications? Do you feel it's really a problem given how they are commonly used and how there would be no conflicting applications? linda -- 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |