Mail Archives: cygwin/2010/01/24/07:06:26
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
- Raw text -