Bug 514112

Summary: Candidate history is not saved
Product: [Fedora] Fedora Reporter: Takanori MATSUURA <t.matsuu>
Component: ibus-anthyAssignee: Jens Petersen <petersen>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: i18n-bugs, petersen, phuang, tagoh
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-08-04 12:18:45 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:

Description Takanori MATSUURA 2009-07-28 03:59:45 UTC 
Description of problem:
Anthy cannot save candidate history in many case.


Steps to Reproduce:
1.type "複数分節でも、学習記録が残ることもあるようだ。"
2.type "カテゴリー別アーカイブ"

Actual results:
1. Only candidate history for "、", "学習", "。" was save in ~/.anthy/last-record2_default.utf8
2. Only candidate history for "アーカイブ" was save in ~/.anthy/last-record2_default.utf8

Expected results:
All candidate history should save in ~/.anthy/last-record2_default.utf8.

Additional info:
When I type same words on emacs with anthy-el, it works.  So I suppose there is a bug in ibus-anthy or ibus, not anthy itself.

I initially assign this bug to ibus-anthy.  If this bug is for ibus or other component, please change value of component.
Comment 1 Takanori MATSUURA 2009-08-04 11:44:07 UTC 
Bug 580358 seems to be similar.  But "私の" and "。" in the test case 3a of the bug 580358 comment #0 are recorded on my F11 machine.

I can test ibus-1.2.0.20090804-1.fc12 package if it is also generated for F11.
Comment 2 Takanori MATSUURA 2009-08-04 12:18:45 UTC 
(In reply to comment #1)
Oops,
Bug 580358 -> Bug 508358.

According to a certain BBS, a user reported that ibus-anthy-1.2.0.20090804-1.fc12 fixes this issue.


I'll close this bug as dup. of bug 508358.

*** This bug has been marked as a duplicate of bug 508358 ***