[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #49118] GUI editor cannot run file in folder n
From: |
Markus Mützel |
Subject: |
[Octave-bug-tracker] [bug #49118] GUI editor cannot run file in folder name with umlaut |
Date: |
Sat, 17 Dec 2016 20:36:05 -0000 |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:51.0) Gecko/20100101 Firefox/51.0 |
Follow-up Comment #39, bug #49118 (project octave):
Thank you very much for the feedback, Mike.
It was quite straight forward removing the C wrappers and introducing the
abstaction layer for fopen (see attached patch).
However, I am at a loss where the functionality for getting a UTF-16 wchar_t
from an Octave string should go. It would be nice to have something like
"wc_str" that would return a pointer to a wchar_t string corresponding to the
multi-byte string in std::string (like "c_str" does directly for char). Is
that what you meant? Where should something like that go? In the
octave_char_matrix class?
For the 8.3 paths: Is there already a class in Octave that is used for
representing file paths?
The conditionals in the file-ops header (still present) won't be needed
anymore when these two abstractions are implemented, I think.
I found that there is std::codecvt_utf8_utf16 in C++11. Thus, there is
probably an easy way to not rely on the WinAPI for the conversion between
UTF-8 (char, string) and UTF-16 (wchar_t, wstring). Is it OK to use features
that are not present in earlier versions of Standard C++?
(file #39058)
_______________________________________________________
Additional Item Attachment:
File name: bug49118_win32_wchar_t_API_v2.patch Size:10 KB
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?49118>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/