|
From: | Mike Miller |
Subject: | [Octave-bug-tracker] [bug #54391] Incorrect result when attempting to type or paste UTF-8 Cyrillic text into octave CLI |
Date: | Thu, 26 Jul 2018 20:01:33 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0 |
Update of bug #54391 (project octave): Category: None => Libraries Status: None => Confirmed Summary: Incorrect result when attempting to cut and paste UTF-8 Cyrillic text into octave CLI => Incorrect result when attempting to type or paste UTF-8 Cyrillic text into octave CLI _______________________________________________________ Follow-up Comment #1: Confirmed, with 4.4 and with the development version. I think you are right that it is specific to Cyrillic characters. In fact it seems to be specific to Cyrillic characters whose UTF-8 encoding starts with the byte 0xD0. These are the 64 characters with UTF-16 code point U+0400 through U+043F. The first byte is being interpreted by the readline library as some kind of control character. On my system it seems to do something similar to the Up arrow key or the Ctrl+P binding. Running octave with --no-line-editing disables readline and allows this to work. Have you tried experimenting with different readline settings? _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?54391> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |