m17n-list
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Release announcement: ibus-typing-booster-2.27.0


From: Mike FABIAN
Subject: Release announcement: ibus-typing-booster-2.27.0
Date: Thu, 19 Dec 2024 17:01:49 +0100
User-agent: Gnus/5.13 (Gnus v5.13)

This is not about m17n directly but might be interesting to users of
ibus-m17n:

I made a new release of ibus-typing-booster

https://github.com/mike-fabian/ibus-typing-booster/releases/tag/2.27.0

which makes it very easy now to use it as a replacement for ibus-m17n.

It was already possible to setup ibus-typing-booster in a way to mostly
work like ibus-m17n does, though not 100% exact.

Now the emulation of ibus-m17n is 100% exact as far as I know (If there
are still any differences I would like to know which differences there
are and fix them if possible, but currently I am not aware of any
differences in user visible behaviour).

Documentation for the new feature is here:

Chapter “Simulate the behaviour of ibus-m17n”:
https://mike-fabian.github.io/ibus-typing-booster/docs/user/#2_3

Now it has become extremly easy to use ibus-typing-booster as an
alternative to ibus-m17n, for each m17n:language:name engine, Typing
Booster provides a corresponding tb:language:name engine with identical
behaviour:

$ ibus list-engine  | grep latn-post 
  tb:t:latn-post - t-latn-post (Typing Booster)
  m17n:t:latn-post - t-latn-post (m17n)
$ ibus list-engine  | grep hi-itrans
  tb:hi:itrans - hi-itrans (Typing Booster)
  m17n:hi:itrans - hi-itrans (m17n)
$

Using these preconfigured typing booster engines eliminates the need to set up
restrictions manually, allowing you to keep the “normal” Typing Booster
engine unrestricted for advanced features like completion,
spell-checking, predictions, and multilingual input. The “normal” Typing
Booster engine is still there and behaves as it always did:

$ ibus list-engine  | grep booster
  typing-booster - Typing Booster
$

-- 
Mike FABIAN <mfabian@redhat.com>
睡眠不足はいい仕事の敵だ。




reply via email to

[Prev in Thread] Current Thread [Next in Thread]