Bug 76445 - elinks cannot display UTF-8
elinks cannot display UTF-8
Product: Red Hat Linux
Classification: Retired
Component: elinks (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
: 92222 100429 107352 117156 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2002-10-21 17:16 EDT by Christian Rose
Modified: 2007-04-18 12:47 EDT (History)
6 users (show)

See Also:
Fixed In Version: 0.9.1-2
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-05-28 04:20:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Makes UTF-8 I/O the default (532 bytes, patch)
2004-05-27 17:43 EDT, Daniel Hokka Zakrisson
no flags Details | Diff

  None (edit)
Description Christian Rose 2002-10-21 17:16:21 EDT
elinks seems to be unable of displaying UTF-8 (it's not available in the 
encoding menu at least), which is very unfortunate in a UTF-8 locale 
environment like is being installed by default in RHL 8.0. It would be great if 
elinks could support UTF-8.
Comment 1 Miloslav Trmac 2002-10-23 05:44:02 EDT
As a workaround, set character set to iso-8859-1 (or what you would
usually use), and run
        LC_ALL=your-locale_without_utf8 luit links
You get only 256 characters, but it works about as well as in RHL 7.3.
Comment 2 Tim Waugh 2003-07-22 06:44:17 EDT
*** Bug 100429 has been marked as a duplicate of this bug. ***
Comment 3 Tim Waugh 2003-10-17 06:34:47 EDT
*** Bug 107352 has been marked as a duplicate of this bug. ***
Comment 4 Tim Waugh 2004-03-11 11:43:50 EST
*** Bug 117156 has been marked as a duplicate of this bug. ***
Comment 5 Tim Waugh 2004-03-11 12:21:56 EST
Set UTF-8 I/O on in your terminal options -- does that make the
problem go away?
Comment 6 Barry K. Nathan 2004-03-13 23:59:53 EST
*** Bug 92222 has been marked as a duplicate of this bug. ***
Comment 7 Barry K. Nathan 2004-03-14 00:00:58 EST
In my case, at least, setting UTF-8 I/O in the terminal options does
make the problem go away.
Comment 8 Daniel Hokka Zakrisson 2004-05-25 17:34:26 EDT
This bug is still present on Fedora Core 2, in a no-X environment.
Comment 9 Daniel Hokka Zakrisson 2004-05-27 17:43:56 EDT
Created attachment 100644 [details]
Makes UTF-8 I/O the default

... and now that I've learned to read, turning on UTF-8 I/O does indeed make
the problem go away.
Comment 10 Tim Waugh 2004-05-28 04:20:29 EDT
Thanks.  Patch applied in 0.9.1-2.

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