From Fedora Project Wiki
 
(9 intermediate revisions by the same user not shown)
Line 54: 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. -->
<!-- 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 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.
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.


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.
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.
Line 93: Line 93:


Provides Vietnamese input that should work across desktops including GNOME Wayland.
Provides Vietnamese input that should work across desktops including GNOME Wayland.
ibus-unikey also has less dependencies when installed under GNOME.


== 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]]
 
<!-- 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/issue/9907 #9907]
* Release engineering: [https://pagure.io/releng/issue/9907 #9907]
Line 110: Line 107:
* Trademark approval: N/A (not needed for this Change)
* 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. -->
<!-- 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 ==
== Upgrade/compatibility impact ==
Line 118: Line 112:


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
The package installed by default will change from ibus-bogo to the packages ibus-unikey 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 ==
== How To Test ==
Line 136: Line 131:


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
Install Fedora in Vietnamese and check that ibus-unikey are installed. The input method Unikey should be available:
1. After doing a Vietnamese installation of Fedora and check that ibus-unikey is installed.
The Unikey input method should be available:


<pre>
<pre>
$ ibus list-engine | grep unikey
$ ibus list-engine | grep Unikey
   unikey
   Unikey - Unikey
$
</pre>
</pre>


Then add the unikey input method in the gnome-control-center select it in the gnome-panel, open
2. Then it should be possible to add the Vietnamese Unikey input method in gnome-control-center.
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”.  
 
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”.


The following screenshots show how to add the ibus-m17n “m17n:vi:telex” input method and do that tests.
5. You should get the result: “Không có gì quí hơn độc lập tự do”.
ibus-unikey and ibus-m17n “m17n:vi:telex” behave the same but ibus-m17n “m17n:vi:telex” suffers from a problem in Wayland that characters are often disappearing while typing, that’s why we prefer ibus-unikey at the moment.
 
The following screenshots show how to add the ibus-unikey input method and do these tests.
ibus-unikey:


<gallery>
<gallery>
Line 167: Line 167:
-->
-->


* There should be very little difference in typing Vietnamese as ibus-bogo and ibus-unikey behave similarly, except that Unikey works much better under Wayland
* 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.


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


== 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 -->
ibus-unikey
* comps has to be updated


== Contingency Plan ==
== 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.  -->
<!-- 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. -->
<!-- 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

Current status

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

    Adding the ibus-unikey input method in the Gnome control centre

  • How to use the ibus-unikey input method.

    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.

Release Notes

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/ibus-unikey_as_default_Vietnamese_IME&oldid=606117"