[Octave-bug-tracker] [bug #64447] Loads of package warnings when Octave install path contains umlaut

[Markus Mützel]

Update of bug #64447 (project octave):

                Category:                    None => Interpreter            
                  Status:                    None => Confirmed              
         Planned Release:                    None => 9.1.0 (current default)

    _______________________________________________________

Follow-up Comment #1:

I can confirm with a build from the current default branch on Windows 11.

The reason is most likely the way the list of files in a directory is queried.
Octave uses the POSIX functions `opendir`, `readdir`, and `closedir` for that
in its `octave::sys::dir_entry` class. On Windows, we are using the
replacement functions from gnulib for them. But those functions don't support
UTF-8 in char arrays on Windows.

One possible solution could be to replace those functions by a combination of
`FindFirstFileW` and `FindNextFileW` on Windows:
https://learn.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-findfirstfilew
https://learn.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-findnextfilew

If I understand correctly, this might not be just a cosmetic issue.
If users add paths containing non-ASCII characters to their load path, changes
to files in those paths might not be noticed by Octave. I.e., Octave might
still execute previously read files.



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?64447>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/