Bug 82598 - some man pages doesn't represent the "-" char correctly
some man pages doesn't represent the "-" char correctly
Status: CLOSED DUPLICATE of bug 80030
Product: Red Hat Linux
Classification: Retired
Component: man-pages (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Eido Inoue
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2003-01-23 16:39 EST by Need Real Name
Modified: 2007-04-18 12:50 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:51:21 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2003-01-23 16:39:51 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830

Description of problem:
the minus sign is not represented correctly in some man pages.
when giving the man command the "-" characther is represented as a small
quadrat and text is cluttered.

there also seems to be a problem with representation 
of swedish charachters in some cases, e.g:
swedish chars in outgoing mail (headers) is converted to several "currency" (eg.
Yen) chars

RH8.0 was installed with US-English as primary (system) language and Swedish as
additional language.

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

How reproducible:

Steps to Reproduce:
1.man iptables

Additional info:
Comment 1 Michael Lee Yohe 2003-01-27 10:53:55 EST
This is related to Bug 80030 where some terminals and applications only use
7-bit character sets (instead of the default system-wide setting of UTF8).  You
can correct the problem for English translated pages by following the steps
outlined within the referenced bug.
Comment 2 Eido Inoue 2003-02-07 15:12:26 EST

*** This bug has been marked as a duplicate of 80030 ***
Comment 3 Red Hat Bugzilla 2006-02-21 13:51:21 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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