In Plasma the Vietnamese keyboard layouts are rather peculiar; at least I’ve never heard of QDERTY or ADERTY, nor have seen anyone using them (They are quite old and reminiscent of the colonial age/90s). The main Vietnamese one in Plasma seems to be VNI. Though VNI is more efficient, Telex is more widely used especially for non-professional since it’s easier without massive compromise. (Telex is actually incorporated into our curriculum. )
Thus a large proportion of Vietnamese uses Telex, and though packages to support this exists, I think this should be natively added since I don’t see anything hindering its feasibility and considering me, a newbie learning Linux in general, this should be added to reflect the incoming trend: It’s long since Linux being a niche and professional-only OS, and this simple addition would help accommodate that.
Hi! I’m no expert in this domain, but just as a note for what it’s worth - in terms of how keyboard input is handled in Linux, I think Vietnamese Telex would be considered an “input method” as opposed to a keyboard layout. My understanding is that would be due to its being more than a mapping of keycodes to characters, but actually programmatically handling keystrokes itself, processing them, and then providing an end result character to the rest of the system.
Just mentioning in case it helps with further discussions or searching for solutions. I think that definition might have been a sticking point in a previous KDE Bugtracking System feature request on this topic: 480355 – Add Telex as an additional Vietnamese keyboard layout variant
Oh yes sorry, like I said before I’m not well-versed yet. They seem to be different and beyond XKB…
However an established way to do this seem to be installing the input method yourself: recommend one is ibus-bamboo:
Unikey also supports the Telex input method and is typically available on distributions for both the iBus and fcitx input method frameworks as ibus-unikey, fcitx5-unikey and/or fcitx-unikey.
Thanks for your input. I just switched to fcitx5 as well; ibus doesn’t seem to work very well on wayland for me; the icon tray keeps glitching and keyboard shortcut for switching input methods also didn’t work. Fcitx5 was a smooth experience. Thus I’d recommend fcitx5
https://github.com/fcitx/fcitx5
https://github.com/fcitx/fcitx5-bamboo
or
https://github.com/fcitx/fcitx5-unikey
Thanks everyone for your input.
Cảm ơn mọi người đã giúp đỡ
Nvm it’s broken again…
For some reason when I start up today fcix5 was not responding, as in both keyboard shortcuts and icon tray, the GUI is completely not working.
This diagnosis pops up when it starts up:
Fcitx should be launched by KWin under KDE Wayland in order to use Wayland input method frontend. This can improve the experience when using Fcitx on Wayland. To configure this, you need to go to “System Settings” → “Virtual keyboard” and select “Fcitx 5” from it. You may also need to disable tools that launches input method, such as imsettings on Fedora, or im-config on Debian/Ubuntu. For more details see Using Fcitx 5 on Wayland - Fcitx
An error message in log also:
DBus call error: org.freedesktop.portal.Error.NotFound Requested setting not found
But Googling said this is just a warning and can be dismissed.
