From Fedora Project Wiki
Line 178: Line 178:


== Contingency Plan ==
== Contingency Plan ==
Revert changes back to ibus-bogo


<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Contingency mechanism: Revert comps and gnome-desktop3 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Contingency deadline: Beta release <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks release? No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next -->
* Blocks product? None <!-- Applicable for Changes that blocks specific product release/Fedora.next -->


== Documentation ==
== Documentation ==

Revision as of 20:27, 13 December 2020


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 and m17n-db
  • 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 the packages ibus-m17n and m17n-db 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

ibus-m17n and m17n-db

  • comps has to be updated
  • gnome-desktop3 has to be updated

Contingency Plan

Revert changes back to ibus-bogo

  • Contingency mechanism: Revert comps and gnome-desktop3
  • Contingency deadline: Beta release
  • Blocks release? No
  • Blocks product? None

Documentation

N/A (not a System Wide Change)

Release Notes