From Fedora Project Wiki
< Features
m (→Documentation: remove spam) |
|||
| (24 intermediate revisions by 3 users not shown) | |||
| Line 8: | Line 8: | ||
== Summary == | == Summary == | ||
<!-- A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release. --> | <!-- A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release. --> | ||
libkkc, a new Japanese Kana Kanji input library, will be available in Fedora 19, along with an IBus input method engine which uses libkkc as backend (ibus-kkc). ibus-kkc will be the default Japanese input method in place of ibus-anthy. | |||
== Owner == | == Owner == | ||
| Line 22: | Line 19: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/19 | Fedora 19 ]] | * Targeted release: [[Releases/19 | Fedora 19 ]] | ||
* Last updated: 2013- | * Last updated: 2013-03-19 | ||
* Percentage of completion: | * Percentage of completion: 100% | ||
<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. --> | <!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. --> | ||
| Line 38: | Line 35: | ||
** There are no library interface. That means it cannot easily be used by other input method frameworks than IBus, such as Fcitx and uim. | ** There are no library interface. That means it cannot easily be used by other input method frameworks than IBus, such as Fcitx and uim. | ||
libkkc and ibus-kkc will be | libkkc and ibus-kkc will be a better replacement of those. | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
| Line 47: | Line 44: | ||
== Scope == | == Scope == | ||
<!-- What work do the 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 the 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?--> | ||
* Import marisa-trie, libkkc, ibus-kkc packages to Fedora (done) | |||
* Make ibus-kkc as the default Japanese input method (done) | |||
* port necessary features like keybinding editor from other IMEs (done) | |||
* Import marisa-trie, libkkc, ibus-kkc packages to Fedora ( | |||
== How To Test == | == How To Test == | ||
| Line 78: | Line 74: | ||
== Dependencies == | == Dependencies == | ||
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature 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 feature)? --> | <!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature 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 feature)? --> | ||
* libkkc ( | * libkkc (packaged) | ||
* marisa | * marisa (packaged) | ||
== Contingency Plan == | == Contingency Plan == | ||
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. 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 "None necessary, revert to previous release behaviour." Or it might not. If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | ||
* | |||
* Keep ibus-anthy as the default Japanese input method | |||
== Documentation == | == Documentation == | ||
<!-- Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | <!-- Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | ||
* [https://bitbucket.org/libkkc/ project page] | * [https://bitbucket.org/libkkc/libkkc project page] | ||
* [https://gitorious.org/libkkc git repos] | * [https://gitorious.org/libkkc git repos] | ||
| Line 93: | Line 90: | ||
<!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --> | <!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --> | ||
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. --> | <!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. --> | ||
* ibus-kkc | * The default Japanese input method changed to ibus-kkc, which uses a new libkkc backend that provides a more intelligent Kana Kanji conversion method. It will speed up the user input of Japanese characters. | ||
== Comments and Discussion == | == Comments and Discussion == | ||
| Line 99: | Line 96: | ||
[[Category: | [[Category:FeatureAcceptedF19]] | ||
<!-- When your feature page is completed and ready for review --> | <!-- When your feature page is completed and ready for review --> | ||
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler --> | <!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler --> | ||
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | <!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | ||
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --> | <!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --> | ||
Latest revision as of 04:39, 10 December 2020
libkkc
Summary
libkkc, a new Japanese Kana Kanji input library, will be available in Fedora 19, along with an IBus input method engine which uses libkkc as backend (ibus-kkc). ibus-kkc will be the default Japanese input method in place of ibus-anthy.
Owner
- Name: Daiki Ueno
- Email: ueno at gnu.org
Current status
- Targeted release: Fedora 19
- Last updated: 2013-03-19
- Percentage of completion: 100%
Detailed Description
There are currently two options for typical users to input Japanese sentences: ibus-anthy or ibus-mozc. However, both have issues:
- ibus-anthy
- Anthy, the backend library, has been dead upstream for years.
- The accuracy is not good because of bugs in the core algorithm of Anthy.
- ibus-mozc
- Contributions to the input method are limited to Google employees.
- There are no library interface. That means it cannot easily be used by other input method frameworks than IBus, such as Fcitx and uim.
libkkc and ibus-kkc will be a better replacement of those.
Benefit to Fedora
- Users will get more intelligent and openly developed Japanese input method.
- Developers will be able to use libkkc easily from their input method frameworks.
Scope
- Import marisa-trie, libkkc, ibus-kkc packages to Fedora (done)
- Make ibus-kkc as the default Japanese input method (done)
- port necessary features like keybinding editor from other IMEs (done)
How To Test
- Try to add "Japanese (Kana Kanji)" input source from gnome-control-center Region panel.
- Enable "Japanese (Kana Kanji)" input source from the gnome-shell.
- Input some Japanese text, say "watashinonamaehanakanodesu", to input a Kana-string "わたしのなまえはなかのです"
- Type Space to convert it to a Kana-Kanji-mixed-string "わたしの名前は中野です".
User Experience
- With the libkkc back end, Japanese users can speed up the Kana Kanji input thanks to its high accuracy algorithm than ibus-anthy.
Dependencies
- libkkc (packaged)
- marisa (packaged)
Contingency Plan
- Keep ibus-anthy as the default Japanese input method
Documentation
Release Notes
- The default Japanese input method changed to ibus-kkc, which uses a new libkkc backend that provides a more intelligent Kana Kanji conversion method. It will speed up the user input of Japanese characters.