From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/20020625
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Go to "www.google.co.jp" with Konqueror.
2.Enter some japanese words and click search-button.
Actual Results: There are no results.
Expected Results: some results.
Galeon is OK.
Is this behavior anything like what is reported in Bug 62445?
>Is this behavior anything like what is reported in Bug 62445?
>>kinput2 status window doesn't show, but input and alternate selection works.
If you say "..and I could get the google-search-results",the answer is NO.
In Limbo,you'll see "kinput2 status window doesn't show, but input and
alternate selection works" again,but it's not so important.
The problem is "You can't get the google-results".
Look at these pictures:
1.Japanese words in google-search-box
You can't go directly,so please delete "()" and paste the addresses.
It appears that this bug is not Bug 62445, but a regression that behaves like
Bug 62446. Japanese entered text in Konqueror does not submit to the Google
search. However, Japanese pasted characters does submit, and so does a mixture
of Japanese and English characters.
It appears that Konqueror is submitting the form improperly in certain
circumstances. You can see this behavior by submitting Japanese text
immediately after it is written with kinput2. Watch the text within the URL
bar. Then try it after you cut & paste Japanese text into the Google search
textbox or mix Japanese and English characters. The search text shows up
incorrectly before the encoding in the former case, but properly after encoding
in the latter.
This bug will be fixed if you use qt-3.0.5.
I use latest Mandrake-Cooker now, and
I can search correctly with google search.
A few days ago (it used qt-3.0.4), I couldn't do it.
Also see http://www.kde.gr.jp/patch/
Japanese KDE users report about bugs in qt-3.0.3.
Fixed in rawhide.
Fix confirmed with qt-3.0.5-13.