[Octave-bug-tracker] [bug #43099] utf-8 files: editor, command windows issues, workspace pane shows correctly

[Philip Nienhuis]

Follow-up Comment #34, bug #43099 (project octave):

Hmmm I lost track of where to post comments as regards these character
encoding stuff. So many bug reports about encoding & character display ...

With Hartmut's patch (file #38798) in bug #49118, qt4 and Markus' patch (file
#38784) here in bug #43099:

- on Win 10 the GUI terminal properly displays UTF8 input from Andreas' .xlsx
file in bug #49222 (file #38622)

- on Win7 however the terminal is still broken. As I wrote I think it is a
problem with Win7's cmd.exe. When encoding UTF-8 input through Markus
utf82unicode.m (see bug #49222) the contents are displayed properly.

My conclusion is that the display of non-ascii in Windows 7 is broken beyond
repair. JWE wrote in another bug report that he hopes to have the terminal
replaced by a pane/widget independent of bash or cmd.exe.  So it may be better
to wait for that to happen.

If you want I can upload the qt4 and qt5 builds (both have the same patches)
to my dropbox. Send me a private mail if you want the URLs.



    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?43099>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/