Bug 134499

Summary: doesn't show the CJK page correctly on UTF-8 locale
Product: [Fedora] Fedora Reporter: Akira TAGOH <tagoh>
Component: lynxAssignee: Tim Waugh <twaugh>
Status: CLOSED UPSTREAM QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: dickey, eng-i18n-bugs
Target Milestone: ---Keywords: i18n
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-12-07 11:23:38 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 Akira TAGOH 2004-10-04 03:34:49 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; ja-JP; rv:1.7.3)
Gecko/20041001 Debian/1.7.3-3

Description of problem:
lynx is going to download the euc-jp page instead of displaying the page.

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

How reproducible:
Always

Steps to Reproduce:
1.lynx http://www.yahoo.co.jp
2.
3.
    

Actual Results:  Alert!: euc-jp
text/html;charsetr=euc-jp D)ownload, or C)ancel

Expected Results:  show the euc-jp page

Additional info:

Comment 1 Akira TAGOH 2004-10-04 03:41:55 UTC
er, it happened on en_US.UTF-8. however that testcase doesn't even
work on ja_JP.UTF-8 locale. the help message on the bottom of screen
can show Japanese, though.

Comment 2 Akira TAGOH 2004-10-07 04:33:21 UTC
actually lynx doesn't work for CJK. for another testcase,

Korean testcase:
LANG=ko_KR.UTF-8 lynx http://kr.yahoo.com/

Result:
going to download the page.

Simplified Chinese testcase:
LANG=zh_CN.UTF-8 lynx http://cn.yahoo.com/

Result:
displaying broken strings

Traditional Chinese testcase:
LANG=zh_TW.UTF-8 lynx http://tw.yahoo.com/

Result:
displaying broken strings

Comment 3 Thomas E. Dickey 2004-10-15 19:18:03 UTC
Setting LANG doesn't help much - lynx doesn't translate
the page content (which is not UTF-8).  This is a known
issue, which I am working on.