-
Notifications
You must be signed in to change notification settings - Fork 45
/
Copy pathmmark.1
121 lines (106 loc) · 3.39 KB
/
mmark.1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "MMARK" 1 "April 2019" "User Commands" "Mmark Markdown"
.SH "NAME"
.PP
mmark \- generate XML, HTML or manual pages from mmark markdown documents.
.SH "SYNOPSIS"
.PP
\fBmmark\fP [\fBOPTIONS\fP] [\fIFILE...\fP]
.SH "DESCRIPTION"
.PP
\fBMmark\fP is a powerful markdown processor written in Go, geared towards writing IETF documents. It
is, however, \fIalso\fP suited for writing complete books and other technical documentation.
.PP
Mmark provides an advanced markdown dialect that processes file(s) to produce internet\-drafts in XML
RFC 7991
\[la]https://tools.ietf.org/html/rfc7991\[ra] format. Mmark can produce xml2rfc (aforementioned
RFC 7991), HTML5 and manual pages.
.PP
The syntax is detailed at https://mmark.miek.nl/syntax
\[la]https://mmark.miek.nl/syntax\[ra].
.PP
Compared to other markdown variants mmark adds:
.IP \(bu 4
(Extended) title block to specify authors and IETF specific bits.
.IP \(bu 4
(Special) sections for abstracts, prefaces or notes.
.IP \(bu 4
Including other files with the option to specify line ranges, regular expressions and/or
prefixing each line with a custom string.
.IP \(bu 4
Document divisions: front matter, main matter and back matter.
.IP \(bu 4
Captions for code, tables, quotes and subfigures.
.IP \(bu 4
Asides for small notes.
.IP \(bu 4
Figures and subfigures that allow for grouping images into subfigures as well as giving a single
image metadata (a link, attributes, etc.).
.IP \(bu 4
Block Level Attributes that allow to specify attributes, classes and IDs for elements.
.IP \(bu 4
Indices to mark an item (and/or a subitem) to be referenced in the document index.
.IP \(bu 4
Citations and adding XML References (those used by the IETF).
.IP \(bu 4
Cross references: short form of referencing a section in the document.
.IP \(bu 4
Super\- and subscript.
.IP \(bu 4
Callouts in code and text.
.IP \(bu 4
BCP14 (RFC 2119) keyword detection.
.SH "RFC 7991"
.PP
This is the XML format used by the RFC editor for accepting Internet\-Drafts.
.SH "HTML5"
.PP
The HTML5 renderer outputs HTML.
.SH "MANUAL PAGES"
.PP
The man renderer outputs nroff that can be viewed via man(1).
.SH "OPTIONS"
.TP
\fB\fC-ast\fR
print abstract syntax tree and exit
.TP
\fB\fC-fragment\fR
don't create a full document
.TP
\fB\fC-css\fR \fIURL\fP
\fIURL\fP to a CSS stylesheet (only used with \-html)
.TP
\fB\fC-head\fR \fIURL\fP
\fIURL\fP to HTML to be included in head (only used with \-html)
.TP
\fB\fC-html\fR
create HTML output
.TP
\fB\fC-man\fR
output nroff (manual pages)
.TP
\fB\fC-unsafe\fR
allow includes from anywhere in the filesystem, otherwise they are only allowed \fIbelow\fP the
current document
.TP
\fB\fC-unicode\fR
allow unicode characters in <t>, from xml2rfc 3.16.0 this is allowed. It's true by default, set
to false if you have an older xml2rfc version. Note the <u> text/html output produced by
xml2rfc is (extremely) verbose.
.TP
\fB\fC-index\fR
generate an index at the end of the document (default true)
.TP
\fB\fC-bibliography\fR
generate a bibliography section after the back matter (default true), this \fIneeds\fP a
\fB\fC{{backmatter}}\fR in the document
.TP
\fB\fC-version\fR
show mmark's version
.SH "ALSO SEE"
.PP
RFC 7991 and (maybe) RFC 7749. The main site for Mmark is
https://mmark.miek.nl
\[la]https://mmark.miek.nl\[ra]. The syntax used by mmark is explained in the syntax
page
\[la]https://mmark.miek.nl/post/syntax/\[ra].