|
From: | Markus Mützel |
Subject: | [Octave-bug-tracker] [bug #59572] "system" doesn't work with non-ASCII characters on Windows |
Date: | Sun, 29 Nov 2020 12:58:15 -0500 (EST) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.67 Safari/537.36 Edg/87.0.664.47 |
Update of bug #59572 (project octave): Summary: "system" doesn't work for non-ASCII characters on Windows => "system" doesn't work with non-ASCII characters on Windows _______________________________________________________ Follow-up Comment #2: Attached is another (independent) patch for non-ASCII characters in commands in asynchronous mode on Windows. I still don't know how to fix the synchronous mode with output. The commands themselves seem to be executed using a pipe. That already works with non-ASCII characters. But if the output contains non-ASCII characters, it is broken currently. The key is probably to understand how `iprocstream` works in `run_command_and_return_output` here: https://hg.savannah.gnu.org/hgweb/octave/file/54509b7fddd3/libinterp/corefcn/toplev.cc#l104 Can it just inherit from `std::wios` instead of `std::ios` and everything will fall in place correctly? If that is the way to go, that would probably mean a lot of duplicated classes. Is there a better way to implement this? (file #50362) _______________________________________________________ Additional Item Attachment: File name: bug59572_CreateProcessW.patch Size:1 KB <https://file.savannah.gnu.org/file/bug59572_CreateProcessW.patch?file_id=50362> _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?59572> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |