On Apr 7 22:01, neomjp wrote:
> On 2009/04/07 3:07, Corinna Vinschen wrote:
> > > I would nevertheless be glad if you would write something up about them,
> > > so we have it in the records should we ever re-examine this issue.
>
> Just for information. Sorry it has become very long... I
>
On 2009/04/07 3:07, Corinna Vinschen wrote:
> > I would nevertheless be glad if you would write something up about them,
> > so we have it in the records should we ever re-examine this issue.
Just for information. Sorry it has become very long... I
thought I should write some background in
On Apr 7 02:51, neomjp wrote:
> On 2009/04/06 20:04, Corinna Vinschen wrote:
> > > After some long mulling over this problem, I gave up on supporting JIS.
>
> > > So, I removed JIS support from Cygwin again. Given that SJIS and eucJP
> > > are both available, this shoudn't pose a big problem for
On 2009/04/06 20:04, Corinna Vinschen wrote:
> > After some long mulling over this problem, I gave up on supporting JIS.
> > So, I removed JIS support from Cygwin again. Given that SJIS and eucJP
> > are both available, this shoudn't pose a big problem for Japanese users.
Ok, I understand
On Apr 4 02:32, neomjp wrote:
> LANG=en_US.ISO-2022-JP
> 000 71 71 0e e4 b8 80 0a
> q q so d 8 nul nl
> 007
> This must be identical to:
> 000 71 71 1b 24 42 30 6c 1b 28 42 0a
> q q esc $ B 0 l esc ( B nl
> 013
After som
On Apr 4 14:48, Andy Moreton wrote:
> On Sat 04 Apr 2009, Corinna Vinschen wrote:
> > On Apr 3 21:20, Corinna Vinschen wrote:
> >> On Apr 4 02:32, neomjp wrote:
> >> > [...]
> >> > But it failed for JIS/ISO-2022-JP and eucJP. (It was represented as
> >> > ASCII SO(0x0e)/UTF-8 sequence).
> >> >
On Sat 04 Apr 2009, Corinna Vinschen wrote:
> On Apr 3 21:20, Corinna Vinschen wrote:
>> On Apr 4 02:32, neomjp wrote:
>> > [...]
>> > But it failed for JIS/ISO-2022-JP and eucJP. (It was represented as
>> > ASCII SO(0x0e)/UTF-8 sequence).
>> >
>> > What is going wrong here? What makes the file
On Apr 3 21:20, Corinna Vinschen wrote:
> On Apr 4 02:32, neomjp wrote:
> > [...]
> > But it failed for JIS/ISO-2022-JP and eucJP. (It was represented as
> > ASCII SO(0x0e)/UTF-8 sequence).
> >
> > What is going wrong here? What makes the file name conversion from
> > UTF-16 to these character s
On Apr 4 02:32, neomjp wrote:
> I used this Corinna's tiny program
> (http://sourceware.org/ml/cygwin/2009-04/msg00053.html )
> to create a file with a name containing a CJK character and tested
> how setting LANG works.
>
> I changed 0x20ac to 0x4e00 (). This is one of the
> characters used in a
On 2009/04/02 22:46, Corinna Vinschen wrote:
> > Btw., it's really not tricky to create a filename with special
> > characters:
I used this Corinna's tiny program
(http://sourceware.org/ml/cygwin/2009-04/msg00053.html )
to create a file with a name containing a CJK character and tested
how setting
10 matches
Mail list logo