[Octave-bug-tracker] [bug #47571] Problem with umlaut in command line

[anonymous]

Follow-up Comment #24, bug #47571 (project octave):

The problem with the display is restricted to the GUI then; the UTF-8 chars
seem to render properly in CLI mode if the command window is configured to
accept UTF-8.

For the Qt GUI, I found these two pieces of information:

1. Set the locate to UTF-8, (re)save the entire Octave codebase as UTF-8 on
the user's machine, and compile everything from source. Qt *should* pick up
locale info and make the GUI work with UTF-8. [1] Does this make sense to
someone with Qt experience? If this is the case, then entering umlauted text
will also be solved by the GUI without any external hackery. This can be done
by the end user without changing the code base, but can also be an annoying
extra hoop for the end user to jump.

2. There is a Qt function called setCodecForCStrings, and it can be passed
"UTF-8" as an argument. [2] Is this something that the Octave GUI code should
have in a header file to "force" UTF-8 interpretation across the GUI? If this
alternative works, it could make life easier for Windows users and precompiled
binaries will also be UTF-8 aware.

Could someone with experience in Qt please comment here?

[1]: https://wiki.qt.io/Strings_and_encodings_in_Qt
[2]: http://doc.qt.io/qt-4.8/qtextcodec.html#setCodecForCStrings


The problem with entering an umlaut on the GUI could be potentially solved
with [1] above; entering it on the CLI is still an unsolved problem. Let me
read up more.

    _______________________________________________________

Reply to this item at:

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

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