X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Sat, 28 Nov 2009 13:53:59 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cyg1.7 - DOS character remapping: change request.
Message-ID: <20091128125359.GC29173@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4B111536.7090904@byu.net>
User-Agent: Mutt/1.5.20 (2009-06-14)
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

On Nov 28 05:19, Eric Blake 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?

> >   But barring any other changes, I'd really, (like pretty please!)
> > like to see them mapped to their, reserved-visual, but semantically
> > impotent equivalents.
> 
> http://cygwin.com/acronyms/#PTC
> 
> 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.

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.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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