m (→Scope) |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 98: | Line 98: | ||
== Scope == | == Scope == | ||
* Proposal owners: | * Proposal owners: | ||
** update langpacks-vi to use ibus-unikey | ** update langpacks-vi to use ibus-unikey [[https://bodhi.fedoraproject.org/updates/FEDORA-2021-d555822355 done]] | ||
* Release engineering: [https://pagure.io/releng/issue/9907 #9907] | * Release engineering: [https://pagure.io/releng/issue/9907 #9907] | ||
| Line 173: | Line 173: | ||
== Dependencies == | == 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)? --> | <!-- 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 --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
== Contingency Plan == | == Contingency Plan == | ||
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. --> | <!-- 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 | * 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. --> | <!-- 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 --> | * Contingency deadline: Beta release <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
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
See also Changes/ibus-m17n_as_default_Sinhala_IME.