From Fedora Project Wiki
(Announcing the Change proposal)
m (Add trackers)
 
(3 intermediate revisions by 2 users not shown)
Line 25: Line 25:


== Current status ==
== Current status ==
[[Category:ChangeAnnounced]]
[[Category:ChangeAcceptedF34]]
<!-- 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 -->
Line 44: Line 44:
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
-->
-->
* FESCo issue: <will be assigned by the Wrangler>
* FESCo issue: [https://pagure.io/fesco/issue/2509 #2509]
* Tracker bug: <will be assigned by the Wrangler>
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1907575 #1907575]
* Release notes tracker: <will be assigned by the Wrangler>
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/615 #615]


== Detailed Description ==
== Detailed Description ==
Line 101: Line 101:
<!-- 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/9866 #9866]
<!-- 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 -->

Latest revision as of 18:15, 14 December 2020


kasumi-unicode

Summary

kasumi-unicode will be generated newly with kasumi.spec in kasumi project.

Owner

Current status

Detailed Description

anthy-unicode has been forked from anthy since anthy was no longer maintained in upstream. kasumi is one of the applications which link to the libraries of anthy. In case kasumi links to anthy, the private dictionary is located in $HOME/.anthy directory. In case kasumi links to anthy-unicode, the private dictionary is located at $XDG_CONFIG_HOME/anthy. I wish kasumi links to anthy-unicode newly but some other applications still use anthy. E.g. ibus-anthy uses anthy-unicode and $XDG_CONFIG_HOME/anthy. fcitx-anthy, scim-anthy, uim-anthy, gcim-anthy uses anthy and $HOME/.anthy. To keep the back compatibility while *-anthy will migrate to use anthy-unicode, kasumi.spec is going to generate kasumi twice to generate two kasumi binaries with different CFLAGS and LDFLAGS between anthy and anthy-unicode. kasumi-unicode will be generated to link to anthy-unicode. anthy-unicode enhances anthy for:

  1. internal data EUC-JP to UTF-8
  2. user dic in $HOME/.anthy to $XDG_CONFIG_HOME/anthy

Feedback

Benefit to Fedora

anthy-unicode saves the user dictionaries in the Freedesktop configuration directory $XDG_CONFIG_HOME. Contributers can develop anthy-unicode with UTF-8 words internally.

Scope

  • Proposal owners:
  • Other developers: AkiraTagoh (Fedora maintaier of kasumi)
  • Release engineering: #9866
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with Objectives:

Upgrade/compatibility impact

ibus-anthy will depend on anthy-unicode and kasumi-unicode instead of kasumi.


How To Test

  1. Enable ibus-anthy in your desktop
  2. Run /usr/libexec/ibus-setup-anthy
  3. Run kasumi-unicode from "Dictionary" tab in the dialog
  4. Register some words with kasumi-unicode

The user dictionary is saved in $XDG_CONFIG_HOME/anthy and ibus-anthy can use it.


User Experience

Users will run anthy-unicode-dic-tool --migrate in case that users need to migrate the user dictionary in $HOME/.anthy with one in $XDG_CONFIG_HOME/anthy.

Dependencies

ibus-anthy


Contingency Plan

  • Contingency mechanism: Revert the change of kasumi.spec and ibus-anthy will depends on kasumi.
  • Contingency deadline: Beta freeze
  • Blocks release? No
  • Blocks product? No

Documentation

Release Notes