-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ENHANCEMENT] Offer additional engines which do simple ibus-m17n emulation by default #570
Comments
Simple engines to emulate ibus-m17n are available now in the branch release-candidate-2.26.26. Builds for Fedora are available here: https://copr.fedorainfracloud.org/coprs/mfabian/ibus-typing-booster/builds/ This video shows a comparison of typing Peek.2024-12-16.10-06.mp4 |
@psads-git Hi Paul, this new feature which I have implemented is surely not interesting to you as you want to continue using the “normal” typing booster for the completions. The new engines I implemented here are restricted do doing only simple transliteration, no completion, nothing fancy. But to implement this, I had to do a lot of changes all over the code. If I did a good job nothing at all should change for you if you update to the newest build from https://copr.fedorainfracloud.org/coprs/mfabian/ibus-typing-booster/builds/ (Currently 2.26.26). If anything changes for you or you notice any problems, please tell me! |
Hi Mike, Thank you for the update. I use Best regards, Paul |
Documentation for the new feature is in the rewritten chapter Simulate the behaviour of ibus-m17n: https://mike-fabian.github.io/ibus-typing-booster/docs/user/#2_3 |
I can confirm, Mike, that |
Thank you very much! |
ibus-typing-booster >= 2.27.0 also offers simple engines emulating the behaviour of the ibus-m17n engines, see: #570 ibus-m17n has an option `☑️ Use US keyboard layout` which some users of ibus-m17n might miss if they try to use the Typing Booster engines emulating ibus-m17n. To make the switch to Typing Booster easier for such users, I am adding the same option to Typing Booster here.
Resolves: #581 ibus-typing-booster >= 2.27.0 also offers simple engines emulating the behaviour of the ibus-m17n engines, see: #570 ibus-m17n has an option `☑️ Use US keyboard layout` which some users of ibus-m17n might miss if they try to use the Typing Booster engines emulating ibus-m17n. To make the switch to Typing Booster easier for such users, I am adding a similar option to Typing Booster here. Similar but better because it also solves some problems with that option in ibus-m17n.
Resolves: #581 ibus-typing-booster >= 2.27.0 also offers simple engines emulating the behaviour of the ibus-m17n engines, see: #570 ibus-m17n has an option `☑️ Use US keyboard layout` which some users of ibus-m17n might miss if they try to use the Typing Booster engines emulating ibus-m17n. To make the switch to Typing Booster easier for such users, I am adding a similar option to Typing Booster here. Similar but better because it also solves some problems with that option in ibus-m17n.
Resolves: #581 ibus-typing-booster >= 2.27.0 also offers simple engines emulating the behaviour of the ibus-m17n engines, see: #570 ibus-m17n has an option `☑️ Use US keyboard layout` which some users of ibus-m17n might miss if they try to use the Typing Booster engines emulating ibus-m17n. To make the switch to Typing Booster easier for such users, I am adding a similar option to Typing Booster here. Similar but better because it also solves some problems with that option in ibus-m17n.
typing-booster can already simulate the behaviour of ibus-m17n pretty closely as is described in this chapter of the user documentation:
This is done by switching off all of the fancy features typing-booster normally offers and restricting it to the basic functionality of m17n transliteration.
But as there is only one engine at the moment, if one restricts that one to simple m17n emulation, one looses all the nice features. It is not possible at the moment to have a simple engine doing only m17n transliteration and a “normal” engine with all the nice features at the same time.
Also, as quite a lot of settings have to be changed to reduce the functionality to m17n emulation, it is not obvious for users how do do that without reading the documentation.
And currently such an engine restricted to m17n emulation cannot be offered by default as it would be silly to restrict the "normal" typing booster engine by default.
The idea to fix that is to keep the "normal"
typing-booster
engine unchanged und unrestricted and in addition offer separate engines for m17n input methods which are by default restricted to doing only the m17n transliteration. But using the setup tool one can lift the restrictions even for the engines which are restricted by default. This makes it possible to have several fully functional typing booster engine with different settings.This could be used to split learning words per language as was requested in this issue:
#165
One could setup one instance of typing-booster for English and another one for Slovak and then the words learned are saved to different databases for these languages. Of course that makes it necessary switching engines when switching languages. I think in most cases it is better to use a single typing-booster engine for multiple languages to save time by not having to switch engines. But if one really wants different engines for different languages, that would be possible with this enhancement.
The text was updated successfully, but these errors were encountered: