[Octave-bug-tracker] [bug #49118] GUI editor cannot run file in folder name with umlaut

[Markus Mützel]

Follow-up Comment #45, bug #49118 (project octave):

As far as I can tell, gnulib won't use the wide character API on Windows
making it impossible (or very un-reliable) to access files and folder with
non-ASCII characters. One would have to convert the internal UTF-8 to the
locale specific code page which would loose characters that cannot be
represented in that codepage.
Using boost::Filesystem [1] could help since it seems to use the wide
character API internally. But that would add a huge new dependency to Octave
and need a (major?) re-write of the functions handling the file system access.
Would that be acceptable and preferred?

Meanwhile, I found that uniconv accepts "wchar_t" as a code page string. This
helps a lot when it comes to handling the different sizes of wchar_t on
different platforms and its corresponding encoding (UTF-16 vs UTF-32). And
hence eliminates the use of the Windows specific conversion functions. 
I also moved all system dependent functions to the sysdep files.
Please, see the attached patch.

[1]: http://www.boost.org/doc/libs/1_42_0/libs/filesystem/doc/index.htm

(file #39829)
    _______________________________________________________

Additional Item Attachment:

File name: bug49118_win32_wchar_t_API_v5.patch Size:26 KB


    _______________________________________________________

Reply to this item at:

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

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