Bug 70381 - man(8) output nearly illegible if TERM=dtterm or TERM=hpterm
Summary: man(8) output nearly illegible if TERM=dtterm or TERM=hpterm
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: man
Version: 8.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Eido Inoue
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-07-31 22:42 UTC by Brent Thompson
Modified: 2007-04-18 16:45 UTC (History)
2 users (show)

Fixed In Version: 1.5m2-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-02-19 17:12:49 UTC
Embargoed:


Attachments (Terms of Use)
Editted sysconfig file (95 bytes, text/plain)
2003-01-17 17:39 UTC, Peter Reeve
no flags Details

Description Brent Thompson 2002-07-31 22:42:09 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.79 [en] (X11; U; HP-UX B.11.11 9000/785)

Description of problem:
man(8) displays properly if TERM=xterm, but output is really screwed up if
TERM=dtterm or hpterm.  It worked properly in RedHat versions 6.* and 7.*.
(Maybe only the '-' character is bad -- I cannot remember now).

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


How reproducible:
Always

Steps to Reproduce:
1. connect to limbo system using dtterm or hpterm
2. run man(8) with any target page
3.
	

Actual Results:  Wherever there should be a '-' character, instead shows up some
hex character that 
displays as ordinary '-' in xterm, but in hpterm or dtterm it displays as 'a'
with tilde on top and 
spaces front and back.
It turns out there are enough of these characters that the man(8) output is
amazingly difficult to 
comprehend.

Expected Results:  '-' character should display as normal ordinary '-'
character.


Additional info:

Comment 1 Stephen Samuel 2003-01-03 23:48:24 UTC
It also seems to happen with kterm and xterm (using the xterm termcap), but 
gnome-terminal with the xterm termcap works OK. 

It appears that someone changed the gnom-terminal escapes and -- instead  of
creating a new termcap name, they just changed the xterm termcap and confused
just about every other xterm clone out there (including xterm).

GUH!

Comment 2 Stephen Samuel 2003-01-04 00:20:24 UTC
OK: I take it back: there's some change to man(1) that seems to be compatible 
with gnom-terminal but incompatible with the other terminals.

Both the termcaps and terminfo's for xterm are unchanged between 7.2 and 8.0 


Comment 3 Eido Inoue 2003-01-04 02:24:25 UTC
what locale (type "locale") are you running your tests in?

Comment 4 Stephen Samuel 2003-01-04 03:56:33 UTC
[samuel@algh1188y43bi samuel]$ locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE=C
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

Note: Setting 
export LC_ALL=C 
seems to solve the bug, as does 
export LC_ALL="en_US.iso885915"

which appears to be the default under 7.2
or
export LC_ALL="en_US"
which seems to be the setting under 7.3



Comment 5 Peter Reeve 2003-01-17 17:39:08 UTC
Created attachment 89425 [details]
Editted sysconfig file

Same problem with rubbish characters when invoking man from a KDE terminal.
Alright on GNOME or a terminal. Using LANG=en_GB.UTF-8. Corrected the problem
by manually editting the configuration file /etc/sysconfig/i18n. Changed
LANG="en_GB.UTF-8" to LANG="en_GB". This get set/reset by the System settings
language tool.

Comment 6 Eido Inoue 2004-02-19 17:12:49 UTC
seems to be fixed with the combo of terminfo stuff in curses 5.4 along
with the UTF-8 grokkin man-1.5m2 and i18nized nroff


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