Bug 79356 - input text box on www.alc.co.jp does not show
Summary: input text box on www.alc.co.jp does not show
Status: RESOLVED UNMAINTAINED
Alias: None
Product: konqueror
Classification: Applications
Component: khtml (show other bugs)
Version: 3.2.1
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-09 22:55 UTC by Ken Deeter
Modified: 2012-06-19 17:09 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ken Deeter 2004-04-09 22:55:49 UTC
Version:            (using KDE KDE 3.2.1)
Installed from:    Gentoo Packages

Seems like many Japanese users are running into this bug. The page is a J->E translation dictionary, and when viewed with khtml, the main entry field (to enter the word to lookup) does not show. Mozilla works fine.

For non-Japanese readers, the box should show up in the blue banner at the top of the page, just to the right of the graphic containing hte text "on the web"

Seems like the actual html for the form is generated from javascript in the page. Not really sure where the problem is.
Comment 1 Ken Deeter 2004-09-20 18:40:39 UTC
I've discovered this is a problem with how javascript in the SJIS japanese encoding gets converted to unicode. With Qt's default setting, a ascii backslash character gets translated into a "yen" mark, which makes the javascript interpreter not treat it as a backslash escape character..

The workaround is to set the environment variable:
UNICODEMAP_JP="open-ascii"

as stated by the qt docs.. perhaps this could be included in the docs somewhere?
Comment 2 Maksim Orlovich 2007-06-08 21:36:30 UTC
Could you perhaps tell me how your locale is setup? 
Comment 3 Janek Bevendorff 2012-06-19 17:09:11 UTC
Message from the Bugsquad and Konqueror teams: This bug is closed as outdated, as we do not have the manpower to maintain the KDE3 version anymore. If you still can reproduce this issue with Konqueror 4.8.4 or later, please open a new report. Thank you for your understanding.