Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 146365 - Strange (non-displayable) characters groff/man creates on utf8-systems
Summary: Strange (non-displayable) characters groff/man creates on utf8-systems
Status: RESOLVED DUPLICATE of bug 126361
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: utf8 herd (RETIRED)
URL:
Whiteboard:
Keywords:
: 146364 (view as bug list)
Depends on:
Blocks: 146315
  Show dependency tree
 
Reported: 2006-09-05 02:27 UTC by Matthias Schwarzott
Modified: 2008-02-24 18:10 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias Schwarzott gentoo-dev 2006-09-05 02:27:57 UTC 
When switching man/groff from cripled ascii-mode  to autodetect (utf8-capable) mode it creates some symbols not displayable on every system.

This works by deleting the -Tascii in NROFF command inside /etc/man.conf, See Bug #146315.

For my system man creates this chars:
* a bullet for lists: c2 b7 in utf8 - viewable for me but not for others
* a hypthen: e2 80 90 in utf8 - not viewable in kde's konsole for me - gives a highligted question mark in pure text-console with lat9w-16 font
Comment 1 Matthias Schwarzott gentoo-dev 2006-09-05 02:28:56 UTC 
*** Bug 146364 has been marked as a duplicate of this bug. ***
Comment 2 Matthias Schwarzott gentoo-dev 2006-09-05 02:36:58 UTC 
two double quotation marks:
left one: e2 80 9c
right one: e2 80 9d
both viewable in kde's konsole (Andale Mono) but not with lat9w-16 in text-console
Comment 3 SpanKY gentoo-dev 2006-09-05 08:13:39 UTC 
as i said, groff/man are known to not work properly ... i dont see any value in filing bugs about the issue; just wait for the next release
Comment 4 SpanKY gentoo-dev 2008-02-24 18:10:58 UTC 

*** This bug has been marked as a duplicate of bug 126361 ***