Red Hat Bugzilla – Bug 82099
man output garbled
Last modified: 2007-04-18 12:50:06 EDT
Description of problem: Output from the man command is garbled. For example, from a telnet session: RPM(8) Red Hat Linux RPM(8) NAME rpm â<88><92> RPM Package Manager SYNOPSIS QUERYING AND VERIFYING PACKAGES: rpm {â<80><90>^Hâ<80><90>q|â<80><90>^Hâ<80><90>â<80><90>^Hâ<80><90>query} rpm {â<80><90>^Hâ<80><90>V|â<80><90>^Hâ<80><90>â<80><90>^Hâ<80><90>verify rpm â<80><90>^Hâ<80><90>â<80><90>^Hâ<80><90>import PUBKEY ... rpm {â<80><90>^Hâ<80><90>K|â<80><90>^Hâ<80><90>â<80><90>^Hâ<80><90>checks PACKAGE_FILE ... INSTALLING, UPGRADING, AND REMOVING PACKAGES: rpm {â<80><90>^Hâ<80><90>i|â<80><90>^Hâ<80><90>â<80><90>^Hâ<80><90>instal rpm {â<80><90>^Hâ<80><90>U|â<80><90>^Hâ<80><90>â<80><90>^Hâ<80><90>upgrad rpm {â<80><90>^Hâ<80><90>F|â<80><90>^Hâ<80><90>â<80><90>^Hâ<80><90>freshe Output in an Xterm session is also garbled, but different. Version-Release number of selected component (if applicable): man-1.5j-11 How reproducible: Always Steps to Reproduce: 1.man rpm 2. 3. Actual results: garbled output Expected results: clear output Additional info:
*** Bug 83020 has been marked as a duplicate of this bug. ***
*** Bug 83500 has been marked as a duplicate of this bug. ***
this is a groff/unicode error
This seems to work with the newest rpms in rawhide: groff-1.18.1-11 and man-1.5k-5 greetings, Florian La Roche
How do I access these updated modules?
Shouldn't errata be created for psyche?
No, normally only security updates are done. greetings, Florian La Roche
This fixed everything I can see but the apostrophe (') character. It displays as â<80><99>.
Please specify what exactly you are running, what versions and why this should be a problem. Thanks, Florian La Roche
I am running Red Hat 8.0 with groff 1.18.1-11 and man 1.5k-5. The command is man rpm.
Works for me with current versions. Probably a setup problem on your end to not have a UTF-8 console? Florian La Roche
How do I set up a UTF-8 console. The term type is vt100. How do I set up to use plain old ASCII?
> Probably a setup problem on your end to not have a UTF-8 console? Saying that it's a setup problem not to have something set up that almost nobody knows about seems , well, SILLY. BTW: my quickest workaround was to setenv LC_ALL=C This sets the local to old-style ascii, where everything seems to work much better (including a 50x increase in grep's speed in some instances)
Should be fixed with the rawhide packages of groff and man.
Closing due to user inactivity.