X-Recipient: archive-cygwin@delorie.com
X-Spam-Check-By: sourceware.org
Date: Sun, 24 Jan 2010 13:05:08 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Please support CP932. (I have problem using subversion with  SJIS)
Message-ID: <20100124120508.GD2402@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <e22ab97b1001222149r3c217decmb0da069d7049c896@mail.gmail.com>  <20100123135020.GW2402@calimero.vinschen.de>  <20100123150703.GY2402@calimero.vinschen.de>  <416096c61001230751m308ac854x4f026b1f83b966d0@mail.gmail.com>  <20100123164546.GZ2402@calimero.vinschen.de>  <416096c61001231431u7e67cd37r2e741d0cb48c732f@mail.gmail.com>  <20100124093750.GA2402@calimero.vinschen.de>  <416096c61001240217l130c3e05ob5df918fd822be2d@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <416096c61001240217l130c3e05ob5df918fd822be2d@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Jan 24 10:17, Andy Koppe wrote:
> 2010/1/24 Corinna Vinschen:
> >   The people who decided to overload backslash
> > and tilde in the ASCII range with different symbols in SJIS still need
> > some serious knock on their heads.  No wonder the Microsoft guys kept
> > the binary values of characters intact, especially due to the backslash
> > problem.
> 
> I looked into this a bit more, out of morbid curiosity.
> [...]

Interesting.

> > In theory, we could be able to keep SJIS support in.C [...]  The
> 
> I've pondered that, and I don't think that's worthwhile. It's still
> going to cause trouble, e.g. with the backslash's use as an escape
> character and the tilde's use in shell expansions. Also, there are
> some more differences between standard SJIS and CP932 (although none
> as serious as the backslash and tilde issues), so more work would be
> needed to get that right. Finally, CP932 is the only "SJIS" that
> people are realistically going to care about, since that's what's in
> widespread use due to Windows. If someone really needs standard SJIS
> for converting documents or something, they can use iconv.
> 
> Therefore I've changed my mind on whether to keep SJIS and CP932
> separate: I think we should stick with the <locale>.SJIS charset as it
> is in 1.7.1, except that nl_langinfo(CODESET) for it should return
> "CP932" instead of "SJIS", to make sure iconv uses the right charset,
> thereby addressing the OP's issue.

You have a point there.  And it's the most easy way to implement it,
which is a good argument in itself.


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