https://bugs.kde.org/show_bug.cgi?id=450670
Bug ID: 450670
Summary: Compose key creates a dot and not the desired
character
Product: frameworks-kglobalaccel
Version: 5.86.0
Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kdelibs-b...@kde.org
Reporter: b...@twosixfour.net
Target Milestone: ---
SUMMARY
When the compose key is activated, an underlined middle dot character (·) and a
blank space next to it are shown. This seems to cause problems in various
places. Worst is in LibreOffice, where if the compose key is invoked at the end
of a line with other lines below it, after the key sequence is entered the
cursor just ends up on the next line and the · remains, while the character the
user tried to enter does not appear. (If done at the end of the final line of a
document or the middle of a line, the character still does appear properly.)
This makes editing very frustrating.
The display of the middle dot and space also seems to causes other issues, such
as when editing the names of files on the desktop. When the compose key is
invoked at the end of a file name, the cursor jumps to the beginning (but at
least the character can successfully be typed). This is also why I think that
this is not just a LibreOffice bug.
Using the compose key used to not show any visual feedback (I think? Maybe I'm
wrong there), so perhaps this problem was introduced when this feedback was
added.
(Apologies if this bug was not filed in the correct place.)
STEPS TO REPRODUCE
1. Open LibreOffice Writer
2. Hit Enter a few times to create some lines
3. Click on any line besides the last one
4. Invoke the compose key to make a special character
OBSERVED RESULT
A · will appear and stay there, while the cursor moves down to the next line.
EXPECTED RESULT
The special character the user wanted to make using the compose key should
appear.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 21.10
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
--
You are receiving this mail because:
You are watching all bug changes.
