Bug 471025 - documentation of the roff language is wrong
Summary: documentation of the roff language is wrong
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: groff
Version: 10
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Stepan Kasal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-11 13:22 UTC by Stepan Kasal
Modified: 2009-12-18 06:48 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-12-18 06:48:43 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Stepan Kasal 2008-11-11 13:22:39 UTC
groff(7) and groff_char(7) contains false information, namely:

groff_char(7):

section "ASCII Characters":
it says that \` is used to get the "Grave accent" printed; but the roff source is borked, so a left-quote is displayed instead of `
[please review the man page sources for similar errors]

section "Named Characters", sub sections "Accents" and "Quotes":
 \[ga]   grave            grave accent
 \[cq]   quoteright       single closing quote (ASCII 39)
 \[aq]   quotesingle      apostrophe quote

not true \(aq, apostrophe is the ASCII 39, and the grave accent is ASCII 0x60 == 96, which is not mentioned.

groff(7):
\’     The acute accent ´; same as \(aa.  Unescaped: apostrophe, right quotation  mark,  single  quote  (ASCII 0x27).
\‘     The grave accent `; same as \(ga.  Unescaped: left quote, backquote (ASCII 0x60).

Shall be:
\' The acute accent ´; same as \(aa.  Unescaped: single right quote (not in ASCII).
\` The grave accent ` (ASCII 0x27); same as \(ga.  Unescaped: single left quote (not in ASCII).

In this light, it is obvious that the paragraphs dedicated to these two chars under the heading CONTROL CHARACTERS need more work.

This list of misinformations is probably not complete; it only shows the types of the problem there; a thorough scrutiny is needed.

Comment 1 john5342 2008-11-11 13:35:33 UTC
This bug has been triaged

Comment 2 Bug Zapper 2008-11-26 05:11:15 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Bug Zapper 2009-11-18 08:49:38 UTC
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Bug Zapper 2009-12-18 06:48:43 UTC
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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