Tuesday, May 14, 2024
8
rated 0 times [  8] [ 0]  / answers: 1 / hits: 1299  / 2 Years ago, fri, january 21, 2022, 8:52:33

I often type the same words in several applications:




  • Editor (emacs, vi)

  • Webbrowser

  • Shells



It would be great to have an autocomplete of the words I typed during the last week available in all the above applications.



Each of them has a way to improve the typing speed. But something at desktop level would be the best.



Example: "Continuous Integration". I want a fast way to type this word without changing the program which receives the input.



Is there already something like this?


More From » desktop-environments

 Answers
0

The solution to your request is Input Method.



What you have described is something familiar to most CJK language users. Let's review how input method works in current Linux systems.



The Input Method system



Here's a simple architecture for a common input method system:





NOTE: I snapshot this image from The X Input Method Protocol. Some of the arrows are irrelevant to following discussion.



Historically, XIM (the X Input Method protocol) was the only protocol. It's overly complex and lacks some desired features. So it's mostly abandoned, though compatibility is still provided by popular toolkits like GTK, Qt.



A modern input method system contains several parts:




  1. Client-side library support




    • typically implemented as a module loaded by toolkits (e.g. for GTK, see /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/)


  2. Input method server

  3. X server



How do these parts fit together?



A user types a key. X server receives the hardware event from evdev interface, composes a XEvent and sends to the application under keyboard focus. The application toolkit (GTK, Qt) input method module intercepts the event and passed the info to input method server. The input method server figures what the user may want and passes some text back to the IM module.



Now, let's talk about the architecture of the IM server.

An IM server typically consists of two parts:




  1. An IM framework which handles platform specific intricacies and provides a nice interface to IM engine and toolkit IM modules. It provides the IPC mechanisms used by the IM module, server and engine.

  2. Various IM engines do the actual work of transforming user-typed keys to desired text. IM engines can be shared libraries loaded by the IM server or independent processes communicating to the IM server.

  3. Auxiliary input method configuration programs provides friendly user interface for customizing the IM server and engine behaviors.



All in all, what an IM does is to transform what you type to something different and optionally provide predictions.



An example



We use ibus-pinyin here to type some Chinese characters.





The romanization of 汉语拼音 is han yu pin yin. At, first you need to type all these letters to get the four Chinese characters. But after a few times, you just need to type the four initial characters h y p y to get the Chinese character.



In the ibus-pinyin case, han yu pin yin is shortened to h y p y.

More advanced IM engines utilize statistical learning techniques to provide better prediction. Nothing can stop you from writing a English input method engine to provide a typing boost.



As a bonus, all toolkits have input method support except some plain old X programs. So this is a quite universal solution.






Thanks to Anders F. U. Kiær. Features / Typing-Booster | Fedora Project Wiki should be the answer


[#27616] Sunday, January 23, 2022, 2 Years  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
taigysel

Total Points: 33
Total Questions: 136
Total Answers: 114

Location: Singapore
Member since Wed, Jan 13, 2021
3 Years ago
;