Bug 154851 - Cannot type any non-korean key like punctuation marks or spaces or backspace on asian(korean) input mode
Summary: Cannot type any non-korean key like punctuation marks or spaces or backspace ...
Status: RESOLVED NOTOURBUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.4.6.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: CJK-Korean
  Show dependency treegraph
 
Reported: 2023-04-17 02:47 UTC by greenscarf005
Modified: 2024-03-19 03:23 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
this demonstrates how non-korean keys are unable to be typed on korean input with keyboard overlay. (2.40 MB, video/mp4)
2023-04-17 02:50 UTC, greenscarf005
Details

Note You need to log in before you can comment on or make changes to this bug.
Description greenscarf005 2023-04-17 02:47:17 UTC
Description:
When typing asian characters, i'm unable to type any punctuation marks such as: spaces, commas(,), periods(.), quotation marks("), and, additionally, backspace also does not work. the only way to type such punction marks is to press ESC, which converts typing mode to english. 

Steps to Reproduce:
1. open libreoffice writer.
2. set default language to korean.
3. change input mode to korean (you should be using korean compatible layout. normally it's called 한/영 key (korean/english key) and bound to right alt key.
4. write any korean.
5. while still in korean mode, try to type any non-korean key, such as: punctuation, spaces, or backsapces.

Actual Results:
on korean mode, it is impossible to type any punctuation mark or spaces or backspaces. only korean characters are typeable.
when pressing ESC, it automatically reverts to english. this is problemetic since any accidental ESC means another 한/영 key to switch to korean.

Expected Results:
input mode should not prohibit user from typing non CJK letters.
in other words, in asian text mode, user should be able to freely type backspaces, spaces or other punctuation marks.
in other words, user should be able to freely type punctuation marks whenever it's asian or non-asian.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.4.6.2 / LibreOffice Community
Build ID: 40(Build:2)
CPU threads: 12; OS: Linux 6.2; UI render: default; VCL: kf5 (cairo+xcb)
Locale: ko-KR (ko_KR.UTF-8); UI: ko-KR
Ubuntu package version: 1:7.4.6-0ubuntu0.22.10.1
Calc: threaded

Operating System: Kubuntu 22.10
KDE Plasma Version: 5.27.0
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.6
Kernel Version: 6.2.10-060210-generic (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics
Memory: 30.7 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2
Manufacturer: HP
Product Name: Victus by HP 15L Gaming Desktop TG02-0xxx
Comment 1 greenscarf005 2023-04-17 02:50:11 UTC
Created attachment 186707 [details]
this demonstrates how non-korean keys are unable to be typed on korean input with keyboard overlay.

attached video demonstration of the issue.
Comment 2 wjsim 2024-03-18 16:03:29 UTC
Hi there, thank you for reporting the bug.

I went ahead and changed the default languages for document as Korean, however I am not able to reproduce the bug. I can type Korean fine and other punctuations or spaces or backspaces seem to function properly. Could you possibly provide a bit more detail on what you mean by setting default language to Korean?

Version: 24.2.1.2 (X86_64) / LibreOffice Community
Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac
CPU threads: 16; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win
Locale: ko-KR (en_US); UI: en-US
Calc: CL threaded

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 6a064b1967e06e40be40817deff99d00c1a8554f
CPU threads: 16; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win
Locale: ko-KR (en_US); UI: en-US
Calc: CL threaded
Comment 3 greenscarf005 2024-03-19 03:23:43 UTC
Hi, this issue was caused by using the kime IME (https://github.com/Riey/kime). Currently I reverted to using IBUS or FCITX, which does not have this issue.