[Octave-bug-tracker] [bug #39009] Dead key sequences incorrectly mapped on Windows terminals

[Philip Nienhuis]

Update of bug #39009 (project octave):

                Category:                     GUI => Interpreter            
              Item Group:                    None => Incorrect Result       
                 Summary: GUI: Quotes always repeated in Windows terminal =>
Dead key sequences incorrectly mapped on Windows terminals

    _______________________________________________________

Follow-up Comment #4:

It turns out it is the "dead" keys  ` ~ ' " ^ that are affected. Or rather:
dead key sequences.

I tried a few other keyboard layouts and found one where double quotes weren't
a dead key but single quotes were; using that layout the GUI terminal worked
OK for the double quotes.

Digging a bit more I see that dead key sequences are incorrectly mapped on
*all* Octave Windows terminals ever since at least Octave-3.2.4 (oldest I have
installed), no matter being built with MinGW, MXE, or MSVC. 
GUI and CLI both return wrong, but different results for dead key sequences.
The fact that dead keys are doubled in the current GUI terminal on Windows
looks to be just a more pronounced side effect. Admittedly it's an annoyance
rather than a showstopper.
This may have gone unnoticed because one normally doesn't need composed
characters in Octave terminals (maybe only in strings). The dead keys ~'"^
weren't in the way as an ensuing space would reveal them.

Intriguingly this is no issue at all on Linux, where I have US Intl keyboard
with dead keys as well. I even get the proper Euro symbol with AltGr-5 in the
GUI terminal (gets me a question mark in Octave terminals on Windows).

(Title and a few other fields adapted.)

    _______________________________________________________

Reply to this item at:

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

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