You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
install ibus-bogo using some kind of hook in the buildscript
But that's not enough. When logged in, by default, no input method program (i.e. ibus) is configured for en_US nor vi_VN locale. That's why we have to setup im-switch. I figured the following out from its manpage:
Fork /etc/X11/xinit/xinput.d/ibus to /etc/X11/xinit/xinput.d/ibus-xim changing QT_IM_MODULE to xim
Use Debian's alternative system to set /etc/alternatives/xinput-all_ALL to be /etc/X11/xinit/xinput.d/ibus-xim
The second step could be changed so that we
create a new file at /etc/alternatives/xinput-vi_VN pointing to /etc/X11/xinit/xinput.d/ibus-xim and another file at /etc/X11/xinit/xinput.d/vi_VN pointing to the first file, just like what they did with /etc/X11/xinit/xinput.d/ja_JP. After that, ibus-bogo will only show up by default in Vietnamese locale. Anything else then the users have to configure ibus themselves.
This is how we are going to do it:
ibus-bogo
using some kind of hook in the buildscriptBut that's not enough. When logged in, by default, no input method program (i.e.
ibus
) is configured for en_US nor vi_VN locale. That's why we have to setupim-switch
. I figured the following out from its manpage:/etc/X11/xinit/xinput.d/ibus
to/etc/X11/xinit/xinput.d/ibus-xim
changingQT_IM_MODULE
toxim
/etc/alternatives/xinput-all_ALL
to be/etc/X11/xinit/xinput.d/ibus-xim
The second step could be changed so that we
/etc/alternatives/xinput-vi_VN
pointing to/etc/X11/xinit/xinput.d/ibus-xim
and another file at/etc/X11/xinit/xinput.d/vi_VN
pointing to the first file, just like what they did with/etc/X11/xinit/xinput.d/ja_JP
. After that,ibus-bogo
will only show up by default in Vietnamese locale. Anything else then the users have to configure ibus themselves.Having done that, we need to:
The text was updated successfully, but these errors were encountered: