[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Multibyte treatment on command windows on Windows
From: |
Tatsuro MATSUOKA |
Subject: |
Re: Multibyte treatment on command windows on Windows |
Date: |
Mon, 13 Apr 2015 09:34:28 +0900 (JST) |
----- Original Message -----
> From: Tatsuro MATSUOKA
> To: "octave-maintainers
> Cc:
> Date: 2015/4/13, Mon 08:21
> Subject: Multibyte treatment on command windows on Windows
>
> Hello
>
> Octave gui editor only treats utf-8 for multibyte character,
> while command window on windows does not handle uff-8 mode on windows command
> console
> (codepage 65001).
>
> The situation is improved on version up from 4.0.0-rc1 to rc2.
> However it became same as rc1 on rc3.
>
> What happens between upgrade rc2 and rc2?
>
> Please come and discuss on the bug tracker.
>
> https://savannah.gnu.org/bugs/?44538
>
Sorry the previous post was sent without careful revise.
Octave gui editor only handles utf-8 and multibyte characters are also handled
by utf-8.
The command window on MS-windows does not handle uff-8 mode on windows command
console without any treatment. For example, in Japanese version windows, the
command window will open with code page 932 (Shift-JIS. Shift-JIS is
traditional Japanese encoding on windows (from MS-DOS). )
However, the command console on windows supports utf-8 by code page 65001.
Then from octave command prompt, "system('chcp 65001')" changes code page of
windows console.
(chcp: is a command which CHange(s) Code Page of console windows. )
I have reported the issues on https://savannah.gnu.org/bugs/?44538.
The situation is improved on version up from 4.0.0-rc1 to rc2.
However the situation on rc3 became back the same as that on rc3.
What happens between upgrade rc2 and rc3?
I wonder why improvement is lost on rc3
Please come and discuss on the bug tracker.
https://savannah.gnu.org/bugs/?44538
Tatsuro