README, INSTALLING, CHANGELOG.md, LICENSE, AUTHORS
manpages(5), Markdown syntax, man(1), roff(7), groff(1), mustache(5), pandoc(1)
Copyright © 2010 Ryan Tomayko, © 2018, 2019, 2020, 2022, 2023 Andrew Janke, © 2022 Takuya Noguchi
\fR\.
.TP
\fB**double\-stars**\fR (markdown compatible)
Also displayed in boldface\. Unlike backticks, inline markup is processed\. HTML output: \fB\fR\.
.TP
\fB\fR (non\-compatible markdown extension)
User\-specified arguments, variables, or user input\. Typically displayed with \fIunderline\fR in roff output\. HTML output: \fB\fR\.
.TP
\fB_\fR\fIunderbars\fR\fB_\fR (markdown compatible)
Emphasis\. May be used for literal option values\. Typically displayed with \fIunderline\fR in roff output\. HTML output: \fB\fR\.
.P
Here is grep(1)'s DESCRIPTION section represented in \fBronn\fR:
.IP "" 4
.nf
`Grep` searches the named input (or standard input if
no files are named, or the file name `\-` is given) for lines
containing a match to the given \. By default, `grep`
prints the matching lines\.
.fi
.IP "" 0
.SH "DEFINITION LISTS"
The definition list syntax is compatible with markdown's unordered list syntax but requires that the first line of each list item be terminated with a colon "\fB:\fR" character\. The contents of the first line is the \fIterm\fR; subsequent lines may be comprised of multiple paragraphs, code blocks, standard lists, and nested definition lists\.
.P
An example definition list, taken from BSD test(1)'s \fIDESCRIPTION\fR section:
.IP "" 4
.nf
The following primaries are used to construct expressions:
* `\-b` :
True if exists and is a block special file\.
* `\-c` :
True if _file_ exists and is a character special file\.
* `\-d` :
True if file exists and is a directory\.
.fi
.IP "" 0
.SH "LINKS"
All markdown(7) linking features are supported\.
.P
Markdown reference\-style links can be used to link to specific sections by name:
.IP "" 4
.nf
## SECTION 1
See the following section\.
## SECTION 2
See [SECTION 1][] or [to put it another way][SECTION 1]\.
.fi
.IP "" 0
.P
The anchor name would be \fB#SECTION\-1\fR and \fB#SECTION\-2\fR\. All non\-word characters are removed and spaces are replaced by dashes\.
.SH "SEE ALSO"
ronn(1), markdown(7), roff(7)
ronn-ng-0.10.1/man/ronn-format.7.ronn 0000664 0000000 0000000 00000011211 14546711747 0017243 0 ustar 00root root 0000000 0000000 ronn-format(7) -- manual authoring format based on Markdown
===========================================================
## SYNOPSIS
name(1) -- short, single-sentence description
=============================================
## SYNOPSIS
`name` [...]
## DESCRIPTION
A normal paragraph. This can span multiple lines and is terminated with two
or more line endings -- just like Markdown.
Inline markup for `code`, `user input`, and **strong** are displayed
boldface; , _emphasis_, *emphasis*, are displayed in italics
(HTML) or underline (roff).
Manual references like sh(1), markdown(7), roff(7), etc. are hyperlinked in
HTML output.
Link to sections like [STANDARDS][], [SEE ALSO][], or [WITH A DIFFERENT LINK
TEXT][#SEE-ALSO].
Definition lists:
* `-a`, `--argument`=[]:
One or more paragraphs describing the argument.
* You can put whatever you *want* here, really:
Nesting and paragraph spacing are respected.
Frequently used sections:
## OPTIONS
## SYNTAX
## ENVIRONMENT
## RETURN VALUES
## STANDARDS
## SECURITY CONSIDERATIONS
## BUGS
## HISTORY
## AUTHOR
## COPYRIGHT
## SEE ALSO
## DESCRIPTION
The ronn(1) command converts text in a simple markup to Unix manual pages. The
syntax includes all Markdown formatting features, plus conventions for
expressing the structure and various notations present in standard Unix
manpages.
Not all roff(7) typesetting features can be expressed using ronn syntax.
## MANPAGE TITLE
Manpages have a , , and a one-line . Files must
start with a level one heading defining these attributes:
ls(1) -- list directory contents
================================
Indicates that the manpage is named `ls` in manual section `1` ("user
commands").
## SECTION HEADINGS
Man section headings are expressed with markdown level two headings. There
are two syntaxes for level two headings.
Hash prefix syntax:
## HEADING TEXT
Dash underline syntax:
HEADING TEXT
------------
Section headings should be all uppercase and may not contain inline markup.
## INLINE MARKUP
Manpages have a limited set of text formatting capabilities. There's basically
boldface and italics (often displayed using underline).
Ronn uses the following bits of markdown(7) to accomplish this:
* \`backticks\` (markdown compatible):
Code, flags, commands, and noun-like things; typically displayed in
boldface. All text included within `backticks` is displayed
literally; other inline markup is not processed. HTML output:
``.
* `**double-stars**` (markdown compatible):
Also displayed in boldface. Unlike backticks, inline markup is processed.
HTML output: ``.
* `` (non-compatible markdown extension):
User-specified arguments, variables, or user input. Typically displayed with
underline in roff output. HTML output: ``.
* `_`_underbars_`_` (markdown compatible):
Emphasis. May be used for literal option values. Typically displayed with
underline in roff output. HTML output: ``.
Here is grep(1)'s DESCRIPTION section represented in `ronn`:
`Grep` searches the named input (or standard input if
no files are named, or the file name `-` is given) for lines
containing a match to the given . By default, `grep`
prints the matching lines.
## DEFINITION LISTS
The definition list syntax is compatible with markdown's unordered list syntax
but requires that the first line of each list item be terminated with a colon
"`:`" character. The contents of the first line is the ; subsequent lines
may be comprised of multiple paragraphs, code blocks, standard lists, and nested
definition lists.
An example definition list, taken from BSD test(1)'s *DESCRIPTION* section:
The following primaries are used to construct expressions:
* `-b` :
True if exists and is a block special file.
* `-c` :
True if _file_ exists and is a character special file.
* `-d` :
True if file exists and is a directory.
## LINKS
All markdown(7) linking features are supported.
Markdown reference-style links can be used to link to specific sections by name:
## SECTION 1
See the following section.
## SECTION 2
See [SECTION 1][] or [to put it another way][SECTION 1].
The anchor name would be `#SECTION-1` and `#SECTION-2`. All non-word characters
are removed and spaces are replaced by dashes.
## SEE ALSO
ronn(1), markdown(7), roff(7)
ronn-ng-0.10.1/man/ronn.1 0000664 0000000 0000000 00000030473 14546711747 0015007 0 ustar 00root root 0000000 0000000 .\" generated with Ronn-NG/v0.10.1
.\" http://github.com/apjanke/ronn-ng/tree/0.10.1
.TH "RONN" "1" "January 2024" "Ronn-NG 0.10.1" "Ronn Manual"
.SH "NAME"
\fBronn\fR \- convert markdown files to manpages
.SH "SYNOPSIS"
\fBronn\fR [\fIformat\fR\|\.\|\.\|\.] \fIfile\fR\|\.\|\.\|\.
.br
\fBronn\fR \fB\-m\fR|\fB\-\-man\fR \fIfile\fR\|\.\|\.\|\.
.br
\fBronn\fR \fB\-S\fR|\fB\-\-server\fR \fIfile\fR\|\.\|\.\|\.
.br
\fBronn\fR \fB\-\-pipe\fR \fIfile\fR
.br
\fBronn\fR < \fIfile\fR
.br
\fBronn\fR \fB\-E\fR|\fB\-\-encoding\fR \fIencoding\fR \|\.\|\.\|\.
.SH "DESCRIPTION"
\fBRonn\fR converts textfiles to standard roff\-formatted Unix manpages or HTML\. ronn\-format(7) is based on markdown(7) but includes additional rules and syntax geared toward authoring manuals\.
.P
In its default mode, \fBronn\fR converts one or more input \fIfile\fRs to HTML or roff output files\. The \fB\-\-roff\fR, \fB\-\-html\fR, and \fB\-\-fragment\fR options dictate which output files are generated\. Multiple format arguments may be specified to generate multiple output files\. Output files are named after and written to the same directory as input \fIfile\fRs\.
.P
The \fB\-\-server\fR and \fB\-\-man\fR options change the output behavior from file generation to serving dynamically generated HTML manpages or viewing \fIfile\fR as with man(1)\.
.P
With no \fIfile\fR arguments, \fBronn\fR acts as simple filter\. Ronn source text is read from standard input and roff output is written to standard output\. Use the \fB\-\-html\fR, \fB\-\-roff\fR, and/or \fB\-\-fragment\fR options to select the output format\.
.SH "FILES"
The \fBronn\fR command expects input to be valid ronn\-format(7) text\. Source files are typically named \fIname\fR\.\fIsection\fR\.ronn (e\.g\., \fBexample\.1\.ronn\fR)\. The \fIname\fR and \fIsection\fR should match the name and section defined in the \fIfile\fR's heading\.
.P
Source files must be in UTF\-8 encoding, or the encoding specified by the \fB\-E\fR/\fB\-\-encoding\fR option, regardless of the locale that \fBronn\fR is running under\.
.P
When building roff or HTML output files, destination filenames are determined by taking the basename of the input \fIfile\fR and adding the appropriate file extension (or removing the file extension in the case of roff output)\. For example, executing \fBronn example\.1\.ronn\fR generates \fBexample\.1\fR with roff output and \fBexample\.1\.html\fR with HTML output\.
.SH "OPTIONS"
These options control whether output is written to file(s), standard output, or directly to a man pager\.
.TP
\fB\-m\fR, \fB\-\-man\fR
Don't generate files, display \fIfile\fRs as if man(1) were invoked on the roff output file\. This simulates default man behavior by piping the roff output through groff(1) and the paging program specified by the \fBMANPAGER\fR environment variable\.
.TP
\fB\-S\fR, \fB\-\-server\fR
Don't generate files, start an HTTP server at \fIhttp://localhost:1207/\fR and serve dynamically generated HTML for the set of input \fIfile\fRs\. A file named \fIexample\.2\.ronn\fR is served as \fI/example\.2\.html\fR\. There's also an index page at the root with links to each \fIfile\fR\.
.IP
The server respects the \fB\-\-style\fR and document attribute options (\fB\-\-manual\fR, \fB\-\-date\fR, etc\.)\. These same options can be varied at request time by giving them as query parameters: \fB?manual=FOO&style=dark,toc\fR
.IP
\fINOTE: The builtin server is designed to assist in the process of writing and styling manuals\. It is in no way recommended as a general purpose web server\.\fR
.TP
\fB\-\-port\fR=\fIport\fR
When used with \fB\-S\fR/\fB\-\-server\fR, runs the server at the specified port instead of the default port 1207\.
.TP
\fB\-\-pipe\fR
Don't generate files, write generated output to standard output\. This is the default behavior when ronn source text is piped in on standard input and no \fIfile\fR arguments are provided\.
.TP
\fB\-o\fR=\fIdirectory\fR, \fB\-\-output\-dir\fR=\fIdirectory\fR
Write generated files to the specified directory instead of the default location\.
.TP
\fB\-E\fR=\fIencoding\fR, \fB\-\-encoding\fR=\fIencoding\fR
Specify the encoding that input files are in\. Default is UTF\-8, regardless of user's locale settings\. Input sent to STDIN is always treated as UTF\-8, regardless of whether \fB\-E\fR is passed\.
.P
Format options control the files \fBronn\fR generates, or the output format when the \fB\-\-pipe\fR argument is specified\. When no format options are given, both \fB\-\-roff\fR and \fB\-\-html\fR are assumed\.
.TP
\fB\-r\fR, \fB\-\-roff\fR
Generate roff output\. This is the default behavior when no \fIfile\fRs are given and ronn source text is read from standard input\.
.TP
\fB\-5\fR, \fB\-\-html\fR
Generate output in HTML format\.
.TP
\fB\-f\fR, \fB\-\-fragment\fR
Generate output in HTML format but only the document fragment, not the header, title, or footer\.
.P
Document attributes displayed in the header and footer areas of generated content are specified with these options\. (These values may also be set via the \fIENVIRONMENT\fR\.)
.TP
\fB\-\-manual\fR=\fImanual\fR
The name of the manual this man page belongs to; \fImanual\fR is prominently displayed top\-center in the header area\.
.TP
\fB\-\-organization\fR=\fIname\fR
The name of the group, organization, or individual responsible for publishing the document; \fIname\fR is displayed in the bottom\-left footer area\.
.TP
\fB\-\-date\fR=\fIdate\fR
The document's published date; \fIdate\fR must be formatted \fBYYYY\-MM\-DD\fR and is displayed in the bottom\-center footer area\. The \fIfile\fR mtime is used when no \fIdate\fR is given, or the current time when no \fIfile\fR is available\.
.P
HTML output can be customized through the use of CSS stylesheets:
.TP
\fB\-\-style\fR=\fImodule\fR[,\fImodule\fR]\|\.\|\.\|\.
The list of CSS stylesheets to apply to the document\. Multiple \fImodule\fR arguments may be specified, but must be separated by commas or spaces\.
.IP
When \fImodule\fR is a simple word, search for files named \fImodule\fR\fB\.css\fR in all directories listed in the \fI\fBRONN_STYLE\fR\fR environment variable, and then search internal styles\.
.IP
When \fImodule\fR includes a \fI/\fR character, use it as the full path to a stylesheet file\.
.IP
Internal styles are \fIman\fR (included by default), \fItoc\fR, and \fI80c\fR\. See \fISTYLES\fR for descriptions of features added by each module\.
.P
Miscellaneous options:
.TP
\fB\-w\fR, \fB\-\-warnings\fR
Show troff warnings on standard error when performing roff conversion\. Warnings are most often the result of a bug in ronn's HTML to roff conversion logic\.
.TP
\fB\-W\fR
Disable troff warnings\. Warnings are disabled by default\. This option can be used to revert the effect of a previous \fB\-w\fR argument\.
.TP
\fB\-v\fR, \fB\-\-version\fR
Show ronn version and exit\.
.SH "LINK INDEXES"
When generating HTML output, \fBronn\fR hyperlinks manual references (like \fBgrep(1)\fR, \fBls(1)\fR, \fBmarkdown(7)\fR) in source text based on reference name to URL mappings defined in an \fBindex\.txt\fR file\. Each line of the index file describes a single reference link, with whitespace separating the reference's \fIid\fR from its \fIlocation\fR\. Blank lines are allowed; lines beginning with a \fB#\fR character are ignored:
.IP "" 4
.nf
# manuals included in this project:
whisky(1) whisky\.1\.ronn
tango(5) tango\.5\.ronn
# external manuals
grep(1) https://man7\.org/linux/man\-pages/man1/grep\.1\.html
ls(1) https://man7\.org/linux/man\-pages/man1/ls\.1\.html
# other URLs for use with markdown reference links
src https://github\.com/
.fi
.IP "" 0
.P
The \fIlocation\fR is an absolute or relative URL that usually points at an HTML version of manpage\. It's possible to define references for things that aren't manpages\.
.P
All manuals in an individual directory share the references defined in that directory's \fBindex\.txt\fR file\. Index references may be used explicitly in Markdown reference style links using the syntax: \fB[\fR\fItext\fR\fB][\fR\fIid\fR\fB]\fR, where \fItext\fR is the link text and \fIid\fR is a reference name defined in the index\.
.SH "STYLES"
The \fB\-\-style\fR option selects a list of CSS stylesheets to include in the generated HTML\. Styles are applied in the order defined, so each can use the cascade to override previously defined styles\.
.SS "Builtin Stylesheets"
These styles are included with the distribution:
.TP
\fBman\fR
Basic manpage styles: typography, definition lists, indentation\. This is always included regardless of \fB\-\-style\fR argument\. It is however possible to replace the default \fBman\fR module with a custom one by placing a \fBman\.css\fR file on the \fBRONN_STYLE\fR path\.
.TP
\fBprint\fR
Basic print stylesheet\. The generated \fB