Skip to content
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

Closed
mike-fabian opened this issue Dec 11, 2024 · 6 comments
Assignees

Comments

@mike-fabian
Copy link
Owner

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.

@mike-fabian mike-fabian self-assigned this Dec 11, 2024
@mike-fabian mike-fabian moved this to In Progress in Mike’s project Dec 11, 2024
mike-fabian added a commit that referenced this issue Dec 14, 2024
Resolves: #570
([ENHANCEMENT] Offer additional engines which do simple ibus-m17n emulation by default)

Resolves: #569
([BUG] setup tool may crash when changing the sound file)
mike-fabian added a commit that referenced this issue Dec 14, 2024
Resolves: #570
([ENHANCEMENT] Offer additional engines which do simple ibus-m17n emulation by default)

Resolves: #569
([BUG] setup tool may crash when changing the sound file)
mike-fabian added a commit that referenced this issue Dec 14, 2024
Resolves: #570
([ENHANCEMENT] Offer additional engines which do simple ibus-m17n emulation by default)

Resolves: #569
([BUG] setup tool may crash when changing the sound file)
mike-fabian added a commit that referenced this issue Dec 15, 2024
Resolves: #570
([ENHANCEMENT] Offer additional engines which do simple ibus-m17n emulation by default)

Resolves: #569
([BUG] setup tool may crash when changing the sound file)
mike-fabian added a commit that referenced this issue Dec 15, 2024
Resolves: #570
([ENHANCEMENT] Offer additional engines which do simple ibus-m17n emulation by default)

Resolves: #569
([BUG] setup tool may crash when changing the sound file)
mike-fabian added a commit that referenced this issue Dec 15, 2024
Resolves: #570
([ENHANCEMENT] Offer additional engines which do simple ibus-m17n emulation by default)

Resolves: #569
([BUG] setup tool may crash when changing the sound file)
mike-fabian added a commit that referenced this issue Dec 16, 2024
Resolves: #570
([ENHANCEMENT] Offer additional engines which do simple ibus-m17n emulation by default)

Resolves: #569
([BUG] setup tool may crash when changing the sound file)
@mike-fabian
Copy link
Owner Author

mike-fabian commented Dec 16, 2024

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 namaste using hi-itrans with the “normal” ibus-typing-booster engine where suggestions are shown, with using it in ibus-m17n (m17n:hi:itrans “Hindi (hi-itrans (m17n))”) where no suggestions are shown and the typed characters are committed as early as possible. Finally it shows using it with the tb:hi:itrans “Hindi (hi-itrans (Typing Booster))” engine which behaves exacly like the respective ibus-m17n engine, no suggestions are shown and the preedit is commited as early as possible:

Peek.2024-12-16.10-06.mp4

mike-fabian added a commit that referenced this issue Dec 16, 2024
Resolves: #570
([ENHANCEMENT] Offer additional engines which do simple ibus-m17n emulation by default)

Resolves: #569
([BUG] setup tool may crash when changing the sound file)
mike-fabian added a commit that referenced this issue Dec 16, 2024
Resolves: #570
([ENHANCEMENT] Offer additional engines which do simple ibus-m17n emulation by default)

Resolves: #569
([BUG] setup tool may crash when changing the sound file)
mike-fabian added a commit that referenced this issue Dec 17, 2024
Resolves: #570
([ENHANCEMENT] Offer additional engines which do simple ibus-m17n emulation by default)

Resolves: #569
([BUG] setup tool may crash when changing the sound file)
@mike-fabian
Copy link
Owner Author

@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!

@psads-git
Copy link
Contributor

psads-git commented Dec 17, 2024

Hi Mike,

Thank you for the update. I use ibus-typing-booster daily and quite extensively. If I notice anything wrong after updating, I will definitely let you know.

Best regards,

Paul

@mike-fabian
Copy link
Owner Author

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

@github-project-automation github-project-automation bot moved this from In Progress to Done in Mike’s project Dec 19, 2024
@psads-git
Copy link
Contributor

I can confirm, Mike, that ibus-typing-booster is working properly and as before.

@mike-fabian
Copy link
Owner Author

I can confirm, Mike, that ibus-typing-booster is working properly and as before.

Thank you very much!

mike-fabian added a commit that referenced this issue Dec 24, 2024
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.
mike-fabian added a commit that referenced this issue Dec 30, 2024
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.
mike-fabian added a commit that referenced this issue Dec 30, 2024
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.
mike-fabian added a commit that referenced this issue Jan 1, 2025
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

2 participants