Mailinglist Archive: opensuse-m17n (5 mails)

< Previous Next >
Re: [opensuse-m17n] IBus's default preload engines are fixed
(2012/02/16 4:25), Takashi Iwai wrote:
> But what about users of systems with some ibus engines but
> in other locales?

Nothing happens. For example, even if Anthy is installed in a system with en_US locale, it is not added to the preload engine list because en_US does not match ja, which Anthy supports. A language supported by an engine is declared also in a XML file.

If there was any engines support languages such as en_US, it would be problem.


Fuminobu Takeyama

(2012/02/16 4:25), Takashi Iwai wrote:
At Thu, 16 Feb 2012 02:50:58 +0900,
Fuminobu TAKEYAMA wrote:

Hi,

I fixed problem that IBus's default preload engines does not work.
(maybe from 1.4?)
https://bugzilla.novell.com/show_bug.cgi?id=746612

Great, thanks!

Because of this problem, we had to open ibus-settings and add engines
into the preload engines list before using IBus.

Now, when the preload engine list is empty, for example, at the first
boot, the engine with the largest rank is selected for each language. If
Anthy (rank: 99) and Mozc (rank: 80) are installed then, in Japanese
environment, both of engines are preloaded and Anthy is selected as a
default engine.

Note that engines whose rank are 0 are not preloaded.


So, I would ask maintainers of engines to confirm each engine has an
appropriate rank value.
It can be found in "/usr/share/ibus/component/*.xml".

Do we need to distribute this fix via the online update?

A good question. For the new installation system, it'd be a really
good improvement. OTOH, if this would change suddenly the setup of
the already "working" system, one would regard it as a regression.

I guess CJK users should have already selected the list, so there will
be no impact by this update. But what about users of systems with
some ibus engines but in other locales?


thanks,

Takashi
--
To unsubscribe, e-mail: opensuse-m17n+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-m17n+owner@xxxxxxxxxxxx

< Previous Next >
List Navigation
Follow Ups