|
From: | Markus Mützel |
Subject: | [Octave-bug-tracker] [bug #60306] Error running files in a folder containing letters that aren't encoded in system locale |
Date: | Fri, 9 Apr 2021 05:42:55 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.114 Safari/537.36 Edg/89.0.774.75 |
Follow-up Comment #24, bug #60306 (project octave): I pushed a partial fix here that afaict will allow to execute files in the current working directory even if it contains characters that cannot be encoded in the locale charset: https://hg.savannah.gnu.org/hgweb/octave/rev/9f0649b4e912 The change will be part of Octave 7 which will probably be released some time next year. This still won't allow to add paths containing non-encodable characters to the search path. A "proper" fix will probably be to switch to using std::filesystem::canonical (and get rid of all the work-arounds we currently have for Windows). _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?60306> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |