(Fixed list items) |
No edit summary |
||
| (10 intermediate revisions by 4 users not shown) | |||
| 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 --> | <!-- 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 --> | ||
= IBus 1.5.19 <!-- The name of your change proposal --> = | = IBus 1.5.19 <!-- The name of your change proposal --> = | ||
{{Change_Proposal_Banner}} | |||
== Summary == | == Summary == | ||
| Line 38: | Line 41: | ||
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: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1598402 #1598402] | ||
* Release Notes tracking: [https://pagure.io/fedora-docs/release-notes/issue/190 #190] | |||
== Detailed Description == | == Detailed Description == | ||
| Line 46: | Line 51: | ||
Currently Ctrl-Shift-u feature of typing Unicode code point is consolidated in the emoji dialog because one shortcut key of Ctrl-Shift-e can cover the feature but the code point feature would not need to launch the dialog because the candidate character is only one so IBus 1.5.19 will separate the Ctrl-Shift-u feature from Ctrl-Shift-e one and both keybindings can be customizable with ibus-setup. | Currently Ctrl-Shift-u feature of typing Unicode code point is consolidated in the emoji dialog because one shortcut key of Ctrl-Shift-e can cover the feature but the code point feature would not need to launch the dialog because the candidate character is only one so IBus 1.5.19 will separate the Ctrl-Shift-u feature from Ctrl-Shift-e one and both keybindings can be customizable with ibus-setup. | ||
Currently IBus compose feature does not show anything until the output character is determined. IBus 1.5. | Currently IBus compose feature does not show anything until the output character is determined. IBus 1.5.19 will shows the pre-edit text during users compose a sequence. | ||
E.g. Multi_key-apostrophe-e outputs 'é' and shows the apostrophe as a character on the pre-edit until 'e' is typed. | E.g. Multi_key-apostrophe-e outputs 'é' and shows the apostrophe as a character on the pre-edit until 'e' is typed. | ||
| Line 92: | Line 97: | ||
<!-- 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/ | * Release engineering: [https://pagure.io/releng/issue/7582 #7582] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED 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 124: | Line 129: | ||
3. What are the expected results of those actions? | 3. What are the expected results of those actions? | ||
--> | --> | ||
* Search emoji | * Search a chracter with emoji annotations or Unicode name directly | ||
# Make sure ibus input source is being used | # Make sure ibus input source is being used | ||
# Type Ctrl-Shift-e | # Type Ctrl-Shift-e | ||
| Line 140: | Line 145: | ||
# Press Enter key and output the selected character | # Press Enter key and output the selected character | ||
* Show Compose preedit | |||
# Make sure ibus input source is being used | |||
# Type three characters of Multi_key, ', e | |||
# Compose preedit is shown and é is output | |||
== User Experience == | == User Experience == | ||
| Line 163: | Line 172: | ||
<!-- 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: Drop the feature in Fedora | * Contingency mechanism: Drop the feature in Fedora 29 and postpone it to Fedora 30 | ||
<!-- 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 freeze | * Contingency deadline: Beta freeze | ||
| Line 174: | Line 183: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
https://desktopi18n.wordpress.com/2018/08/23/ibus-1-5-19-is-released/ | |||
== Release Notes == | == Release Notes == | ||
| Line 182: | Line 191: | ||
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze. | Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze. | ||
--> | --> | ||
* Release Notes tracking: [https://pagure.io/fedora-docs/release-notes/issue/190 #190] | |||
[[Category: | [[Category:ChangeAcceptedF29]] | ||
<!-- 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 --> | ||
Latest revision as of 15:07, 27 June 2023
IBus 1.5.19
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.
Summary
IBus 1.5.19 will have two features.
- Move the input entry on IBus emoji dialog to the input entry on each application using IBus pre-edit text so that the focus event is not changed when the emoji typing is enabled
- Ctrl-Shift-u feature of typing Unicode code points is separated from Ctrl-Shift-e feature so that neither an additional dialog or popup window is needed.
- Typing compose keys will have a pre-edit text
Owner
- Name: Takao Fujiwara
- Email: fujiwara [at] redhat [dot] com
- Release notes owner:
Current status
- Targeted release: Fedora 29
- Last updated: 2023-06-27
- Tracker bug: #1598402
- Release Notes tracking: #190
Detailed Description
Currently Ctrl-Shift-e launches an IBus emoji dialog and users type emoji annotations in an input entry on the dialog and the input entry can convert the muti-byte annotation to an emoji character, besides ASCII annotation. However the dialog takes the current input focus in any desktop environments and also the dialog position cannot determined in Wayland because the dialog has no parent windows. IBus 1.5.19 will move the input entry on the emoji dialog to the current input context on each applications using IBus pre-edit feature. Users type emoji annotations on the pre-edit text after they type Ctrl-Shift-e and typing space key launches a lookup window to show emoji candidates.
Currently Ctrl-Shift-u feature of typing Unicode code point is consolidated in the emoji dialog because one shortcut key of Ctrl-Shift-e can cover the feature but the code point feature would not need to launch the dialog because the candidate character is only one so IBus 1.5.19 will separate the Ctrl-Shift-u feature from Ctrl-Shift-e one and both keybindings can be customizable with ibus-setup.
Currently IBus compose feature does not show anything until the output character is determined. IBus 1.5.19 will shows the pre-edit text during users compose a sequence. E.g. Multi_key-apostrophe-e outputs 'é' and shows the apostrophe as a character on the pre-edit until 'e' is typed.
Benefit to Fedora
Users can type either emoji annotation or Unicode names on the current application.
Users can see the composing text before the final committed text is output.
Scope
- Proposal owners:
IBusEngine class will be changed in ibus-libs package to handle Ctrl-Shift-e and Ctrl-Shift-u and it will effects all IBus engines.
- Other developers: N/A
- Release engineering: #7582 (a check of an impact with Release Engineering is needed)
- List of deliverables: N/A
- Policies and guidelines: N/A
- Trademark approval: N/A
Upgrade/compatibility impact
Users don't have to type Ctrl-Shift-e or Ctrl-Shift-u if they don't need the feature or users can delete the shortcut keys with ibus-setup.
How To Test
- Search a chracter with emoji annotations or Unicode name directly
- Make sure ibus input source is being used
- Type Ctrl-Shift-e
- Type "smile"
- Press Space key to convert the first emoji character
- Press Space key again to get more candidates with an IBus lookup window
- Press Ctrl-[f|b|n|p] to move the selected character
- Press Enter key and output the selected character
- Show emoji category list
- Make sure ibus input source is being used
- Type Ctrl-Shift-e
- Press Space key to show emoji category list
- Press Ctrl-[f|b|n|p] to move the selected character
- Press Enter key and output the selected character
- Show Compose preedit
- Make sure ibus input source is being used
- Type three characters of Multi_key, ', e
- Compose preedit is shown and é is output
User Experience
Ctrl-Shift-e and Ctrl-Shift-u features are available in X11, GTK, QT applications.
Two dimension lookup table of the emoji candidates is shown in Xorg environment, which provides more annotation information.
One dimension lookup table of the emoji candidates is shown in Wayland environment. It means the existing lookup window and there is no enhanced lookup tables in Wayland because GTK popup window takes the focus in Wayland without any parent windows.
Dependencies
This change effects all IBus engines but rebuilds are not needed.
Contingency Plan
- Contingency mechanism: Drop the feature in Fedora 29 and postpone it to Fedora 30
- Contingency deadline: Beta freeze
- Blocks release? No
- Blocks product? No
Documentation
https://desktopi18n.wordpress.com/2018/08/23/ibus-1-5-19-is-released/
Release Notes
- Release Notes tracking: #190