| delorie.com/archives/browse.cgi | search |
2010/1/24 Corinna Vinschen <corinna-cygwin AT cygwin DOT com>: > On Jan 24 13:05, Corinna Vinschen wrote: >> On Jan 24 10:17, Andy Koppe wrote: >> > 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. =A0And it's the most easy way to implement it, >> which is a good argument in itself. > > I checked that in now. =A0I also kept charset "CP932" in. =A0After all, it > doesn't hurt to support that as well. > > Nayuta, can you please test if the latest from CVS works for you even > with LANG=3D"ja_JP.SJIS"? Thank you for implementing CP932 and changing SJIS to an alias of CP932. I'll test it tomorrow. 2010/1/24 Andy Koppe <andy DOT koppe AT gmail DOT com>: > I think that's the correct thing to do, but it'll likely break other > stuff. Seems SJIS really isn't suited for Unix command line use. All > the more reason to make EUC-JP the default for "ja_JP" I guess. I prefer UTF-8 (or CP932) for the default for "ja_JP", but I don't know that this is a consensus of Japanese. --=20 nayuta -- 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 |