Bug 438662
Summary: | ordering of candidates is wrong in Zhu Yin | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Allison Lee <leemayee> | ||||||||
Component: | scim-tables | Assignee: | Caius Chance <K9> | ||||||||
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | medium | Docs Contact: | |||||||||
Priority: | low | ||||||||||
Version: | 9 | CC: | eng-i18n-bugs, petersen, phuang | ||||||||
Target Milestone: | --- | Keywords: | i18n | ||||||||
Target Release: | --- | ||||||||||
Hardware: | All | ||||||||||
OS: | Linux | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2008-06-19 06:39:52 UTC | Type: | --- | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Attachments: |
|
Description
Allison Lee
2008-03-24 10:00:32 UTC
Created attachment 298881 [details]
bad candidates on first page
Hi Peng, Would you know how Zhu Yin load in order? Is it rely on the order in the table files? I remember a frequency could be specified for every phrase in the table file. The table engine will short the candidates by frequency. Does the Zhu Yin table provide the correct frequencies for phrases or chars? Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Compared the Zhu Yin table file in rawhide and FC-4, "今" is lower than those characters in rawhide but it is the first candidate for "rup" in FC-4. The order in the table file should be the default order for the candidates to be shown on the look-up window. I need to confirm if latest Zhu Yin has character/phrase frequency mechanism which could adjust the candidate order from learning. Besides, generally frequently used chars like "今" should be at higher rank initially. We should have a more practical table file. Wondering how the order of characters in the latest table file referred to. The character order is changed on then: Revision 1.9 - (view) (download) (annotate) - [select for diffs] Mon Jan 16 07:06:14 2006 UTC (2 years, 5 months ago) by suzhe Branch: MAIN Changes since 1.8: +43763 -43501 lines Diff to previous 1.8 Update ZhuYin tables according to the latest table from CMEX. ( http://scim.cvs.sourceforge.net/scim/scim-tables/tables/zh/ZhuYin.txt.in?view=log#rev1.12 ) I haven't estimate the workload to revert to the version before this change, with all clean later fixes merged. Hi Allison, I could rearrange the candidate orders based on the table in FC-5. However, there are changes which made by upstream since then which might have minor effects on specific characters. For example, "兒" was moved from "-" to "-6". Then the candidate after 兒 will be moved up towards the head of candidate list. To ensure you have exact character always at exact location in your current Fedora release version as it was in FC-5, I suggest you recompile scim-tables with the ZhuYin.txt.in and ZhuYin-Big.txt.in copied over from FC-5 sources (tarball/src.rpm). Thank you very much. Decided to revert the Zhu Yin table to the one in FC-5. Due to the huge size of data (~58k entries), fixing the latest table manually by me alone isn't feasible to be finished in short period. Created attachment 309816 [details]
Zhu Yin table in FC-5.
Created attachment 309817 [details]
Zhu Yin table (Big) in FC-5.
Built to rawhide: http://koji.fedoraproject.org/koji/buildinfo?buildID=53197 Hi Caius, I compiled ZhuYin.txt.in and ZhuYin-Big.txt.in from FC-5 and Zhu Yin works fine now. Candidate orders are back to how they were. The position of "兒" is also correct. Thank you very much! You have been great in trying to get this problem fixed. |