[Octave-bug-tracker] [bug #42036] Files and directories with non-ASCII characters not handled correctly on Windows

[Tatsuro MATSUOKA]

Follow-up Comment #15, bug #42036 (project octave):

Torsten

How did you do that?
(I have build mxe-octave adding -DUNICODE and -D_UNICODE to the compile flags
in the Makefile and changed the codepage to 65001 in the terminal window.)

I have tried to add  -DUNICODE and -D_UNICODE in CFLAGS and CXXFLAGS in
src/octave-mk and built mxe-octave (4.0.0-rc4)  However, my results were
different. 

The ls command at codepage 932 (Japanese), ls command gives broken screen but
they are different from octave-4.0.0-rc4 on ftp alpha site.

After system('chcp 65001'), for me, ls command works perfect.
The system('type nihongo.m') represent Japanese characters but nihongo.m did
not work.

I could not handle path and file names which contain Japanese multibyte
character are not able to be handled.

MinGW page suggests to use wmain or _tmain and use wchar or tchar.
However the use of it loses portability of the code.

I cannot figure out what is the good solution for this matter.
  




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?42036>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/