Bug 68086
Summary: | Can't use Japanese words at Google-search with Konqueror | ||
---|---|---|---|
Product: | [Retired] Red Hat Public Beta | Reporter: | Need Real Name <utuhiro> |
Component: | kdenetwork | Assignee: | wdovlrrw <brosenkr> |
Status: | CLOSED RAWHIDE | QA Contact: | Ben Levenson <benl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | limbo | CC: | eng-asia-list, wtogami, ynakai |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-08-01 00:29:10 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: | |||
Bug Depends On: | |||
Bug Blocks: | 67217 |
Description
Need Real Name
2002-07-06 06:44:14 UTC
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
(h)ttp://www.geocities.jp/knee2525/google01.png
2.the result
(h)ttp://www.geocities.jp/knee2525/google02.png
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. |