Bug 88313
Summary: | man does'nt display accented characters | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Jacques Rodary <jrodary> |
Component: | man | Assignee: | Eido Inoue <havill> |
Status: | CLOSED WORKSFORME | QA Contact: | Ben Levenson <benl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | jshin |
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: | 2003-09-02 19:03:59 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
Jacques Rodary
2003-04-08 20:27:09 UTC
Reading my mail, I feel bugzilla has the same problem; LoL -:) Is there anybody out there (Pink Floyd, the Wall)? what locale are you using? (type "locale" at the command line) LANG=fr_FR@euro LC_CTYPE="fr_FR@euro" LC_NUMERIC="fr_FR@euro" LC_TIME="fr_FR@euro" LC_COLLATE="fr_FR@euro" LC_MONETARY="fr_FR@euro" LC_MESSAGES="fr_FR@euro" LC_PAPER="fr_FR@euro" LC_NAME="fr_FR@euro" LC_ADDRESS="fr_FR@euro" LC_TELEPHONE="fr_FR@euro" LC_MEASUREMENT="fr_FR@euro" LC_IDENTIFICATION="fr_FR@euro" LC_ALL= Still hoping for an answer. Thanks Try LANG=fr_FR.UTF-8@euro man ls not just LANG=fr_FR@euro I tried LANG=fr_FR.UTF-8@euro: it qgaves things like répertoires instead of répertoire. But LANG=fr_FR works, I am sure it didn't with RH7.3), and I still have the euro sign â¬. I don't understand, but thanks anyway. Is your terminal set to display UTF-8? If it isn't you're receive gargage. The reason fr_FR works and fr_FR@euro doesn't is because they use different character sets: fr_FR uses iso-8859-1 (aka Latin-1) and fr_FR@euro uses iso-8859-15 (aka Latin-9 or Latin-0) The default character encoding for Red Hat Linux 8 and beyond (for European language-- other languages (esp CJK) will be migrated to UTF-8 in later versions) is UTF-8, which is different from 7.3. I have been trying (very hard) to tell you that UTF8 does'nt work at all with any west european locale (and possibly others). Please try them. For your information, my last comment said ini works, but I have to use kde konsole (in gnome !!!).Gnome terminal won't accept fr_FR locale. > Is your terminal set to display UTF-8? > If it isn't you're receive gargage. reporter, you didn't answer this question. However, I confirmed that 'man' doesn't work the way it should. There are two problems. One of them is not the fault of man but that of less (see bug 88868). To see that, you can do the following: 1. $ env LC_ALL=fr_FR.UTF-8 xterm & 2. In a new xterm window, $ env LANG=fr_FR.UTF-8 man man -P more You'll see that letters with diacritic marks are rendered correctly 3. In the same xterm, $ env LANG=fr_FR.UTF-8 man man would not work. Because the default pager for 'man' is 'less -isr', this is a clear indication that 'less' is to blame. Now, what's the problem of 'man' I wrote about above? That is, it's not compliant to the POSIX-specified locale resolution-order. When LC_ALL is specified, it should have the highest priority, but it still selects the man page based on LANG. I'll file it as a separate bug. sorry. the first part of my comment #10 is wrong. I didn't relaize that JLESSCHARSET was set to 'ko'. With that unset, LANG=fr_FR.UTF-8 /usr/bin/man man works fine in a UTF-8 terminal. So, this bug as reported should be closed. On the other hand, I have a trouble with fr_FR (fr_FR@euro) in a ISO-8859-1 or ISO-8859-15 terminal. Letters with diacritic marks come up as question marks.Using '-P more' didn't change this. When I use fr_FR.ISO-8859-1 or fr_FR.ISO-8859-15, they come up correctly. Because '-P more' change didn't make any difference, I suspect that either man or groff is to blame for not using nl_langinfo(CODESET) but relying on parsing the value of LANG to determine the codeset. as per comment #11, closing |