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

[Markus Mützel]

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

Sorry it looks like I misunderstood what you were asking for. And I am afraid
I still don't understand.

To stay with the mkdir example: I didn't find a gnulib function which would
handle the wide character API automatically. That doesn't necessarily mean
that it doesn't exist. I just couldn't find it.
I thought I did "the next best thing" and created a wrapper function that does
that for us. That wrapper is octave::sys::octave_mkdir. Should this be done
differently?

Since there is no guarantee for wchar_t's size, it can change in the future.
At the moment Windows uses UTF-16 encoded strings. But that might change in
the future. (In fact, MS might consider using UTF-32 to ultimately achieve the
original goal of "one wchar_t per character".) I figured the best thing would
be to use gnulib's "u8_conv_to_encoding" which is able to convert from UTF-8
encoded char's to "wchar_t" (whatever its size is or will be). If anything
should change we could rely on gnulib to do the right thing.
I created "u8_to_wstring" and "u8_from_wstring" just to make it easier to use
gnulib's "u8_conv_to_encoding" and "u8_conv_from_encoding".

    _______________________________________________________

Reply to this item at:

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

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