Bug 996335 - Chinese intelligent pinyin could not work well.
Summary: Chinese intelligent pinyin could not work well.
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: ibus-pinyin
Version: 19
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Peng Wu
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-13 01:24 UTC by 韩聪
Modified: 2013-08-16 08:01 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-16 08:01:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
the wrong input~~ (77.71 KB, image/png)
2013-08-13 01:24 UTC, 韩聪
no flags Details
my language setting...After delete the "Japanese Kana" input-method (35.54 KB, image/png)
2013-08-15 08:23 UTC, 韩聪
no flags Details

Description 韩聪 2013-08-13 01:24:57 UTC
Created attachment 785929 [details]
the wrong input~~

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.With the Intelligent Pinyin input method, I couldn't enter Chinese characters. 
2.If I use the Japanese input method at first, and turn to Chinese Pinyin, the Keyboard Layout will get wrong. 

Actual results:
I need changing to the  "Chinese zh" input-method, then back to Intelligent Pinyin, and success... 

Expected results:
Enter the right Chinese characters directly, at any time just in the right input method.

Additional info:

Comment 1 韩聪 2013-08-13 01:27:16 UTC
If I use the Japanese input method at first, and turn to Chinese Pinyin, the Keyboard Layout will get wrong, such as, type the "," but the "(" appears.

Comment 2 Peng Wu 2013-08-13 02:19:25 UTC
If I remember correctly, we changed most ime to use <layout>default</layout>, which doesn't change the keyboard layout when switching ime.

Guess the steps to reproduce is:
1. switch ibus-anthy;
2. switch ibus-pinyin;
3. try to input pinyin:
Did I miss something on the reproduce steps?

Comment 3 Peng Wu 2013-08-15 03:05:42 UTC
Please provide the output of the following command:
$rpm -qa "google-chrome*" "ibus*"

Comment 4 韩聪 2013-08-15 08:03:48 UTC
(In reply to Peng Wu from comment #3)
> Please provide the output of the following command:
> $rpm -qa "google-chrome*" "ibus*"

$ $rpm -qa "google-chrome*" "ibus*"
bash: -qa: command not found...
...

PS:To reproduce this bug I reported, I switch the input method to "Japanese Kana", with the key "h", "ク" appears, and I return to "Chinese Intelligent Pinyin", input the "h", also "ク" appears...So I have to switch to "Chinese zh", and then "Chinese Intelligent Pinyin", this time I got the correct result~
But why couldn't I turn from "Japanese Kana" to  "Chinese Intelligent Pinyin" directly?
Thanks~~:)

Comment 5 韩聪 2013-08-15 08:20:50 UTC
(In reply to Peng Wu from comment #3)
> Please provide the output of the following command:
> $rpm -qa "google-chrome*" "ibus*"

The "kana kanji" works well.:)And after I deleted the method "kana", I could not find it any more...

Comment 6 韩聪 2013-08-15 08:23:18 UTC
Created attachment 786861 [details]
my language setting...After delete the "Japanese Kana" input-method

Comment 7 fujiwara 2013-08-15 13:54:44 UTC
(In reply to 韩聪 from comment #4)
> (In reply to Peng Wu from comment #3)
> > Please provide the output of the following command:
> > $rpm -qa "google-chrome*" "ibus*"
> 
> $ $rpm -qa "google-chrome*" "ibus*"
> bash: -qa: command not found...

You should not type '&' which indicates the prompt for bash.

% rpm -qa "google-chrome*" "ibus*"

> PS:To reproduce this bug I reported, I switch the input method to "Japanese
> Kana", with the key "h", "ク" appears, and I return to "Chinese Intelligent
> Pinyin", input the "h", also "ク" appears...So I have to switch to "Chinese
> zh", and then "Chinese Intelligent Pinyin", this time I got the correct
> result~
> But why couldn't I turn from "Japanese Kana" to  "Chinese Intelligent
> Pinyin" directly?

I think we disable "Japanese Kana" in either gnome-control-center or ibus.
I wonder how you added "Japanese Kana" in ibus.

I suggest to use any Japanese input methods likes "Japanese (Kana Kanji)" or anthy instead of "Japanese Kana".

Did you install the latest gnome-control-center and ibus-kkc?
# yum install control-center ibus-kkc

If you really wish to use jp kana keymap, it would be better to change "default" layout to "us" layout in /usr/share/ibus/component/libpinyin.xml by manual.

Comment 8 韩聪 2013-08-16 04:51:11 UTC
When install Fedora19 I choose lots of Japanese input-method including "Japanese kana" and it seems like "Japanese Kana        ja3".Now I choose the "Japanese kana kanji"...Thanks.

(In reply to fujiwara from comment #7)
> (In reply to 韩聪 from comment #4)
> > (In reply to Peng Wu from comment #3)
> > > Please provide the output of the following command:
> > > $rpm -qa "google-chrome*" "ibus*"
> > 
> > $ $rpm -qa "google-chrome*" "ibus*"
> > bash: -qa: command not found...
> 
> You should not type '&' which indicates the prompt for bash.
> 
> % rpm -qa "google-chrome*" "ibus*"
> 
> > PS:To reproduce this bug I reported, I switch the input method to "Japanese
> > Kana", with the key "h", "ク" appears, and I return to "Chinese Intelligent
> > Pinyin", input the "h", also "ク" appears...So I have to switch to "Chinese
> > zh", and then "Chinese Intelligent Pinyin", this time I got the correct
> > result~
> > But why couldn't I turn from "Japanese Kana" to  "Chinese Intelligent
> > Pinyin" directly?
> 
> I think we disable "Japanese Kana" in either gnome-control-center or ibus.
> I wonder how you added "Japanese Kana" in ibus.
> 
> I suggest to use any Japanese input methods likes "Japanese (Kana Kanji)" or
> anthy instead of "Japanese Kana".
> 
> Did you install the latest gnome-control-center and ibus-kkc?
> # yum install control-center ibus-kkc
> 
> If you really wish to use jp kana keymap, it would be better to change
> "default" layout to "us" layout in /usr/share/ibus/component/libpinyin.xml
> by manual.

Comment 9 fujiwara 2013-08-16 08:01:30 UTC
OK.


Note You need to log in before you can comment on or make changes to this bug.