Bug 111425 - Missing chunks of text in historical manpages
Summary: Missing chunks of text in historical manpages
Status: Open
Alias: None
Product: Documentation
Classification: Unclassified
Component: Manual Pages (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-09 20:20 UTC by Jerry Peek
Modified: 2024-04-30 03:45 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jerry Peek 2007-04-09 20:20:02 UTC
I've used the historical manpages -- especially 7th Edition and 4.3
Reno -- for years, thanks.  Today I'm reading the 4.3 Reno page diff3(1),
from http://www.freebsd.org/cgi/man.cgi?query=diff3&apropos=0&sektion=1&manpath=4.3BSD+Reno&format=html
.  It has a problem I've seen in some other pages (but not reported before):
some small bits of text are missing.

For instance, the second paragraph of DESCRIPTION begins like this:

Options are: Produces output in a form suitable as an input script for
the ed(1) utility.

Which option does that describe?  It doesn't say.  Another example is
in the FILES section:

FILES
     temporary files.  the executable.

I think that section should include /tmp/XXX and /usr/bin/diff3, or something.

Fix: 

I'm guessing that there's a macro call which isn't being read or handled
by the man-to-html converter.  For instance, the missing -e option might
have been coded as:

.XX -e
How-To-Repeat: Open the manual page I mentioned in Firefox 2.0.0.3, or probably in other browsers too.
Comment 1 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 07:58:41 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped
Comment 2 Chris Davidson 2024-04-30 03:45:16 UTC
This manual page is being rendered incorrectly.

Rationale:
1. The bug is quite old
2. It is for an Operating System 4.3 Reno that is no longer being updated
3. Important to have render anomalies evaluated and potentially addressed

My suggestion would be: To realign this bug to a non-doc component, maybe infrastructure?