From Fedora Project Wiki
(Initial Changes for IBus 1.5.21)
 
(typo)
 
(8 intermediate revisions by 3 users not shown)
Line 36: Line 36:
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
-->
-->
* Tracker bug: <will be assigned by the Wrangler>
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1732128 #1732128]
* Release notes tracker: <will be assigned by the Wrangler>
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/366 #366]


== Detailed Description ==
== Detailed Description ==
Line 83: Line 83:
<!-- 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?-->
<!-- 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/8503 #8503] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- 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.  
<!-- 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 -->
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 -->
Line 101: Line 101:
== How To Test ==
== How To Test ==
# Create `$HOME/.config/ibus/Compose` with the following context [1]
# Create `$HOME/.config/ibus/Compose` with the following context [1]
# Restart ibus-daemon
# Restart ibus-daemon (execute command "ibus restart")
# Launch gedit and type Multi_key-t-o-w-e-r
# Launch gedit and type Multi_key-t-o-w-e-r


Line 109: Line 109:
<Multi_key> <t> <o> <w> <e> <r>  : "🗼"
<Multi_key> <t> <o> <w> <e> <r>  : "🗼"
</pre>
</pre>
{{admon/note|Configure Mult_key on your keyboard in GNOME desktop|Run `gnome-tweaks`, go to "Keyboard & Mouse", configure "Compose key" and you can check the behavior with `xev` command}}


<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.  
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.  
Line 125: Line 127:


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->


== User Experience ==
== User Experience ==
Line 171: Line 172:
-->
-->


[[Category:ChangePageIncomplete]]
[[Category:ChangeAcceptedF31]]
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) -->  
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) -->  
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
 
[[Category:SelfContainedChange]]
<!-- Select proper category, default is Self Contained Change -->
<!-- [[Category:SelfContainedChange]] -->
[[Category:SystemWideChange]]

Latest revision as of 10:31, 10 September 2019


IBus 1.5.21

Summary

IBus 1.5.21 will extend the current compose typing.

  1. IBus will extend the compose key sequences less than 255 characters.
  2. IBus will extend the compose outputs more equal than one characters.

Owner

Current status

Detailed Description

The current IBus accepts the compose key sequences less than 7 characters due to the internal fixed buffer size, E.g. Multi_key-O-R are three characters and the sequence can output "®" but Multi_key-Multi_key-o-i-i-i-n-t are eight characters and the sequence is not enabled in IBus. This release will extend this limitation to 255 characters.

The current IBus outputs one compose character only and size is limited in 16bits. E.g. "®" is one character and it can be output and "🗼" is one character but the size is extended the upper limit of 16bits and the output is not enabled in IBus. This release will delete the limitation of the character lengths and the size will be extended to 32bits.

Benefit to Fedora

The users won't have to mind those compose limitations above and X11 compose does not have the limitations.


Scope

  • Proposal owners:
  • Other developers: N/A
  • Release engineering: #8503 (a check of an impact with Release Engineering is needed)
  • Policies and guidelines: N/A
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

Users can update their local compose file in $HOME/.config/ibus/Compose or $HOME/.XCompose to extend the compose table and need to restart ibus-daemon.


How To Test

  1. Create $HOME/.config/ibus/Compose with the following context [1]
  2. Restart ibus-daemon (execute command "ibus restart")
  3. Launch gedit and type Multi_key-t-o-w-e-r

"🗼" is output.

[1]:

<Multi_key> <t> <o> <w> <e> <r>  : "🗼"
Note.png
Configure Mult_key on your keyboard in GNOME desktop
Run gnome-tweaks, go to "Keyboard & Mouse", configure "Compose key" and you can check the behavior with xev command


User Experience

Users can reuse the user compose file of X11 to IBus. The X11 system compose file has been loaded by the desktop locale since the previous IBus version.

Dependencies

This change effects all IBus engines but rebuilds are not needed.


Contingency Plan

  • Contingency mechanism: Drop the feature in Fedora 31 and postpone it to Fedora 32
  • Contingency deadline: Beta freeze
  • Blocks release? No
  • Blocks product? No

Documentation

TBD

Release Notes