[Octave-bug-tracker] [bug #52905] Can't manage paths that contain extended unicode characters

[Markus Mützel]

Follow-up Comment #4, bug #52905 (project octave):

At the moment Octave is transitioning from Qt4 to Qt5 for its GUI. Both handle
non-ASCII character just fine "behind the scenes".

Like you've already written, what the interpreter does is a separate thing.
I wouldn't say that Octave "misuses WinAPI". I've nowhere seen that Windows'
ANSI character API (the one that uses "char" and has "A" at the end of most
API function calls) is obsolete. In fact it would probably break a lot of
programs that are out there if it would be deprecated. And I believe that this
won't happen in quite some time from now.

The patch in bug #49118 changes the file IO of Octave's core to use Windows'
wide character API (the one that uses "wchar_t" and has "W" at the end of most
API function calls) in many places. If you have suggestions on how this should
be done, you are welcome to comment at that bug report.

    _______________________________________________________

Reply to this item at:

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

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