[Octave-bug-tracker] [bug #60306] Error running files in a folder containing letters that aren't encoded in system locale

[Torsten Lilge]

Follow-up Comment #23, bug #60306 (project octave):

[comment #21 comment #21:]
> Yes, you could google how to fix it, change the folder name and what-not,
but this shouldn't be happening like it isn't for any other program out
there...
> 
> Also the fact that it says not such file rather than what actually is the
problem isn't very helpful.

I can understand that you would like to have a quick fix for this issue. But
please let me add a few comments:

* Nobody suggested that you should google how to fix it (or I have missed the
related post)
* Our suggestions to test without or with other special characters in the file
path were required to find the cause of the bug you are seeing. Otherwise
there is no way to fix this bug in future versions of octave.
* You are completely right, this bug should not happen. That's why we are
trying to find the cause and ways how to fix it.
* A program that can not find a file under a given location can not determine
why the file does not exist and can't give a more meaningful error message. In
your case, the program does not know that it has misinterpreted the provided
location due to encoding problems and is looking at the wrong location for the
file.

    _______________________________________________________

Reply to this item at:

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

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