Aren/NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
e2d4a3ff6c
NetBSD/share/tmac/doc2html

1555 lines
32 KiB
Plaintext
Raw Normal View History

Add simple An handling. Modified version of a patch by Greg A. Woods in private mail. Closes my PR 29241.
2005-02-07 04:11:14 +03:00
.\" $NetBSD: doc2html,v 1.46 2005/02/07 01:11:14 wiz Exp $
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
.\"
.\" Copyright (c) 1998, 1999 The NetBSD Foundation, Inc.
.\" All rights reserved.
.\"
.\" This code is derived from software contributed to The NetBSD Foundation
.\" by Ross Harvey.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed by the NetBSD
.\" Foundation, Inc. and its contributors.
.\" 4. Neither the name of The NetBSD Foundation nor the names of its
.\" contributors may be used to endorse or promote products derived
.\" from this software without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS
.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
.ig
The first section of this package processes a large subset of the -mdoc macro
functions into HTML. All of the commonly used requests are implemented.
The second section implements -man (-man.old) macros. These are trivial
compared to -mdoc.
NOTES:
The initial purpose of these macros is to support distrib/notes.
It's very close, but not quite ready to do all of the man pages.
See src/distrib/notes/Makefile.inc for important groff command
examples. For HTML generation it is important to turn off overstrike
modes with -P-b -P-u -P-o.
TODO:
There are a few internal macros and other symbols that don't contain
an embedded `-'.
Need a tbl(1) command that generates html tables from tbl(1)
input. (Partially written.) For now, we just switch into <pre>
mode on .TS or .PS. Tbl input is very uncommon these days, anyway.
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
(-mdoc has the .Bl -column list, which eliminates most requirements
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
for tbl)
We should probably end all the html pages with an upward
pointing "contents" link, except right now there is nothing
to point to.
We need "intro" or "contents" pages for each man/man? (man/html?)
section.
WARNING! If you add a callable macro (or define an old one that
was missing) it MUST have a doc2html@@ alias. (Scan for @@ to see.)
..
.
Fix a number of bugs and and start over again on the style sheet.
2002-02-07 03:59:18 +03:00
.if dError .Error - multiple inclusion of doc2html
.
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
.de TS
<pre>
..
.de TE
Fix a number of bugs and and start over again on the style sheet.
2002-02-07 03:59:18 +03:00
. DEBUG .tm TE
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
</pre>
..
.de PS
<pre>
..
.de PE
Fix a number of bugs and and start over again on the style sheet.
2002-02-07 03:59:18 +03:00
. DEBUG .tm PE
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
</pre>
..
.
.nr doc-stackp 0
.de doc-push
. ds doc-stack-rq-\\n[doc-stackp] \\$1
. nr doc-stack-ln-\\n[doc-stackp] \\n[.c]
. nr doc-stackp +1
..
.
.de doc-pop
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
. ie \\n[doc-stackp]<=0 .Error Extraneous \\$1 request
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. el .nr doc-stackp -1
. ds doc-pop-tmp1 \\*[doc-stack-rq-\\n[doc-stackp]]
. if !\\*[doc-pop-tmp1]\\$1 \{\
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
. tm Need \\*[doc-pop-tmp1] before \\$1
. Error See line \\n[doc-stack-ln-\\n[doc-stackp]]
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. \}
..
.
.de doc-rlookup
. if !r\\$1 \{\
. ie \\w\\V[\\$1] .nr \\$1 \\V[\\$1]
. el .nr \\$1 \\$2
. \}
..
.
.de doc-slookup
. if !d\\$1 \{\
. ie \\w\\V[\\$1] .ds \\$1 \\V[\\$1]
. el .ds \\$1 \\$2
. \}
..
.
.doc-rlookup DOC_DEBUG_MODE 0
Invert the default of DOC_XR and generate an href anchor by default. Also, assume that any man page called "index.html" will actually be installed (sigh) as "xindex.html", which is what bsd.man.mk actually does now.
2002-02-07 04:59:14 +03:00
.doc-rlookup DOC_XR 0
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
.doc-slookup DOC_MANROOT ..
.
.nr in-pre 0
.nr HTML 1
.pl 1i
.po 0
.in 0
.nf
.nh
.nr list-level 0
.de ce
. ie \\$1 \{\
<center>
. nr center-on \\$1
. it 1 doc-center-step
. \}
. el . end-center
..
.nr center-on 0
.de end-center
. it
. if \\n[center-on] </center>
. nr center-on 0
..
.
.de doc-center-step
<br>
. nr center-on -1
. ie \\n[center-on]<=0 .end-center
. el .it 1 doc-center-step
..
.
.ds copy &copy;
.ds > &gt;
.ds < &lt;
.ds >= &gt;=
.ds <= &lt;=
Fix bug with html < and > chars found by Alan Barrett.
1999-01-17 15:17:11 +03:00
.ds Lt &lt;
.ds Gt &gt;
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
.ds & &amp;
.ds _ &nbsp;
.ds q &quot;
.ds body-params bgcolor="#FFFFFF" text="#000000"
.ds document-title
.ds title-section
.ds dot-de .de
.ds dot-dot ..
.ds sepstring \~
.ds doc-punct-result
.ds doc-punct { . , : ; ( ) [ ] }
.ds close-mode
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
.ds open-mode
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
.ds doc-anchor
Kill Nm-save warning.
1999-03-18 21:57:42 +03:00
.ds Nm-save
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
.ds T " x
* Sync .St with the main mdoc * Fix (some of) the bugs with .Fn
1999-06-01 22:25:15 +04:00
.ds tN <font\ size="-1">
.ds aa </font>
.ds Px \\*(tNPOSIX\\*(aa
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
.chop T
.nr doc-dosep 0
.nr r-lvl 0
.
.if !dMANROOT \{\
. ds MANROOT \V[MANROOT]
. if !\w\*[MANROOT] .ds MANROOT ..
.\}
.
.blm Pp
.
.
.de DEBUG
.if \\n[DOC_DEBUG_MODE] \\$*
..
.de Dd
. as document-title " \\$*
..
.de Dt
. as document-title " \\$*
..
.de Os
. as document-title " \\$*
. init-html
..
.\"----------------------------------------------------------------------
Fix a number of bugs and and start over again on the style sheet.
2002-02-07 03:59:18 +03:00
.\" troff requests we delete
.
.rm wh
.
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
.\" troff requests we translate
Fix a number of bugs and and start over again on the style sheet.
2002-02-07 03:59:18 +03:00
.
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
.rn br br-real
.rn sp sp-real
.rn fi fi-real
.rn nf nf-real
Fix a number of bugs and and start over again on the style sheet.
2002-02-07 03:59:18 +03:00
.
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
.de br
Fix a number of bugs and and start over again on the style sheet.
2002-02-07 03:59:18 +03:00
. if \\n[in-pre]=0 <br>
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
..
.de sp-nice-try-ross
. ie !\\n(.$ <br>
. el .ie '\\$1'1' <br>
. el \{\
. if !\\n[in-pre] <pre>
. nr sp-tmp \\$1v-1v
. if \\n[sp-tmp]>0 .sp-real \\n[sp-tmp]u
. if !\\n[in-pre] </pre>
. \}
..
.\" Although the above probably works, the following is a lot simpler. It
.\" reduces the request to 1v, but why would you put more than one adjacent
.\" blank line in an html document anyway?
.de sp
. ie \\n[center-on] <!-- -->
. el <br><br>
..
.de end-preformat
Fix a number of bugs and and start over again on the style sheet.
2002-02-07 03:59:18 +03:00
. DEBUG .tm end-preformat \\n[in-pre]
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. if \\n[in-pre] </pre>
. nr in-pre 0
..
.de fi
Fix a number of bugs and and start over again on the style sheet.
2002-02-07 03:59:18 +03:00
. DEBUG fi
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. end-preformat
..
.de nf
<br>
<pre>
. nr in-pre 1
..
.\"
.\"----------------------------------------------------------------------
.\" Magic to open and close <body> and <html>
.\"
.de end-macro
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
. if \\w\\n[.z] .ab ERROR, unclosed quotation from line \
\\n[quotation_line]
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. br-real \" should be unnecessary...we have fill turned off
. fl \" more paranoia
</font></body>
</html>
. br-real
. fl
..
.em end-macro
.de init-html
<html>
Improve appearance, tone down the .Sh size, define a <style> for color headings, etc. Please feel free to fiddle with this stuff, people...
1999-03-09 09:25:58 +03:00
<head>
<title>
Fix a number of bugs and and start over again on the style sheet.
2002-02-07 03:59:18 +03:00
\\*[document-title]\\$*
Improve appearance, tone down the .Sh size, define a <style> for color headings, etc. Please feel free to fiddle with this stuff, people...
1999-03-09 09:25:58 +03:00
\\*[title-section]
</title>
<style type="text/css">
<!--
body { margin-left:4%; }
Fix a number of bugs and and start over again on the style sheet.
2002-02-07 03:59:18 +03:00
H1, H2, H3, H4, H5 {
color: maroon; padding: 4pt; margin-left: -4%;
border: solid; border-width: thin; width: 100%;
background: rgb(204,204,255)
}
Improve appearance, tone down the .Sh size, define a <style> for color headings, etc. Please feel free to fiddle with this stuff, people...
1999-03-09 09:25:58 +03:00
-->
</style>
</head>
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
<body \\*[body-params]>
\\*[dot-de] init-html
\\*[dot-dot]
..
.de Lk
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
. if \\n[.$]<1 .ab #\\n[.c]: Usage: .Lk href [ anchortext/punct ] ...
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. ds doc-href \\$1
. ds doc-anchortext \\$1
. shift
. if \\n[.$] \{\
. doc-checkpunct \\$1 \\*[doc-punct]
. if !\\n[doc-ispunct] \{\
. ds doc-anchortext \\$1
. shift
. \}
. \}
. ds doc-anchor <a href="\\*[doc-href]">\\*[doc-anchortext]</a>
. while \\n[.$] \{\
. doc-checkpunct \\$1 \\*[doc-punct]
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
. if !\\n[doc-ispunct] .ab #\\n[.c]: .link ... '$1' -- Huh?
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. as doc-anchor \\$1
. shift
. \}
. ds doc-tmp1 No
. nr doc-tmp-2 \\w^G\\*[doc-anchortext]^G
. nr doc-tmp-2 \\n[doc-tmp-2]/\\w'0'
. if \\n[doc-tmp-2]>=30 .ds doc-tmp1 D1
. \\*[doc-tmp1] \\*[doc-anchor]
..
.
.\".de mailto
.\"<a href="mailto:\\$1">\\$1</a>\\$2\\$3\\$4
.\"..
.
.de Ht
\\$*
..
.de Sh
. end-preformat
. init-html
Improve appearance, tone down the .Sh size, define a <style> for color headings, etc. Please feel free to fiddle with this stuff, people...
1999-03-09 09:25:58 +03:00
<h3>
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
\\$*
Improve appearance, tone down the .Sh size, define a <style> for color headings, etc. Please feel free to fiddle with this stuff, people...
1999-03-09 09:25:58 +03:00
</h3>
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
..
.de Ss
. end-preformat
. init-html
Improve appearance, tone down the .Sh size, define a <style> for color headings, etc. Please feel free to fiddle with this stuff, people...
1999-03-09 09:25:58 +03:00
<h4>
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
<a name="\\$*">
\\$*
</a>
Improve appearance, tone down the .Sh size, define a <style> for color headings, etc. Please feel free to fiddle with this stuff, people...
1999-03-09 09:25:58 +03:00
</h4>
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
..
.
.de Sx
. end-preformat
. ds doc-tmp-1 "\\$1
. shift
. while \\n[.$] \{\
. doc-checkpunct \\$1 \\*[doc-punct]
. ie !\\n[doc-ispunct] .as doc-tmp-1 " \\$1
. el .break
. shift
. \}
<a href="#\\*[doc-tmp-1]">\\*[doc-tmp-1]</a>\\$1\\$2\\$3\\$4\\$5\\$6
..
.
.de Pp
. end-preformat
<p>
..
.
.nr doc-markbreak 0
.de doc-conditional-break
. if \\n[.c]>(\\n[doc-markbreak]+1) <br>
. nr doc-markbreak \\n[.c]
..
.
.de D1
. end-preformat
. doc-conditional-break
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
. No \\$@
<br>
..
.
.de Dl
. end-preformat
. doc-conditional-break
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
. Li \\$@
<br>
..
.
.de Bd
. doc-push .Ed
. end-preformat
. nr Bd-literal 0
. nr Bd-offset 0
. ds get-file
. while \\n(.$ \{\
. if '\\$1'-literal' \{\
. nr Bd-literal 1
. shift
. continue
. \}
. if '\\$1'-offset' \{\
. shift
. shift
. nr Bd-offset 1
. ds start-display <dl compact><dt><dd>
. continue
. \}
. if '\\$1'-file' \{\
. ds get-file so \\$2
. shift
. shift
. continue
. \}
. shift
. \}
. if \\n[Bd-offset] <dl compact><dt><dd>
. if \\n[Bd-literal] <code>
<pre>\\" HOW DO WE GET RID OF THIS NEWLINE??
.\\*[get-file]
..
.de Ed
Fix a number of bugs and and start over again on the style sheet.
2002-02-07 03:59:18 +03:00
. DEBUG .tm Ed
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
</pre>
. doc-pop .Ed
. if \\n[Bd-literal] </code>
. if \\n[Bd-offset] </dl>
..
.de Bl
. doc-push .El
. end-preformat
. ds list-start UNKNOWN
. nr bl-is-compact 0
. while \\n(.$ \{\
. if '\\$1'-width' \{\
. shift
. shift
. continue
. \}
. if '\\$1'-column' \{\
. ds list-start <center><table>
. ds list-end </table></center>
. ds list-tag-prefix <tr><td>
. ds list-pp-prefix
. shift
. break
. \}
. if '\\$1'-bullet' \{\
. ds list-start <ul>
. ds list-end </ul>
. ds list-tag-prefix <p>
. ds list-pp-prefix <li>
. shift
. continue
. \}
. if '\\$1'-dash' \{\
. ds list-start <dl>
. ds list-end </dl>
. ds list-tag-prefix <p>
. ds list-pp-prefix <dd>-
. shift
. continue
. \}
. if '\\$1'-enum' \{\
. ds list-start <ol>
. ds list-end </ol>
. ds list-tag-prefix <p>
. ds list-pp-prefix <li>
. shift
. continue
. \}
. if '\\$1'-hyphen' \{\
. ds list-start <dl>
. ds list-end </dl>
. ds list-tag-prefix <p>
. ds list-pp-prefix <dd>-
. shift
. continue
. \}
. if '\\$1'-item' \{\
. ds list-start <dl>
. ds list-end </dl>
. ds list-tag-prefix <p>
. ds list-pp-prefix <dd>
. shift
. continue
. \}
. if '\\$1'-tag' \{\
. ds list-start <dl compact>
. ds list-end </dl>
. ds list-tag-prefix <p><dt>
. ds list-pp-prefix <dd>
. shift
. continue
. \}
. if '\\$1'-diag' \{\
. ds list-start <dl compact>
. ds list-end </dl>
. ds list-tag-prefix <p><dt>
. ds list-pp-prefix <dd>
. shift
. continue
. \}
. if '\\$1'-hang' \{\
. ds list-start <dl compact>
. ds list-end </dl>
. ds list-tag-prefix <p><dt>
. ds list-pp-prefix <dd>
. shift
. continue
. \}
. if '\\$1'-ohang' \{\
. ds list-start <dl>
. ds list-end </dl>
. ds list-tag-prefix <p><dt>
. ds list-pp-prefix <dd>
. shift
. continue
. \}
. if '\\$1'-offset' \{\
. \" FIXME -- this isn't implemented
. shift
. shift
. continue
. \}
. if '\\$1'-compact' \{\
. nr bl-is-compact 1
. shift
. continue
. \}
. if '\\$1'-inset' \{\
. ds list-start <dl>
. ds list-end </dl>
. ds list-tag-prefix <p><dt>
. ds list-pp-prefix <dd>
. shift
. continue
. \}
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
. ab Unknown .Bl list parameter \\$1 (#\\n(.c)
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. break
. \}
. if \\n[bl-is-compact] \{\
. if '\\*[list-tag-prefix]'<p>' .ds list-tag-prefix
. if '\\*[list-tag-prefix]'<p><dt>' .ds list-tag-prefix <dt>
. \}
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
. if '\\*[list-start]'UNKNOWN' .ab \
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
Unknown .Bl list type \\$1 (#\\n(.c)
. push-list-level start end tag-prefix pp-prefix
\\*[list-start]
..
.de push-list-level
. nr list-level +1
. while \\n(.$ \{\
. ds list-\\$1-\\n[list-level] \\*[list-\\$1]
. shift
. \}
..
.de pop-list-level
. nr list-level -1
..
.de It-span
. end-preformat
. as doc-pcresult <tr><td colspan=9>
. recurse \\$@
. as doc-pcresult
. pc-fin
..
.de It
. end-preformat
. as doc-pcresult \\*[list-tag-prefix-\\n[list-level]]
. recurse \\$@
. as doc-pcresult \\*[list-pp-prefix-\\n[list-level]]
. pc-fin
..
.de El
. doc-pop .El
\\*[list-end-\\n[list-level]]
. pop-list-level
..
.de Lb
.if !\\n(.$==1 .tm Usage: .Lb [library name]
.if "\\$1"libarm32" \&ARM32 Architecture Library (libarm32, -larm32)
.if "\\$1"libi386" \&i386 Architecture Library (libi386, -li386)
Add a libm68k library macro.
2001-07-04 21:12:33 +04:00
.if "\\$1"libm68k" \&m68k Architecture Library (libm68k, -lm68k)
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
.if "\\$1"libc" \&Standard C Library (libc, -lc)
Add libcdk to these two files
2001-01-05 18:59:30 +03:00
.if "\\$1"libcdk" \&Curses Development Kit Library (libcdk, -lcdk)
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
.if "\\$1"libcompat" \&Compatibility Library (libcompat, -lcompat)
.if "\\$1"libcrypt" \&Crypt Library (libcrypt, -lcrypt)
.if "\\$1"libcurses" \&Curses Library (libcurses, -lcurses)
.if "\\$1"libedit" \&Command Line Editor Library (libedit, -ledit)
Add libevent.
2003-07-04 16:20:11 +04:00
.if "\\$1"libevent" \&Event Notification Library (libevent, -levent)
Added libform.
2001-01-05 15:59:25 +03:00
.if "\\$1"libform" \&Curses Form Library (libform, -lform)
declare .Lb symbol for libintl.
2000-10-31 18:08:29 +03:00
.if "\\$1"libintl" \&Internationalized Message Handling Library (libintl, -lintl)
add LIBRARY section into libipsec manpages. add ".Lb libipsec" for this.
1999-07-04 05:27:19 +04:00
.if "\\$1"libipsec" \&IPsec Policy Control Library (libipsec, -lipsec)
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
.if "\\$1"libkvm" \&Kernel Data Access Library (libkvm, -lkvm)
.if "\\$1"libm" \&Math Library (libm, -lm)
Make libmagic known as a system library, and install manual page links of the libmagic functions. Submitted by Hiroshi Ura <ura at hiru dot aoba dot yokohama dot jp> in PR21496. Reviewed By: wiz
2003-05-08 11:14:11 +04:00
.if "\\$1"libmagic" \&Magic Number Recognition Library (libmagic, -lmagic)
Add .Lb libmenu.
1999-11-24 15:46:40 +03:00
.if "\\$1"libmenu" \&Curses Menu Library (libmenu, -lmenu)
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
.if "\\$1"libossaudio" \&OSS Audio Emulation Library (libossaudio, -lossaudio)
Add libpcap.
2003-02-25 15:53:03 +03:00
.if "\\$1"libpcap" \&Packet Capture Library (libpcap, -lpcap)
Add libpci.
2001-09-14 03:21:49 +04:00
.if "\\$1"libpci" \&PCI Bus Access Library (libpci, -lpci)
Add libpmc.
2002-08-09 04:18:30 +04:00
.if "\\$1"libpmc" \&Performance Counters Library (libpmc, -lpmc)
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
.if "\\$1"libposix" \&POSIX Compatibility Library (libposix, -lposix)
Add libpthread and librt.
2003-01-23 02:40:19 +03:00
.if "\\$1"libpthread" \&POSIX Thread Library (libpthread, -lpthread)
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
.if "\\$1"libresolv" \&DNS Resolver Library (libresolv, -lresolv)
Add libpthread and librt.
2003-01-23 02:40:19 +03:00
.if "\\$1"librt" \&POSIX Real-time Library (librt, -lrt)
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
.if "\\$1"libtermcap" \&Termcap Access Library (libtermcap, -ltermcap)
Add libusbhid.
2001-12-29 02:06:30 +03:00
.if "\\$1"libusbhid" \&USB Human Interface Devices Library (libusbhid, -lusbhid)
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
.if "\\$1"libutil" \&System Utilities Library (libutil, -lutil)
.if "\\$1"libz" \&Compression Library (libz, -lz)
..
.
.
.de doc-checkpunct
. ds doc-cp-tmp1 \\$1
. shift
. nr doc-ispunct 0
. while \\n[.$] \{\
. if \\*[doc-cp-tmp1]\\$1 .nr doc-ispunct 1
. shift
. \}
..
.\"
.\" Parsed and Callable macros
.\"
.\" Internal structure: `recurse' and `mode-*-{on,off}'
.\"
.de recurse
. nr r-lvl +1
.DEBUG .tm r \\n[r-lvl] __\\*[doc-pcresult]==\\$@__
. while \\n(.$ \{\
. doc-checkpunct \\$1 \\*[doc-punct]
. if \\n[doc-ispunct] \{\
. as doc-punct-result \\$1
. shift
. continue
. \}
. nr is-request \\A'\\$1'
. if \\n[is-request] \{\
. if ddoc2html@@\\$1 .nr is-request 1
. if !ddoc2html@@\\$1 .nr is-request 0
. \}
. ie \\n[is-request] \{\
. ds recurse-tmp1 \\$1
. shift
. \\*[recurse-tmp1] \\$@
. break
. \}
. el \{\
.DEBUG .tm r \\n[r-lvl] __\\*[doc-pcresult]+\\$1==\\$@__
. \" a random word, so output saved punctuation
. \" (normally saved until level 0 mode closure )
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
. if \\w\\*[doc-pcresult] \{\
. as doc-pcresult \\*[close-mode]
. as doc-pcresult \\*[doc-punct-result]
. as doc-pcresult \\*[open-mode]
. ds doc-punct-result
. \}
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. if \\n[doc-dosep] .as doc-pcresult \\*[sepstring]
. nr doc-dosep 1
Fix a number of bugs and and start over again on the style sheet.
2002-02-07 03:59:18 +03:00
. as doc-pcresult \\$1
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. shift
. continue
. \}
. \}
. nr r-lvl -1
..
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
.
.de resetmode
. ds open-mode
. ds close-mode
..
.
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
.de make-mode
\\*[dot-de] mode-\\$1-on
. DEBUG .tm mode-\\$1-on <\\\\$@>
. rn close-mode xclose-mode
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
. ds open-mode \\$2
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. ds close-mode \\$3
. as doc-pcresult \\\\*[xclose-mode]\\$2
\\*[dot-dot]
\\*[dot-de] mode-\\$1-off
. DEBUG .tm mode-\\$1-off <\\\\$@>
. as doc-pcresult \\\\*[close-mode]
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
. resetmode
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
\\*[dot-dot]
..
.de pc-fin
. as doc-pcresult \\$1
. if \\n[r-lvl]=0 \{\\*[doc-pcresult]\\*[doc-punct-result]
. ds doc-punct-result
. rm doc-pcresult
. ds sepstring \~
. nr doc-dosep 0
. \}
..
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
.
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
.make-mode bold <b> </b>
.make-mode code <code> </code>
.make-mode em <em> </em>
.make-mode i <i> </i>
Change the end of caps mode from <font size="+0"> to </font>. This gets the tag nesting more correct, and is necessary to get the INSTALL notes to render correctly in Konqueror. The results still look sensible in w3m, Lynx and Mozilla.
2002-05-27 21:46:55 +04:00
.make-mode caps <font\ size="-1"> </font>
Define mode-null-{on,off} for turning off special modes. Turn off any special modes when Ns is called.
1999-01-28 03:11:07 +03:00
.make-mode null \& \&
* Sync .St with the main mdoc * Fix (some of) the bugs with .Fn
1999-06-01 22:25:15 +04:00
.make-mode function <code> </code>
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
.am mode-i-on
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
. ds sepstring \~
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
..
.am mode-em-on
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
. ds sepstring \~
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
..
.am mode-i-off
. ds sepstring \~
..
.am mode-em-off
. ds sepstring \~
..
.
.de doc-sep-append
. if \\n[doc-dosep] .as doc-pcresult \~
. as doc-pcresult \\$1
. nr doc-dosep 0
..
.de No
. as doc-pcresult \\*[close-mode]
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
. resetmode
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. recurse \\$@
. pc-fin
..
.de Fl
.DEBUG .tm .Fl \\$*
Fix a number of bugs and and start over again on the style sheet.
2002-02-07 03:59:18 +03:00
. as doc-pcresult <b>-</b>
. nr doc-dosep 0
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. mode-bold-on
. recurse \\$@
. mode-bold-off
. pc-fin
..
.de Cm
.DEBUG .tm .Cm \\$*
. mode-bold-on
. recurse \\$@
. mode-bold-off
. pc-fin
..
.de Op
.DEBUG .tm .Op \\$*
. as doc-pcresult \&[
. recurse \\$@
. pc-fin \&]
..
.de Em
.DEBUG .tm .Em \\$*
. mode-em-on
. recurse \\$@
. mode-em-off
. pc-fin
..
.de Fx
.DEBUG .tm .Fx \\$*
. as doc-pcresult FreeBSD
. recurse \\$@
..
.de Nm
Improve appearance, tone down the .Sh size, define a <style> for color headings, etc. Please feel free to fiddle with this stuff, people...
1999-03-09 09:25:58 +03:00
. ds Nm-result \\*[Nm-save]
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. if \\n(.$ \{\
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
. ie '\\$1'' .br-real
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. el \{\
Improve appearance, tone down the .Sh size, define a <style> for color headings, etc. Please feel free to fiddle with this stuff, people...
1999-03-09 09:25:58 +03:00
. ds Nm-result \\$1
. if '\\*[Nm-save]'' .ds Nm-save \\$1
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. shift
. \}
. \}
. mode-bold-on
Improve appearance, tone down the .Sh size, define a <style> for color headings, etc. Please feel free to fiddle with this stuff, people...
1999-03-09 09:25:58 +03:00
. as doc-pcresult \\*[Nm-result]
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. recurse \\$@
. mode-bold-off
. pc-fin
..
.de Nd
.DEBUG .tm .Nd \\$*
- \\$*
..
.de At
AT&T UNIX\\$*
..
Add simple An handling. Modified version of a patch by Greg A. Woods in private mail. Closes my PR 29241.
2005-02-07 04:11:14 +03:00
.de An
. recurse \\$@
. pc-fin
..
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
.de Lk
. as doc-pcresult <a href="\\$1">\\$1</a>
. shift
. recurse \\$@
. pc-fin
..
.de Mt
. as doc-pcresult <a href="mailto:\\$1">\\$1</a>
. shift
. recurse \\$@
. pc-fin
..
.de Ta
. as doc-pcresult <td>
. recurse \\$@
. pc-fin
..
.de Bx
. doc-checkpunct \\$1 \\*[doc-punct]
. if !\\n[doc-ispunct] \{\
. as doc-pcresult \\$1
. shift
. \}
. as doc-pcresult BSD
. recurse \\$@
. pc-fin
..
.de Nx
. as doc-pcresult NetBSD
. recurse \\$@
. pc-fin
..
Add Ox macro (OpenBSD).
2000-07-05 14:54:12 +04:00
.de Ox
. as doc-pcresult OpenBSD
. recurse \\$@
. pc-fin
..
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
.de Ux
. as doc-pcresult UNIX
. recurse \\$@
. pc-fin
..
.de Ql
. as doc-pcresult `
. recurse \\$@
. pc-fin \&'
..
.de Pf
. as doc-pcresult \\$1
. shift
. nr doc-dosep 0
. recurse \\$@
. pc-fin
..
.de Ns
. nr doc-dosep 0
Define mode-null-{on,off} for turning off special modes. Turn off any special modes when Ns is called.
1999-01-28 03:11:07 +03:00
. mode-null-on
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. recurse \\$@
Define mode-null-{on,off} for turning off special modes. Turn off any special modes when Ns is called.
1999-01-28 03:11:07 +03:00
. mode-null-off
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. pc-fin
..
.
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
.de doc-start-quote
. if \\n[r-lvl]&\\n[doc-dosep] .as doc-pcresult \\*[sepstring]
. as doc-pcresult \\$1
. nr doc-dosep 0
..
.
.de safe-blm
..
.
Fix a number of bugs and and start over again on the style sheet.
2002-02-07 03:59:18 +03:00
.nr quote-level 0
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
.de doc-quote-open
Fix a number of bugs and and start over again on the style sheet.
2002-02-07 03:59:18 +03:00
. nr quote-level +1
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
. blm safe-blm
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. if \\n[r-lvl]&\\n[doc-dosep] .as doc-pcresult \\*[sepstring]
. nr doc-dosep 0
Fix a number of bugs and and start over again on the style sheet.
2002-02-07 03:59:18 +03:00
. ie \\n[quote-level]=1 \{\
. ev quotation_ev
. di quotation
. br-real
. nr quotation_line \\n[.c]
. \}
. el \{\
. di
. as quotation \\$1
. da quotation
. \}
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
..
.
.de general-close
Fix a number of bugs and and start over again on the style sheet.
2002-02-07 03:59:18 +03:00
. nr quote-level -1
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
. if \\w\\n[.z]=0 .Error no quotation is open
. br-real
Fix a number of bugs and and start over again on the style sheet.
2002-02-07 03:59:18 +03:00
. if \\n[quote-level]=0 \{\
. di
. ev
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
. ev quotation_ev
. br-real
. da quotation
Fix a number of bugs and and start over again on the style sheet.
2002-02-07 03:59:18 +03:00
. nf-real
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
.
. di
. ev
Fix a number of bugs and and start over again on the style sheet.
2002-02-07 03:59:18 +03:00
. as doc-pcresult \\$1\\*[quotation]\\
. blm Pp
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
. \}
.
.
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
..
.
.de make-quoter
\\*[dot-de] \\$1o
Fix a number of bugs and and start over again on the style sheet.
2002-02-07 03:59:18 +03:00
. doc-quote-open \\$2
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. recurse \\\\$@
. pc-fin
\\*[dot-dot]
\\*[dot-de] \\$1c
Fix a number of bugs and and start over again on the style sheet.
2002-02-07 03:59:18 +03:00
. DEBUG .tm CLOSE 1,\\\\$@,
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
. general-close \\$2
Fix a number of bugs and and start over again on the style sheet.
2002-02-07 03:59:18 +03:00
. DEBUG .tm CLOSE 2,\\\\$@,\\$3,
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
. recurse \\\\$@ \\$3
. pc-fin
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
\\*[dot-dot]
\\*[dot-de] \\$1q
. doc-start-quote \\$2
. recurse \\\\$@
. pc-fin \\$3
\\*[dot-dot]
..
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
.
Make Pq, Po, Pc, Oo, Oc callable.
1999-03-07 11:48:48 +03:00
.\" generate Aq Ao Ac Bq Bo Bc Dq Do Dc Pq Po Pc Qq Qo Qc Sq So Sc Oo Oc
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
.make-quoter A &lt; &gt;
Fix a number of bugs and and start over again on the style sheet.
2002-02-07 03:59:18 +03:00
.make-quoter B \&[ ]
.make-quoter D \&`` ''
.make-quoter P \&( )
.make-quoter Q \&" "
.make-quoter S \&` '
Escape some punctuation, and make Oo and Oc aliases for Bo and Bc.
1999-03-07 11:37:03 +03:00
.als Oo Bo
.als Oc Bc
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
.de Error
. ab Line \\n[.c], Error: \\$*
..
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
.de Ft
. as doc-pcresult <br><br>
. mode-code-on
. recurse \\$@
. mode-code-off
. pc-fin
..
.de Fn
. mode-bold-on
. as doc-pcresult "\\$1
. shift
. mode-bold-off
. as doc-pcresult (
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
. mode-function-on
Improve appearance, tone down the .Sh size, define a <style> for color headings, etc. Please feel free to fiddle with this stuff, people...
1999-03-09 09:25:58 +03:00
. ds sepstring , \" (need the space)
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. recurse \\$@
* Sync .St with the main mdoc * Fix (some of) the bugs with .Fn
1999-06-01 22:25:15 +04:00
. as doc-pcresult \\*[close-mode])
Fix a number of bugs and and start over again on the style sheet.
2002-02-07 03:59:18 +03:00
. resetmode
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
. pc-fin
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
..
.de Fo
. mode-bold-on
. as doc-pcresult "\\$1
. shift
. mode-bold-off
. as doc-pcresult (
. mode-code-on
. recurse \\$@
. mode-code-off
. pc-fin
..
.de Fc
. recurse \\$@
. pc-fin )
..
.de Ar
. mode-i-on
. recurse \\$@
. mode-i-off
. pc-fin
..
.de Ic
. mode-bold-on
. recurse \\$@
. mode-bold-off
. pc-fin
..
.de Fa
. mode-code-on
. recurse \\$@
. mode-code-off
. pc-fin
..
.de Xr
Don't make broken links out of incomplete .Xr requests.
2002-02-06 00:00:09 +03:00
. nr have-sec 0
. if \\$21 .nr have-sec 1
. if \\$22 .nr have-sec 1
. if \\$23 .nr have-sec 1
. if \\$24 .nr have-sec 1
. if \\$25 .nr have-sec 1
. if \\$26 .nr have-sec 1
. if \\$27 .nr have-sec 1
. if \\$28 .nr have-sec 1
. if \\$29 .nr have-sec 1
. ie \\n[DOC_XR]:(\\n[have-sec]=0) \{\
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. mode-code-on
Don't make broken links out of incomplete .Xr requests.
2002-02-06 00:00:09 +03:00
. ie \\n[have-sec]=0 .as doc-pcresult \\$1
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
. el .as doc-pcresult \\$1(\\$2)
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. mode-code-off
. \}
. el \{\
Invert the default of DOC_XR and generate an href anchor by default. Also, assume that any man page called "index.html" will actually be installed (sigh) as "xindex.html", which is what bsd.man.mk actually does now.
2002-02-07 04:59:14 +03:00
. ds Xr-tmp \\$1
. if \\*[Xr-tmp]index .ds Xr-tmp xindex
. as doc-pcresult <a href="\\*[DOC_MANROOT]/html\\$2/\\$1.html">
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
. ie \\w\\$2=0 .as doc-pcresult \\$1
. el .as doc-pcresult \\$1(\\$2)
. as doc-pcresult </a>
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. \}
. shift
. shift
. recurse \\$@
. pc-fin
..
.de Dv
. mode-code-on
. recurse \\$@
. mode-code-off
. pc-fin
..
.de Ic
. mode-bold-on
. recurse \\$@
. mode-bold-off
. pc-fin
..
.de Pa
. mode-code-on
. recurse \\$@
. mode-code-off
. pc-fin
..
.de Tn
. mode-caps-on
. recurse \\$@
. mode-caps-off
. pc-fin
..
.de Fd
. as doc-pcresult <br>
. mode-bold-on
. recurse \\$@
. mode-bold-off
. pc-fin
..
.de Va
. mode-i-on
. recurse \\$@
. mode-i-off
. pc-fin
..
.de Li
. mode-code-on
. recurse \\$@
. mode-code-off
. pc-fin
..
.de Sy
. mode-bold-on
. recurse \\$@
. mode-bold-off
. pc-fin
..
.de Me
. mode-bold-on
. recurse \\$@
. mode-bold-off
. pc-fin
..
.de Ev
. mode-code-on
. recurse \\$@
. mode-code-off
. pc-fin
..
.de Cd
. mode-bold-on
. recurse \\$@
. mode-bold-off
. pc-fin
..
.ig
I used to have a caps-code mode for Er. But <code> apparently
already implies a small mode or maybe actually small caps mode.
..
.de Er
. mode-code-on
. recurse \\$@
. mode-code-off
. pc-fin
..
.de St
. ie \\n(.$==0 \{\
. tm The .St (expand standard name) macro requires >= 1 arg
. \}
. el \{\
. ds std-tmp1 ERROR
Add a symbol for IEEE Std 1003.1-2001.
2002-05-15 14:11:15 +04:00
. if "\\$1"-p1003.1-2001" \{\
. ds std-tmp1 \&IEEE Std1003.1-2001
. as std-tmp1 " \"exactly one space
. as std-tmp1 (``\\*(Px'')
. \}
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. if "\\$1"-p1003.1-96" \{\
Whitespace nit in -p1003.1-96.
2000-02-11 01:02:09 +03:00
. ds std-tmp1 \&ISO/IEC 9945-1:1996
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. as std-tmp1 " \"exactly one space
. as std-tmp1 (``\\*(Px'')
. \}
Add a 1003.1g-2000 macro.
2001-10-22 20:46:05 +04:00
. if "\\$1"-p1003.1g-2000" \{\
. ds std-tmp1 \&IEEE Std1003.1g-2000
. as std-tmp1 " \"exactly one space
. as std-tmp1 (``\\*(Px'')
. \}
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. if "\\$1"-p1003.1c-95" \{\
. ds std-tmp1 \&IEEE Std1003.1c-1995
. as std-tmp1 " \"exactly one space
. as std-tmp1 (``\\*(Px'')
. \}
. if "\\$1"-p1003.1b-93" \{\
. ds std-tmp1 \&IEEE Std1003.1b-1993
. as std-tmp1 " \"exactly one space
. as std-tmp1 (``\\*(Px'')
. \}
. if "\\$1"-p1003.1-90" \{\
. ds std-tmp1 \&IEEE Std1003.1-1990
. as std-tmp1 " \"exactly one space
. as std-tmp1 (``\\*(Px'')
. \}
. if "\\$1"-p1003.1-88" \{\
. ds std-tmp1 \&IEEE Std1003.1-1988
. as std-tmp1 " \"exactly one space
. as std-tmp1 (``\\*(Px'')
. \}
. if "\\$1"-p1003.1" \{\
. ds std-tmp1 \&IEEE Std1003.1
. as std-tmp1 " \"exactly one space
. as std-tmp1 (``\\*(Px'')
. \}
. if "\\$1"-p1003.2-92" \{\
. ds std-tmp1 \&IEEE Std1003.2-1992
. as std-tmp1 " \"exactly one space
. as std-tmp1 (``\\*(Px.2'')
. \}
. if "\\$1"-p1003.2" \{\
. ds std-tmp1 \&IEEE Std1003.2
. as std-tmp1 " \"exactly one space
. as std-tmp1 (``\\*(Px.2'')
. \}
Use St -isoC-9X instead of St -isoC9X, to be in sync with groff.
2003-09-08 21:54:31 +04:00
. if "\\$1"-isoC-90" \{\
Changes references from ``ISO C'' to ``ISO C90''.
2000-07-04 11:03:15 +04:00
. ds std-tmp1 \&ISO/IEC 9899:1990
. as std-tmp1 " \"exactly one space
. as std-tmp1 (``ISO C90'')
. \}
. if "\\$1"-isoC-amd1" \{\
. ds std-tmp1 \&ISO/IEC 9899/AMD1:1990
. as std-tmp1 " \"exactly one space
. as std-tmp1 (``ISO C90'')
. \}
. if "\\$1"-isoC-amd2" \{\
. ds std-tmp1 \&ISO/IEC 9899/AMD2:1990
. as std-tmp1 " \"exactly one space
. as std-tmp1 (``ISO C90'')
. \}
. if "\\$1"-isoC-tcor1" \{\
. ds std-tmp1 \&ISO/IEC 9899/TCOR1:1990
. as std-tmp1 " \"exactly one space
. as std-tmp1 (``ISO C90'')
. \}
. if "\\$1"-isoC-tcor2" \{\
. ds std-tmp1 \&ISO/IEC 9899/TCOR2:1990
. as std-tmp1 " \"exactly one space
. as std-tmp1 (``ISO C90'')
. \}
Use St -isoC-9X instead of St -isoC9X, to be in sync with groff.
2003-09-08 21:54:31 +04:00
. if "\\$1"-isoC-99" \{\
Add an -isoC99 macro; while I'm here, correct white space usage in other ISO/IEC document numbers.
2000-03-05 21:40:06 +03:00
. ds std-tmp1 \&ISO/IEC 9899:1999
. as std-tmp1 " \"exactly one space
. as std-tmp1 (``ISO C99'')
. \}
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. if "\\$1"-ansiC" \{\
. ds std-tmp1 \&ANSI X3.159-1989
. as std-tmp1 " \"exactly one space
. as std-tmp1 (``ANSI C'')
. \}
. if "\\$1"-ansiC-89" \{\
. ds std-tmp1 \&ANSI X3.159-1989
. as std-tmp1 " \"exactly one space
. as std-tmp1 (``ANSI C'')
. \}
. if "\\$1"-ieee754" \{\
. ds std-tmp1 \&IEEE Std754-1985
. \}
Add IEEE 1275-1994 (already in mdoc.local).
2003-07-01 12:42:19 +04:00
. if "\\$1"-ieee754" \{\
. ds std-tmp1 \&IEEE Std1275-1994
. as std-tmp1 " \"exactly one space
. as std-tmp1 (``Open Firmware'')
. \}
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. if "\\$1"-iso8802-3" \{\
ISO 8802-3:1989 -> ISO/IEC 8802-3:1989 Ok'd by kleink.
2001-11-29 17:58:24 +03:00
. ds std-tmp1 \&ISO/IEC 8802-3:1989
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. \}
. if "\\$1"-xpg3" \{\
* Sync .St with the main mdoc * Fix (some of) the bugs with .Fn
1999-06-01 22:25:15 +04:00
. ds std-tmp1 X/Open Portability Guide Issue 3
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. as std-tmp1 " \"exactly one space
. as std-tmp1 (``XPG3'')
. \}
. if "\\$1"-xpg4" \{\
* Sync .St with the main mdoc * Fix (some of) the bugs with .Fn
1999-06-01 22:25:15 +04:00
. ds std-tmp1 X/Open Portability Guide Issue 4
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. as std-tmp1 " \"exactly one space
. as std-tmp1 (``XPG4'')
. \}
. if "\\$1"-xpg4.2" \{\
Use even more standard names for standards.
2001-11-21 14:25:22 +03:00
. ds std-tmp1 X/Open Portability Guide Issue 4, Version 2
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. as std-tmp1 " \"exactly one space
. as std-tmp1 (``XPG4.2'')
. \}
* Sync .St with the main mdoc * Fix (some of) the bugs with .Fn
1999-06-01 22:25:15 +04:00
. if "\\$1"-xbd5" \{\
. ds std-tmp1 X/Open System Interface Definitions Issue 5
. as std-tmp1 " \"exactly one space
. as std-tmp1 (``\\*(tNXBD5\\*(aa'')
. \}
. if "\\$1"-xcu5" \{\
. ds std-tmp1 X/Open Commands and Utilities Issue 5
. as std-tmp1 " \"exactly one space
. as std-tmp1 (``\\*(tNXCU5\\*(aa'')
. \}
. if "\\$1"-xsh5" \{\
. ds std-tmp1 X/Open System Interfaces and Headers Issue 5
. as std-tmp1 " \"exactly one space
. as std-tmp1 (``\\*(tNXSH5\\*(aa'')
. \}
. if "\\$1"-xns5" \{\
. ds std-tmp1 X/Open Networking Services Issue 5
. as std-tmp1 " \"exactly one space
. as std-tmp1 (``\\*(tNXNS5\\*(aa'')
. \}
add St -xns5.2d2.0
2001-07-04 02:05:11 +04:00
. if "\\$1"-xns5.2d2.0" \{\
. ds std-tmp1 X/Open Networking Services Issue 5.2 Draft 2.0
. as std-tmp1 " \"exactly one space
. as std-tmp1 (``\\*(tNXNS5.2D2.0\\*(aa'')
. \}
* Sync .St with the main mdoc * Fix (some of) the bugs with .Fn
1999-06-01 22:25:15 +04:00
. if "\\$1"-xcurses4.2" \{\
Use even more standard names for standards.
2001-11-21 14:25:22 +03:00
. ds std-tmp1 X/Open Curses, Issue 4, Version 2
* Sync .St with the main mdoc * Fix (some of) the bugs with .Fn
1999-06-01 22:25:15 +04:00
. as std-tmp1 " \"exactly one space
. as std-tmp1 (``\\*(tNXCURSES4.2\\*(aa'')
. \}
Add a macro for our friend, the System V Interface Definition.
1999-02-06 18:01:13 +03:00
. if "\\$1"-svid4" \{\
. ds std-tmp1 \&System V Interface Definition,
. as std-tmp1 " \"exactly one space
. as std-tmp1 \&Fourth Edition
. as std-tmp1 " \"exactly one space
. as std-tmp1 (``SVID4'')
. \}
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. if "\\*[std-tmp1]"ERROR" .tm ERROR, no such std: .St \\$*
. shift
. as doc-pcresult \~\\*[std-tmp1]\~
. recurse \\$@
. pc-fin
. \}
..
.ig
I've observed that <code> does decent things with caps, and it should
be reminiscent of the old typewriter-style unix logos.
..
.de At
. if \\n(.$==2 \{\
. if "\\$1"32v" Version 32V <code>AT&T UNIX</code>\\$2
. if "\\$1"V" \<code>AT&T</code> System V <code>UNIX</code>\\$2
. if "\\$1"V.1" <code>AT&T</code> System V.1 <code>UNIX</code>\\$2
. if "\\$1"V.2" <code>AT&T</code> System V.2 <code>UNIX</code>\\$2
. if "\\$1"V.3" <code>AT&T</code> System V.3 <code>UNIX</code>\\$2
. if "\\$1"V.4" <code>AT&T</code> System V.4 <code>UNIX</code>\\$2
add AT&T v1 and v5
2001-07-02 04:03:31 +04:00
. if "\\$1"v1" Version 1 <code>AT&T UNIX</code>\\$2
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. if "\\$1"v5" Version 5 <code>AT&T UNIX</code>\\$2
. if "\\$1"v6" Version 6 <code>AT&T UNIX</code>\\$2
. if "\\$1"v7" Version 7 <code>AT&T UNIX</code>\\$2
. \}
. if \\n(.$==1 \{\
. if "\\$1"32v" Version 32V <code>AT&T UNIX</code>
. if "\\$1"V" <code>AT&T</code> System V <code>UNIX</code>
. if "\\$1"V.1" <code>AT&T</code> System V.1 <code>UNIX</code>
. if "\\$1"V.2" <code>AT&T</code> System V.2 <code>UNIX</code>
. if "\\$1"V.3" <code>AT&T</code> System V.3 <code>UNIX</code>
. if "\\$1"V.4" <code>AT&T</code> System V.4 <code>UNIX</code>
add AT&T v1 and v5
2001-07-02 04:03:31 +04:00
. if "\\$1"v1" Version 1 <code>AT&T UNIX</code>
. if "\\$1"v5" Version 5 <code>AT&T UNIX</code>
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. if "\\$1"v6" Version 6 <code>AT&T UNIX</code>
. if "\\$1"v7" Version 7 <code>AT&T UNIX</code>
. \}
. if \\n(.$==0 \{\
. if 1 <code>AT&T UNIX</code>
. \}
..
.\"----------------------------------------------------------------------
.\"
.\" There must be a doc2html alias for all callable macros
.\"
.als doc2html@@Dd Dd
.als doc2html@@Dt Dt
.als doc2html@@Os Os
.als doc2html@@br br
.als doc2html@@sp sp
.als doc2html@@fi fi
.als doc2html@@nf nf
.als doc2html@@Sh Sh
.als doc2html@@Ss Ss
.als doc2html@@Pp Pp
.als doc2html@@D1 D1
.als doc2html@@Dl Dl
.als doc2html@@Bd Bd
.als doc2html@@Ed Ed
.als doc2html@@Bl Bl
.als doc2html@@It It
.als doc2html@@El El
.als doc2html@@Fl Fl
.als doc2html@@Cm Cm
.als doc2html@@Op Op
.als doc2html@@Em Em
.als doc2html@@Fx Fx
Add Ox macro (OpenBSD).
2000-07-05 14:54:12 +04:00
.als doc2html@@Ox Ox
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
.als doc2html@@Nm Nm
.als doc2html@@Nd Nd
.als doc2html@@At At
.als doc2html@@Bx Bx
.als doc2html@@Nx Nx
.als doc2html@@Ux Ux
.als doc2html@@Ql Ql
.als doc2html@@Pf Pf
.als doc2html@@Ns Ns
.als doc2html@@Ft Ft
.als doc2html@@Fn Fn
.als doc2html@@Fo Fo
.als doc2html@@Fc Fc
.als doc2html@@Ar Ar
.als doc2html@@Ic Ic
.als doc2html@@Fa Fa
.als doc2html@@Xr Xr
.als doc2html@@Dv Dv
.als doc2html@@Ic Ic
.als doc2html@@Pa Pa
.als doc2html@@Tn Tn
.als doc2html@@Fd Fd
.als doc2html@@Va Va
.als doc2html@@Li Li
.als doc2html@@Sy Sy
.als doc2html@@Me Me
.als doc2html@@Ev Ev
.als doc2html@@Cd Cd
.als doc2html@@St St
.als doc2html@@Er Er
.als doc2html@@Aq Aq
.als doc2html@@Ao Ao
.als doc2html@@Ac Ac
.als doc2html@@Bq Bq
.als doc2html@@Bo Bo
.als doc2html@@Bc Bc
.als doc2html@@Dq Dq
.als doc2html@@Do Do
.als doc2html@@Dc Dc
.als doc2html@@Qq Qq
.als doc2html@@Qo Qo
.als doc2html@@Qc Qc
Make Pq, Po, Pc, Oo, Oc callable.
1999-03-07 11:48:48 +03:00
.als doc2html@@Pq Pq
.als doc2html@@Po Po
.als doc2html@@Pc Pc
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
.als doc2html@@Sq Sq
.als doc2html@@So So
.als doc2html@@Sc Sc
Make Pq, Po, Pc, Oo, Oc callable.
1999-03-07 11:48:48 +03:00
.als doc2html@@Oo Oo
.als doc2html@@Oc Oc
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
.als doc2html@@Ta Ta
.als doc2html@@Mt Mt
.als doc2html@@Lk Lk
.als doc2html@@No No
Add simple An handling. Modified version of a patch by Greg A. Woods in private mail. Closes my PR 29241.
2005-02-07 04:11:14 +03:00
.als doc2html@@An An
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
.
.rn em doc-real-em
.de em
Fix bugs reported by mycroft, except one.
1999-05-01 03:47:25 +04:00
. tm Hint: Should this have been .Em ...?
. Error end-macro (.em) respecification is not allowed.
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
..
.
.ig
----------------------------------------------------------------------
----------------------------------------------------------------------
----------------------------------------------------------------------
THESE ARE THE -man (-man.old) MACRO FUNCTIONS
Internal symbols relating to -man are prefixed with mo-
The body-params string used with -mdoc2html is used here as well.
..
.de TH
Fix a number of bugs and and start over again on the style sheet.
2002-02-07 03:59:18 +03:00
. init-html \\$@
. nr mo-section \\$2
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
..
.de SH
. end-preformat
. mo-end-dl
Improve appearance, tone down the .Sh size, define a <style> for color headings, etc. Please feel free to fiddle with this stuff, people...
1999-03-09 09:25:58 +03:00
<h3> \\$* </h3>
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
..
.de SS
. end-preformat
. mo-end-dl
Improve appearance, tone down the .Sh size, define a <style> for color headings, etc. Please feel free to fiddle with this stuff, people...
1999-03-09 09:25:58 +03:00
<h4> \\$* </h4>
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
..
.de B
. ie \\n(.$ <b>\&\\$*</b>
. el \{\
. if 1 <b>
. it 1 mo-end-bold
. \}
..
.de I
. ie \\n(.$ <i>\&\\$*</i>
. el \{\
. if 1 <i>
Fix a number of bugs and and start over again on the style sheet.
2002-02-07 03:59:18 +03:00
. it 1 mo-end-italic
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
. \}
..
.de mo-end-bold
</b>
..
.de mo-end-italic
</i>
..
.de SM
<font size=-1>
. it 1 mo-end-smallcaps
. if \\n(.$ \&\\$*
..
.de mo-end-smallcaps
<font size=+0>
..
.de BI
. mo-try-link \\$1 \\$2
. if !\\n[mo-did-link] \{\
. ds mo-bi-tmp1
. while \\n(.$>=2 \{\
. as mo-bi-tmp1 <b>\\$1</b><i>\\$2</i>
. shift
. shift
. \}
. as mo-bi-tmp1 \\$*
\&\\*[mo-bi-tmp1]
. \}
..
.de BR
. mo-try-link \\$1 \\$2
. if !\\n[mo-did-link] \{\
. ds mo-bi-tmp1
. while \\n(.$>=2 \{\
. as mo-bi-tmp1 <b>\\$1</b>\\$2
. shift
. shift
. \}
. as mo-bi-tmp1 \\$*
\&\\*[mo-bi-tmp1]
. \}
..
.de IB
. mo-try-link \\$1 \\$2
. if !\\n[mo-did-link] \{\
. ds mo-bi-tmp1
. while \\n(.$>=2 \{\
. as mo-bi-tmp1 <i>\\$1</i><b>\\$2</b>
. shift
. shift
. \}
. as mo-bi-tmp1 \\$*
\&\\*[mo-bi-tmp1]
. \}
..
.de IR
. mo-try-link \\$1 \\$2
. if !\\n[mo-did-link] \{\
. ds mo-bi-tmp1
. while \\n(.$>=2 \{\
. as mo-bi-tmp1 <i>\\$1</i>\\$2
. shift
. shift
. \}
. as mo-bi-tmp1 \\$*
\&\\*[mo-bi-tmp1]
. \}
..
.de CT
\&&lt;<font size=-1>CTRL/<font size=+0>\\$*&gt;
..
.de DS
<code><pre>
..
.de DE
Fix a number of bugs and and start over again on the style sheet.
2002-02-07 03:59:18 +03:00
. DEBUG .tm DE
New macro package for automatically converting -mdoc input to HTML. Use: nroff -mdoc2html input_file... Or, for the completely general case, Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ... This was originally intended for just the new distrib/notes and other non-man-page project documentation, but in fact it can get almost all of the man pages right at this point. In many cases, I would suggest that original documentation not be written in HTML or ASCII any more. A good example would be "supported devices". It's presently duplicated, in the install notes, the web pages, and the man pages. If written in -mdoc, it can automatically be a man page, a www page feature, and a printable, downloadable file. We can generate PostScript and the "unix enhanced text" format used by more(1), as well as plain old ascii, and all using in-tree tools. TNF Copyright.
1999-01-13 08:00:28 +03:00
</pre></code>
..
.als Ds DS
.als De DE
.als EX DS
.als EE DE
.de TP
. mo-start-dl
<dt>
. it 1 mo-dd
..
.de IP
. mo-start-dl
<dt>
<b>\\$1</b>
. it 1 mo-dd
..
.de mo-start-dl
. end-preformat
. if !\\n[mo-in-dl] <dl compact>
. nr mo-in-dl 1
..
.de mo-dd
<dd>
..
.de mo-end-dl
. if \\n[mo-in-dl] </dl>
. nr mo-in-dl 0
..
.de P
. end-preformat
. mo-end-dl
<p>
..
.als PP P
.als LP P
.de mo-try-link
. nr mo-did-link 0
. if \\A'\\$2' \{\
. if \\w'\\*[\\$2]' \{\
. Xr \\$1 \\*[\\$2]
. nr mo-did-link 1
. \}
. \}
..
.ds (1) 1
.ds (2) 2
.ds (3) 3
.ds (4) 4
.ds (5) 5
.ds (6) 6
.ds (7) 7
.ds (8) 8
.ds (9) 9
.ds (1), 1
.ds (2), 2
.ds (3), 3
.ds (4), 4
.ds (5), 5
.ds (6), 6
.ds (7), 7
.ds (8), 8
.ds (9), 9
.ds (1). 1
.ds (2). 2
.ds (3). 3
.ds (4). 4
.ds (5). 5
.ds (6). 6
.ds (7). 7
.ds (8). 8
.ds (9). 9
Reference in New Issue Copy Permalink