NICE_HEADERS is a set of print-only enhancements, however the HTML
backend is invoked whenever an index is generated, so we should not
touch JADEOPTS directly and should instead modify the .tex-ps target
directly.
appropriate.
I've specifically left JKH's attribution for the "FreeBSD History"
section in tact, since this is a first person account of the history
of FreeBSD and as such the author needs to be identified in place.
This could probably be marked up differently, but its clear that this
section is different from all of the other "contributed by XXX" in the
Handbook.
Also add support for <sect1info> and <sect2info> to the stylsheet so
that these attributions get displayed as they have been.
call for help is listed on the third page of the printed Handbook or
on the top level index for the HTML version and it need not be
repeated here.
* End all list items with a period, not just some of them.
* Reword a couple of sentences so that they don't start with command
names.
* Reword a couple of confusing run-on sentences into more succinct
sentences with a separate <note> with additional information.
* Add a couple of missing words and remove some extra words to
construct sentences that make sense.
* Reworded paragraph with awkward "Either .. alternatively"
construction.
* Correct a reference to the Amanda port so that it looks good in
printed form. Dima's <port> tag would be helpful here.
* Fix a couple of other minor typos.
* Remove myself from list of chapter authors, since I didn't really add
very much.
* Add more <filename> and <varname> tags
* Use <varname> instead of <literal> around sysctl names
* Reword references to look better without the benefit of a hyperlink
- <para>Please see &man.ata.4;.</para>
+ <para>For more information, please see &man.ata.4;.</para>
* Use 'SoftUpdates' consistently.
* Saying that an "error message shows up in dmesg" is a bit cryptic for
new users, so explain that messages get sent to a system buffer that
is viewed with the dmesg command.
Placed applications in <application>
Placed commands in <command>
Placed hostnames in <hostid>
Placed usernames in <username>
Placed some terms in <literal>/<quote>
Places some commands in man entities
Changed some <filename> to <command> tags
Placed files in <filename>
Spelling:
linux -> Linux
pc -> PC
reckognized -> recognized
initialise -> initialize
behaviour -> behavior
mountpath -> mount path (to spell check nicely although mountpoint would
probably be more correct)
Reviewed by: murray
Local-file URLs are encoded as file://localhost/path/file which is
fine for HTML but this looks ugly when printed.
Add a function to chop off the "file://localhost" so that the above
URL would be printed as "/path/file" but still link to
"file://localhost/path/file" for HTML output.
Placed sh, bash, csh, tcsh in <command>
Placed commands in <command>
Placed options in <option>
Placed several commands in man entities
Placed several applications in <application>
Placed make vars/targets into <makevar>/<maketarget>
Placed filenames in <filename>
<literal>chmod()</literal> -> <function>chmod()</function>
Standardize:
ATT -> AT&T
endeavour -> endeavor
tcl -> Tcl
Reviewed by: murray
* Add chapter on kernel debugging (repo-copied from the Handbook)
* Change "Introduction" part with 4 empty chapters to a
"Introduction" chapter with 4 mostly empty <sect1>s.
* Combine many of the different <part>s that contain only one empty
<chapter> into larger <part>s.
* Add * in front of unfinished chapter names so its very clear what
needs to be worked on.
* Added some <filename> tags where appropriate.
Place some terms in <varname>
Change <emphasis> -> <varname> in some intstances
Place commands in <command> or man entitiy
Place applications in <application>
Place filenames in <filename>
Place hostnames in <hostid>
One instance of <quote> -> <errorname>
Spelling/Terminology Fixes:
ip -> IP address
IPs/ips -> IP addresses
cfg -> config
Unice -> Unix systems
Reviewed by: murray
dictionary, so it doesn't make sense to list common, every-day words
with well-known spellings. Besides, "can not" is a proper, albeit
confusing, construct. For example:
The quick brown fox can not jump over the lazy dog.
The above isn't saying that the fox isn't capable of jumping over the
dog, but rather that the fox is capable of *not* jumping over it
(e.g., it can walk around it). It is confusing (and should be
avoided), but nonetheless valid, English.
Reword a couple of run-on sentences to use better subject-verb
agreement.
Terminate all items in a list with a period, not just some of
them.
Add <username> and <application> tags as appropriate.
"pw(8) has the information"
doesn't look well without the benefits of a hyperlink. Reword this to:
"For more information, please see pw(8)."
Update example to change shells to zsh since tcsh is now in the base
system.
internet -> Internet
can not -> cannot
CD-ROM -> CDROM
cdrom -> CDROM
UNIX -> Unix
To be standardized with the rest of the doc tree.
Approved by: murray
Remove extra prompts from <screen> examples.
Remove lame text telling the user to "Forget about it" if a port is
broken.
Use absolute links since relative links don't mean much in PostScript
form.
