octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #58717] Inputting Chinese Characters and Resiz


From: Markus Mützel
Subject: [Octave-bug-tracker] [bug #58717] Inputting Chinese Characters and Resizing windows will cause a mess
Date: Tue, 7 Jul 2020 04:24:37 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.116 Safari/537.36 Edg/83.0.478.58

Update of bug #58717 (project octave):

                  Status:                    None => Confirmed              

    _______________________________________________________

Follow-up Comment #1:

There are a few similar open bug reports: e.g. bug #58637, bug #47571.
Also there is bug #56224. Maybe something similar is happening here. One byte
of the (UTF-8 encoded) character might be interpreted as a command that
completely breaks the input. (At least this is what I guess is happening.)

We are using the Windows console behind the scenes to provide the command
window widget on Windows. Unfortunately, the Windows console has problems
handling UTF-8 (or any Unicode fwiw).
I've read somewhere that MS is considering the console to be legacy code
(can't find the source at the moment). So there is probably little hope that
they are going to invest much effort to improve that situation.

One thing that Octave might be able to do is to write our own (cross-platform)
widget for the command window. However, that is a major project (and
development in that direction seems to have stalled).
The current implementation works good enough on non-Windows platforms (which
use a different model that doesn't work on Windows). Most active developers
use Linux...

I guess what I wanted to say is: I can confirm that on Windows the command
window doesn't work correctly for international characters. But unfortunately
I don't know of a quick fix that would fix all the problems.

IIRC, we are using file handles to communicate with the console. Maybe if we
wrote a wrapper that forwarded those streams to the Windows console API
(ReadConsoleW and WriteConsoleW), some of the issues would be alleviated.
But all time and effort invested in this now might be in vain if we switched
to a cross-platform widget in the future...

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?58717>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]