On 01/28/2010 03:14 PM, Andy Koppe wrote:
Kazuhiro Fujieda:
Andy Koppe:
Another example is X11, which has its own locale system independent
from Cygwin's. There, "ja_JP" implies eucJP already. This means that
with LANG=ja_JP, xterm uses eucJP, while filenames and programs
currently use the syst
Kazuhiro Fujieda:
> Andy Koppe:
>> Another example is X11, which has its own locale system independent
>> from Cygwin's. There, "ja_JP" implies eucJP already. This means that
>> with LANG=ja_JP, xterm uses eucJP, while filenames and programs
>> currently use the system's ANSI codepage, i.e. CP932 o
On Jan 27 06:28, Andy Koppe wrote:
> 2010/1/27 Kazuhiro Fujieda:
> > The default character encoding in the Japanese locale has become
> > UTF-8 in other POSIX systems. In most of all Linux distributions,
> > the default is UTF-8. In OpenSolaris, the default is also UTF-8.
>
> Are you saying that p
>>> On Tue, 26 Jan 2010 18:28:53 +
>>> Andy Koppe said:
> Another example is X11, which has its own locale system independent
> from Cygwin's. There, "ja_JP" implies eucJP already. This means that
> with LANG=ja_JP, xterm uses eucJP, while filenames and programs
> currently use the system's AN
2010/1/27 Kazuhiro Fujieda:
> Andy said `Seems SJIS really isn't suited for Unix command line
> use.' I said there is no problem, no difference with EUC-JP, and
> no need to change the default.
That comment primarily referred to standard SJIS, with its mappings of
the ASCII backslash and tilde cod
>>> On Tue, 26 Jan 2010 18:06:15 +0100
>>> Corinna Vinschen said:
> As for the default charset, now that we get extended NLS
> support, there are packages out there which have messages
> files for ja_JP encoded in eucJP. These are not shown
> correctly if SJIS is the default.
The runtime library
2010/1/26 Corinna Vinschen:
>> Any users of Japanese version of Windows don't use eucJP as
>> typical euncoding scheme. It will cause unnecessary confusion.
>
> Well, you can always use "ja_JP.SJIS".
>
> As for the default charset, now
> that we get extended NLS support, there are packages out ther
On Jan 27 01:36, Kazuhiro Fujieda wrote:
> >>> On Sun, 24 Jan 2010 17:23:58 +0100
> >>> Corinna Vinschen said:
>
> > The Unix consensus is apparently EUC-JP and that's what Cygwin 1.7.2
> > will use as default as well. If you want UTF-8, just use "ja_JP.UTF-8".
>
> To change the default codeset
>>> On Sun, 24 Jan 2010 17:23:58 +0100
>>> Corinna Vinschen said:
> The Unix consensus is apparently EUC-JP and that's what Cygwin 1.7.2
> will use as default as well. If you want UTF-8, just use "ja_JP.UTF-8".
To change the default codeset of ja_JP to eucJP is ridiculous.
Any users of Japanese
2010/1/25 Corinna Vinschen :
> On Jan 25 01:00, Nayuta Taga wrote:
>> 2010/1/24 Corinna Vinschen :
>> > Nayuta, can you please test if the latest from CVS works for you even
>> > with LANG="ja_JP.SJIS"?
>>
>> Thank you for implementing CP932 and changing SJIS to an alias of CP932.
>> I'll test it t
On Jan 25 01:00, Nayuta Taga wrote:
> 2010/1/24 Corinna Vinschen :
> > Nayuta, can you please test if the latest from CVS works for you even
> > with LANG="ja_JP.SJIS"?
>
> Thank you for implementing CP932 and changing SJIS to an alias of CP932.
> I'll test it tomorrow.
Thanks.
> I prefer UTF-8
2010/1/24 Corinna Vinschen :
> 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 .SJIS charset as it
>> > is in 1.7.1, except that nl_langinfo(CODESET)
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 .SJIS charset as it
> > is in 1.7.1, except that nl_langinfo(CODESET) for it should return
> > "CP932" in
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 character
2010/1/24 Corinna Vinschen:
>> Something's going seriously wrong with this, and I'd suspect it's to
>> do with turning backslashes into yen symbols.
>
> Right. It occured to me tonight that this will not work from a
> filesystem point-of-view. The people who decided to overload backslash
> and ti
On Jan 24 10:37, Corinna Vinschen wrote:
> On Jan 23 22:31, Andy Koppe wrote:
> > Corinna Vinschen:
> > > I applied a patch which handles the characters 0x5c and 0cfe differently
> > > if the charset is set to "SJIS"
> >
> > Something's going seriously wrong with this, and I'd suspect it's to
> >
On Jan 23 22:31, Andy Koppe wrote:
> Corinna Vinschen:
> > I applied a patch which handles the characters 0x5c and 0cfe differently
> > if the charset is set to "SJIS"
>
> Something's going seriously wrong with this, and I'd suspect it's to
> do with turning backslashes into yen symbols.
Right.
Corinna Vinschen:
> I applied a patch which handles the characters 0x5c and 0cfe differently
> if the charset is set to "SJIS"
Something's going seriously wrong with this, and I'd suspect it's to
do with turning backslashes into yen symbols.
C:\Users\Andy>set LANG=C.SJIS
C:\Users\Andy>\bin\bash -
On Jan 23 15:51, Andy Koppe wrote:
> On 23 January 2010 15:07, Corinna Vinschen:
> > Ouch. I understand now. Standard SJIS is *really* different from
> > Microsoft CP932 in two code points:
> >
> > CP932 0x5c == U+005E
> > SJIS 0x5c == U+00A5
> >
> > CP932 0x7e == U+007E
> > SJIS 0x7e == U+
On 23 January 2010 15:07, Corinna Vinschen:
> Ouch. I understand now. Standard SJIS is *really* different from
> Microsoft CP932 in two code points:
>
> CP932 0x5c == U+005E
> SJIS 0x5c == U+00A5
>
> CP932 0x7e == U+007E
> SJIS 0x7e == U+203E
Aargh! I wonder what that would do to DOS paths
On Jan 23 14:50, Corinna Vinschen wrote:
> On Jan 23 14:49, Nayuta Taga wrote:
> > In short, '~' (U+007E TILDE) turns into U+203E (OVERLINE) when
> > LANG=ja_JP.SJIS.
> >
> > Then I looked into cygwin and subversion again.
> > (1) cygwin1.dll converts L"foo~" (UCS-2) to "foo~" (CP932).
> > (2) Bec
On Jan 23 14:49, Nayuta Taga wrote:
> Hi all,
>
> Please support CP932. Because CP932 is not equal to SJIS, I have
> problem using subversion when LANG=ja_JP.SJIS . With the attached
> patch and LANG=ja_JP.CP932, I can use subversion as expected.
>
> The problem is as follows:
>
> I have the f
Pardon me. I forgot to attach my patch.
2010/1/23 Nayuta Taga :
> Please support CP932. Because CP932 is not equal to SJIS, I have
> problem using subversion when LANG=ja_JP.SJIS . With the attached
> patch and LANG=ja_JP.CP932, I can use subversion as expected.
Index: newlib/libc/locale/locale
23 matches
Mail list logo
