Latest revision as of 16:10, 25 February 2021

Use ibus-unikey as the default IME for Vietnamese

Summary

This recommended default input method for Vietnamese will be changed from ibus-bogo to ibus-unikey.

Owner

Name: Mike Fabian
Email: <mfabian@redhat.com>

Current status

Targeted release: Fedora 34
Last updated: 2021-02-25
FESCo issue: #2527
Tracker bug: #1913431
Release notes tracker: #625

Detailed Description

The current Fedora recommended Vietnamese input method ibus-bogo seems not actively maintained, and doesn't work well currently with GNOME Wayland for some time.

Since the ibus-unikey input method seems to work better under Wayland and provides similar functionality, it is now recommended input method and installed for Vietnamese users.

Feedback

Benefit to Fedora

Provides Vietnamese input that should work across desktops including GNOME Wayland.

ibus-unikey also has less dependencies when installed under GNOME.

Scope

Proposal owners:
- update langpacks-vi to use ibus-unikey [done]

Release engineering: #9907

Policies and guidelines: N/A (not a System Wide Change)

Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

Upgrades are not affected, and ibus-unikey should be reasonably compatible with ibus-bogo for Vietnamese input.

How To Test

1. After doing a Vietnamese installation of Fedora and check that ibus-unikey is installed. The Unikey input method should be available:

$ ibus list-engine | grep Unikey
  Unikey - Unikey

2. Then it should be possible to add the Vietnamese Unikey input method in gnome-control-center.

3. Select Unikey in the input sources menu list in the GNOME panel.

4. Start gedit and type: “Khoong cos gif quis hown ddoocj laapj tuwj do”.

5. You should get the result: “Không có gì quí hơn độc lập tự do”.

The following screenshots show how to add the ibus-unikey input method and do these tests. ibus-unikey:

Adding the ibus-unikey input method in the Gnome control centre
How to use the ibus-unikey input method.

User Experience

Vietnamese users should not notice much difference in typing Vietnamese with ibus-unikey compared to ibus-bogo, except that Unikey works much better under Wayland.

The setup tool looks a little different: ibus-unikey does not depend on Qt.

Dependencies

None

Contingency Plan

None needed really, but we change back to ibus-bogo.

Contingency mechanism: Revert langpacks-vi to ibus-bogo
Contingency deadline: Beta release
Blocks release? No
Blocks product? None

Documentation

https://github.com/ibus/ibus-unikey

Release Notes

@@ Line 1: / Line 1: @@
 <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
-= Use ibus-m17n as the default IME for Vietnamese <!-- The name of your change proposal --> =
+= Use ibus-unikey as the default IME for Vietnamese <!-- The name of your change proposal --> =
 == Summary ==
@@ Line 7: / Line 7: @@
 Note that motivation for the change should be in the Benefit to Fedora section below, and this part should answer the question "What?" rather than "Why?". -->
-The current default input method for Vietnamese is ibus-bogo. This should change to the ibus-m17n input method “m17n:vi:telex - telex (m17n)”
+This recommended default input method for Vietnamese will be changed from ibus-bogo to ibus-unikey.
 == Owner ==
@@ Line 26: / Line 26: @@
 == Current status ==
-[[Category:ChangePageIncomplete]]
+<!-- [[Category:ChangePageIncomplete]] -->
+[[Category:ChangeAcceptedF34]]
 <!-- When your change proposal page is completed and ready for review and announcement -->
 <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
@@ Line 45: / Line 46: @@
 CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
 -->
-* FESCo issue: <will be assigned by the Wrangler>
+* FESCo issue: [https://pagure.io/fesco/issue/2527 #2527]
-* Tracker bug: <will be assigned by the Wrangler>
+* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1913431 #1913431]
-* Release notes tracker: <will be assigned by the Wrangler>
+* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/625 #625]
 == Detailed Description ==
@@ Line 53: / Line 54: @@
 <!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
-The current Fedora default input method ibus-bogo seems to be not actively maintained and it doesn't work
+The current Fedora recommended Vietnamese input method ibus-bogo seems not actively maintained, and [https://bugzilla.redhat.com/show_bug.cgi?id=1690326 doesn't work well] currently with GNOME Wayland for some time.
-on Gnome Wayland. The bug has been reported already in Fedora 30, see:
-https://bugzilla.redhat.com/show_bug.cgi?id=1690326
+Since the ibus-unikey input method seems to work better under Wayland and provides similar functionality, it is now recommended input method and installed for Vietnamese users.
-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 ==
@@ Line 100: / Line 92: @@
 -->
-Vietnamese input works again on Gnome-Wayland. Currently with ibus-bogo it is broken.
+Provides Vietnamese input that should work across desktops including GNOME Wayland.
+ibus-unikey also has less dependencies when installed under GNOME.
 == Scope ==
 * Proposal owners:
-** update default IME in comps @input methods
+** update langpacks-vi to use ibus-unikey [[https://bodhi.fedoraproject.org/updates/FEDORA-2021-d555822355 done]]
-** update langpacks-vi to use ibus-m17n and m17n-db
-<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
-* Other developers: gnome-desktop3 for default vi_VN input method <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
-* Release engineering: [https://pagure.io/releng/issues #Releng issue number] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Release engineering: [https://pagure.io/releng/issue/9907 #9907]
-<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.
-The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
 * Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
@@ Line 120: / Line 107: @@
 * Trademark approval: N/A (not needed for this Change)
 <!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://pagure.io/Fedora-Council/tickets/issues ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->
-* Alignment with Objectives:
-<!-- Does your proposal align with the current Fedora Objectives: https://docs.fedoraproject.org/en-US/project/objectives/ ? It's okay if it doesn't, but it's something to consider -->
 == Upgrade/compatibility impact ==
@@ Line 128: / Line 112: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-The package installed by default will change from ibus-bogo to the packages ibus-m17n and m17n-db for an installation in Vietnamese.
+Upgrades are not affected, and ibus-unikey should be reasonably compatible with ibus-bogo for Vietnamese input.
 == How To Test ==
@@ Line 146: / Line 131: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-Install Fedora in Vietnamese and check that the default input method is vi-telex with ibus-m17n.
+. After doing a Vietnamese installation of Fedora and check that ibus-unikey is installed.
+The Unikey input method should be available:
+<pre>
+$ ibus list-engine | grep Unikey
+  Unikey - Unikey
+</pre>
+. Then it should be possible to add the Vietnamese Unikey input method in gnome-control-center.
+. Select Unikey in the input sources menu list in the GNOME panel.
+. Start gedit and type: “Khoong cos gif quis hown ddoocj laapj tuwj do”.
+. You should get the result: “Không có gì quí hơn độc lập tự do”.
+The following screenshots show how to add the ibus-unikey input method and do these tests.
+ibus-unikey:
+<gallery>
+Screenshot-f34-add-ibus-unikey-input-method.png|Adding the ibus-unikey input method in the Gnome control centre
+Screenshot-f34-using-ibus-unikey-input-method.png|How to use the ibus-unikey input method.
+</gallery>
 == User Experience ==
@@ Line 160: / Line 167: @@
 -->
-* There should be very little difference in typing Vietnamese as ibus-bogo and ibus-m17n with vi-telex.mim behave the same.
+* Vietnamese users should not notice much difference in typing Vietnamese with ibus-unikey compared to ibus-bogo, except that Unikey works much better under Wayland.
-* The setup tool looks a little different.
-* Package sizes and dependent packages are different.
+* The setup tool looks a little different: ibus-unikey does not depend on Qt.
-* Memory usage is different.
 == Dependencies ==
 <!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
+None
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-ibus-m17n and m17n-db
-* comps has to be updated
-* gnome-desktop3 has to be updated
 == Contingency Plan ==
-Revert changes back to ibus-bogo
+None needed really, but we change 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.  -->
-* Contingency mechanism: Revert comps and gnome-desktop3  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Contingency mechanism: Revert langpacks-vi to ibus-bogo  <!-- 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. -->
 * Contingency deadline: Beta release <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
@@ Line 192: / Line 191: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-N/A (not a System Wide Change)
+https://github.com/ibus/ibus-unikey
+See also [[Changes/ibus-m17n_as_default_Sinhala_IME]].
 == Release Notes ==

Search

Changes/ibus-unikey as default Vietnamese IME: Difference between revisions