From Fedora Project Wiki


Use ibus-m17n as the default IME for Vietnamese

Summary

The current default input method for Vietnamese is ibus-bogo. This should change to the ibus-m17n input method “m17n:vi:telex - telex (m17n)”

Owner

Current status

  • Targeted release: Fedora 34
  • Last updated: 2020-12-13
  • FESCo issue: <will be assigned by the Wrangler>
  • Tracker bug: <will be assigned by the Wrangler>
  • Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

The current Fedora default input method ibus-bogo seems to be not actively maintained and it doesn't work on Gnome Wayland. The bug has been reported already in Fedora 30, see:

https://bugzilla.redhat.com/show_bug.cgi?id=1690326

The ibus-m17n input method vi-telex.mim seems to do the same as ibus-bogo, see

https://bugzilla.redhat.com/show_bug.cgi?id=1690326#c12

Using vi-telex.mim via ibus-m17n seems to behave exactly like ibus-bogo.

If ibus-bogo offers no additional benefit, it is probably better to use ibus-m17n with vi-telex as the default input method for Vietnamese. ibus-m17n has to be maintained anyway. Therefore, this saves the effort of fixing the unmaintained ibus-bogo.

Feedback

Benefit to Fedora

Vietnamese input works again on Gnome-Wayland. Currently with ibus-bogo it is broken.

Scope

  • Proposal owners:
    • update default IME in comps @input methods
    • update langpacks-vi to use ibus-m17n
  • Other developers: gnome-desktop3 for default vi_VN input method
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with Objectives:

Upgrade/compatibility impact

The package installed by default will change from ibus-bogo to ibus-m17n for an installation in Vietnamese.

How To Test

Install Fedora in Vietnamese and check that the default input method is vi-telex with ibus-m17n.

User Experience

  • There should be very little difference in typing Vietnamese as ibus-bogo and ibus-m17n with vi-telex.mim behave the same.
  • The setup tool looks a little different.
  • Package sizes and dependent packages are different.
  • Memory usage is different.

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No
  • Blocks product? product

Documentation

N/A (not a System Wide Change)

Release Notes