чување 5c6828c9a64eb0f441db59b2ebcb6c214f8e2c7b
родитељ 22af0e44ed5cbf6174b930f8943c1eb63f17441d
Аутор: Страхиња Радић <contact@strahinja.org>
Датум: Mon, 15 May 2023 07:48:45 +0200
slweb.1.in: \fP -> \fR (some "resets" were incorrect)
Signed-off-by: Страхиња Радић <contact@strahinja.org>
Diffstat:
| M | slweb.1.in | | | 220 | ++++++++++++++++++++++++++++++++++++++++---------------------------------------- |
измењених датотека: 1, додавања: 110(+), брисања: 110(-)
diff --git a/slweb.1.in b/slweb.1.in
@@ -55,15 +55,15 @@ custom Markdown-like syntax into
.TQ
.B \-\-body\-only
.br
-Only add the contents of the \fC<body>\fP tag, skipping \fC<html>\fP and
-\fC<head>\fP.
+Only add the contents of the \fC<body>\fR tag, skipping \fC<html>\fR and
+\fC<head>\fR.
.
.TP
.BI \-d " directory"
.TQ
.BI \-\-basedir " directory"
.br
-Set the base directory for includes (\fC{include}\fP and \fC{incdir}\fP) and
+Set the base directory for includes (\fC{include}\fR and \fC{incdir}\fR) and
favicons. Defaults to the current directory (\[lq].\[rq]).
.
.TP
@@ -100,24 +100,24 @@ are using a minimal subset of Markdown with added directives.
.
.IP \[bu] 4
.BR Backticks .
-Text inside \fC`backticks`\fP will be put inside \fC<code></code>\fP. Text
-surrounded by triple backticks (\fC```\fP) on the lines by themselves will be
-put inside \fC<pre></pre>\fP. Any \[lq]less-than\[rq] character inside backticks
-will be converted to \fC<\fP. Any text following the first triple backticks
+Text inside \fC`backticks`\fR will be put inside \fC<code></code>\fR. Text
+surrounded by triple backticks (\fC```\fR) on the lines by themselves will be
+put inside \fC<pre></pre>\fR. Any \[lq]less-than\[rq] character inside backticks
+will be converted to \fC<\fR. Any text following the first triple backticks
until the end of the line will be ignored. This is to account for language
highlighting specification, which isn't yet supported.
.
.IP \[bu]
.BR Blockquotes .
-Starting the line with \fC>\fP will surround it with a \fC<blockquote>\fP tag.
+Starting the line with \fC>\fR will surround it with a \fC<blockquote>\fR tag.
Multiple lines are supported.
.
.IP \[bu]
.BR Bold/italic .
-Text inside \fC*asterisks*\fP or \fC_underlines_\fP will be put inside
-\fC<em></em>\fP. Text inside \fC**double asterisks**\fP or \fC__double
-underlines__\fP will be put inside \fC<strong></strong>\fP. \fC***More than
-two*** of the ___same symbol___\fP should be avoided.
+Text inside \fC*asterisks*\fR or \fC_underlines_\fR will be put inside
+\fC<em></em>\fR. Text inside \fC**double asterisks**\fR or \fC__double
+underlines__\fR will be put inside \fC<strong></strong>\fR. \fC***More than
+two*** of the ___same symbol___\fR should be avoided.
.
.IP \[bu]
.BR "Footnotes (regular and inline)" .
@@ -160,7 +160,7 @@ With a footnote!</p>
.
.IP \- 4
.B Inline footnotes
-can be added by using the construct \fC^[footnotetext]\fP. For example, input
+can be added by using the construct \fC^[footnotetext]\fR. For example, input
.
.CDS 8
Inline footnote^[Footnote text] in a paragraph.
@@ -184,7 +184,7 @@ The horizontal rule and the list of footnotes is output only once, before the
end of
.SM HTML
document body. Rule and the list of footnotes can be surrounded by a div with
-the \[lq]\fCfootnotes\fP\[rq] id by setting the
+the \[lq]\fCfootnotes\fR\[rq] id by setting the
.SM YAML
variable
.I add-footnote-div
@@ -201,15 +201,15 @@ encounters both footnote types in the same document, a warning will be issued to
.
.IP \[bu]
.BR Headings .
-A line starting with \fC#\fP followed by space will be put inside
-\fC<h?></h?>\fP, where \fC?\fP stands for 1-4, depending on the number of
-hash signs. Tags will have \fCid\fP attributes set to \fCheading-?\fP, with
-\fC?\fP set to the number representing its position within the list of all
+A line starting with \fC#\fR followed by space will be put inside
+\fC<h?></h?>\fR, where \fC?\fR stands for 1-4, depending on the number of
+hash signs. Tags will have \fCid\fR attributes set to \fCheading-?\fR, with
+\fC?\fR set to the number representing its position within the list of all
headings.
.
.IP \[bu]
.BR "Horizontal rules" .
-Three dashes at the start of the line will produce a \fC<hr />\fP in the output.
+Three dashes at the start of the line will produce a \fC<hr />\fR in the output.
As this Markdown feature clashes with
.SM YAML
block boundaries, it will work only if
@@ -218,7 +218,7 @@ block is present in the input and before the three dashes for the horizontal
rule. Any text following the three dashes on the same line will be ignored.
.
.IP
-Alternatively, three asterisks (\fC***\fP) can be used instead of dashes,
+Alternatively, three asterisks (\fC***\fR) can be used instead of dashes,
avoiding the necessity for a
.SM YAML
block preceding the asterisks.
@@ -245,10 +245,10 @@ Which will produce:
.CDE
.
.IP
-The attributes \fCwidth\fP and \fCheight\fP will be determined automatically
+The attributes \fCwidth\fR and \fCheight\fR will be determined automatically
using the command
.BR identify (1)
-(if present), provided the \fCsrc\fP attribute contains a valid file path. (Also
+(if present), provided the \fCsrc\fR attribute contains a valid file path. (Also
see
.BR image-file-prefix ).
.
@@ -258,7 +258,7 @@ used, using the image id instead of the direct
.SM URL.
.
.IP
-If the additional link or \fC<figure>\fP/\fC<figcaption>\fP tags are not
+If the additional link or \fC<figure>\fR/\fC<figcaption>\fR tags are not
desirable, they can be turned off by setting
.B add-image-links
and
@@ -267,13 +267,13 @@ to \[lq]0\[rq].
.
.IP \[bu]
.BR "Keyboard tags" .
-Text inside \fC||double bars||\fP will be put inside \fC<kbd></kbd>\fP tags. As
+Text inside \fC||double bars||\fR will be put inside \fC<kbd></kbd>\fR tags. As
with backticks, any \[lq]less-than\[rq] character will be converted to
-\fC<\fP.
+\fC<\fR.
.
.IP \[bu]
.BR "Line breaks" .
-Two spaces followed by a newline will become \fC<br />\fP.
+Two spaces followed by a newline will become \fC<br />\fR.
.
.IP \[bu]
.BR Links .
@@ -281,14 +281,14 @@ Two spaces followed by a newline will become \fC<br />\fP.
.RS
.IP \- 4
.BR "Inline links" .
-The construct \fC[A link](https://example.com)\fP will be converted into \fC<a
-href="https://example.com">A link</a>\fP.
+The construct \fC[A link](https://example.com)\fR will be converted into \fC<a
+href="https://example.com">A link</a>\fR.
.
.IP ""
-Special case is the form \fC[=somemacro Link title](https://anything)\fP which
+Special case is the form \fC[=somemacro Link title](https://anything)\fR which
prepends the body of a macro
.I somemacro
-into the \fC<a></a>\fP tag (here broken into multiple lines for clarity):
+into the \fC<a></a>\fR tag (here broken into multiple lines for clarity):
.
.CDS 8
<a href="https://anything">
@@ -303,8 +303,8 @@ icons to links. See
.BR Macros .
.
.IP "" 4
-Also, the form \fC[(Link title)](http://asite.com)\fP will surround the link
-title (text between \fC<a></a>\fP tags) with \fC<span></span>\fP, like so:
+Also, the form \fC[(Link title)](http://asite.com)\fR will surround the link
+title (text between \fC<a></a>\fR tags) with \fC<span></span>\fR, like so:
.
.CDS 8
<a href="http://asite.com"><span>Link title</span></a>
@@ -321,7 +321,7 @@ macro-form:
.IP
It will prepend the body of a macro
.I somemacro
-outside of the \fC<span></span>\fP:
+outside of the \fC<span></span>\fR:
.
.CDS 8
<a href="http://asite.com">
@@ -330,10 +330,10 @@ outside of the \fC<span></span>\fP:
.CDE
.
.IP
-Exception is the form \fC[Some text (parenthesized)](https://somelink)\fP, which
-won't output \fC<span>\fP tags, and will simply include the parentheses in the
+Exception is the form \fC[Some text (parenthesized)](https://somelink)\fR, which
+won't output \fC<span>\fR tags, and will simply include the parentheses in the
output instead. This form doesn't apply to macro-form \fC[=macro Some
-(text)](http://link)\fP, which will always output \fC<span>\fP tags.
+(text)](http://link)\fR, which will always output \fC<span>\fR tags.
.
.IP \-
.BR "Regular links" .
@@ -341,7 +341,7 @@ Everything said about inline links applies to regular links, with the exception
that instead of the parenthesized
.SM URL,
link text inside brackets should be followed by link id (different than the
-\[lq]\fCid\fP\[rq]
+\[lq]\fCid\fR\[rq]
.IR attribute! )
inside brackets, and a
separate definition of that link id is needed, usually near the end of input.
@@ -369,7 +369,7 @@ This can help reduce the amount of code in the text of the page.
.
.IP \[bu] 4
.BR Lists .
-Lines starting with a dash (\fC\-\fP), an asterisk (\fC*\fP) or lowercase
+Lines starting with a dash (\fC\-\fR), an asterisk (\fC*\fR) or lowercase
\[lq]o\[rq], followed by a space, will start an unordered list (if used for the
first time) and start a list item. Input:
.
@@ -430,24 +430,24 @@ otherwise start a list shall just be inserted as-is in the output.
.
.IP \[bu] 4
.BR "Non\-breaking hyphen" .
-Tilde followed by a hyphen (\fC~-\fP) will insert \fC‑\fP in the output.
+Tilde followed by a hyphen (\fC~-\fR) will insert \fC‑\fR in the output.
.
.IP \[bu] 4
.BR "Non\-breaking space" .
-Two consecutive tildes (\fC~~\fP) will produce \fC \fP in the output.
+Two consecutive tildes (\fC~~\fR) will produce \fC \fR in the output.
.
.IP \[bu] 4
.BR Paragraphs .
-Text surrounded by newlines will be put inside \fC<p></p>\fP tags. See
+Text surrounded by newlines will be put inside \fC<p></p>\fR tags. See
.SM "KNOWN LIMITATIONS."
.
.IP \[bu] 4
.BR Strikethrough .
-Text surrounded by tildes (\fC~\fP) will be put inside \fC<s></s>\fP.
+Text surrounded by tildes (\fC~\fR) will be put inside \fC<s></s>\fR.
.
.IP \[bu] 4
.BR Tables .
-Lines starting with vertical bars (\fC|\fP) will be transformed into
+Lines starting with vertical bars (\fC|\fR) will be transformed into
.SM HTML
tables. The first such line is treated as a header row, second as the alignment
specifier (currently ignored), and the rest regular rows. Table cells and header
@@ -483,7 +483,7 @@ or
.SM CSV
directive. In order for tables to work with templating, they need two additional
lines at the top and the bottom, to mark the start and the end of the table. All
-the lines in partial tables need to start with \[lq]\fC|@\fP\[rq], with only the
+the lines in partial tables need to start with \[lq]\fC|@\fR\[rq], with only the
character following at-mark being different:
.
.CDS 8
@@ -509,10 +509,10 @@ example only for aesthetic purposes. See
.LP
Math mode is supported through KaTeX. With
.BR katex
-installed, anything between dollar signs (\fC$\fP) will be transformed into
+installed, anything between dollar signs (\fC$\fR) will be transformed into
MathML and
.SM HTML
-markup. To generate display math, use double dollar signs (\fC$$\fP). The text
+markup. To generate display math, use double dollar signs (\fC$$\fR). The text
between the dollar signs in both cases should be LaTeX source code, and is
passed to
.BR katex .
@@ -529,74 +529,74 @@ variables (see
.
.IP \[bu] 4
.BR "Brand \[lq]watermark\[rq]" .
-Directive \fC{made\-by}\fP results in a div to be output at the end of the
-document, with the id \fCmade\-by\fP containing the \[lq]watermark\[rq] text and
+Directive \fC{made\-by}\fR results in a div to be output at the end of the
+document, with the id \fCmade\-by\fR containing the \[lq]watermark\[rq] text and
a link to the
.B slweb
home page.
.
.IP \[bu] 4
.BR "General tags" .
-Directive \fC{sometag}{/sometag}\fP will be transformed into
-\fC<sometag></sometag>\fP.
+Directive \fC{sometag}{/sometag}\fR will be transformed into
+\fC<sometag></sometag>\fR.
.
.RS
.IP \- 4
.BR "Class attributes" .
-Directive \fC{tag.myclass mysecondclass}{/tag}\fP will be transformed into
-\fC<tag class="myclass mysecondclass"></tag>\fP. Only one class attribute is
+Directive \fC{tag.myclass mysecondclass}{/tag}\fR will be transformed into
+\fC<tag class="myclass mysecondclass"></tag>\fR. Only one class attribute is
permitted per tag directive (subsequent dots will be inserted as part of the
-\fCclass\fP attribute), but you can include multiple classes by separating them
+\fCclass\fR attribute), but you can include multiple classes by separating them
with a space, just like in
.SM HTML,
and you can have both a class attribute and an id attribute per tag.
-A variation of this is to use a special form \fC{.myclass}{/.myclass}\fP, which
-will be transformed into \fC<div class="myclass"></div>\fP.
+A variation of this is to use a special form \fC{.myclass}{/.myclass}\fR, which
+will be transformed into \fC<div class="myclass"></div>\fR.
.
.IP \-
.BR "Id attributes" .
-Directive \fC{tag#myid}{/tag}\fP will be transformed into \fC<tag
-id="myid"></tag>\fP. Only one id attribute is permitted per tag directive
-(subsequent hash signs will be included as part of the \fCid\fP attribute), and
+Directive \fC{tag#myid}{/tag}\fR will be transformed into \fC<tag
+id="myid"></tag>\fR. Only one id attribute is permitted per tag directive
+(subsequent hash signs will be included as part of the \fCid\fR attribute), and
you can have both an id attribute and a class attribute per tag.
-A variation of this is to use a special form \fC{#myid}{/#myid}\fP, which will
-be transformed into \fC<div id="myid"></div>\fP.
+A variation of this is to use a special form \fC{#myid}{/#myid}\fR, which will
+be transformed into \fC<div id="myid"></div>\fR.
.RE
.
.IP \[bu]
.BR Includes .
-Directive \fC{include "somefile"}\fP will fork, parse
+Directive \fC{include "somefile"}\fR will fork, parse
.I somefile.slw
(related to
.IR basedir )
and output the resulting
.SM HTML
-as if the option \fC\-\-body\-only\fP was specified. All
+as if the option \fC\-\-body\-only\fR was specified. All
.SM YAML
variables will be preserved.
.
.IP \[bu]
.BR Macros .
-Macros can be declared using the directive \fC{=!macroname}{/=!macroname}\fP,
+Macros can be declared using the directive \fC{=!macroname}{/=!macroname}\fR,
where
.I macroname
is the name of the macro. Anything between those two tags will then become the
-body of a macro. Whenever \fC{=macroname}\fP is subsequently encountered in the
+body of a macro. Whenever \fC{=macroname}\fR is subsequently encountered in the
file, it will be replaced by the macro body. Macro definitions can't be nested
nor can they contain macro calls, and doing so will produce an error. Tags won't
be processed within the body of a macro.
.
.IP \[bu]
.BR "Previous Git commit information" .
-Directive \fC{git-log}\fP is converted into a div with the id \fCgit-log\fP
+Directive \fC{git-log}\fR is converted into a div with the id \fCgit-log\fR
containing the information about the previous commit (as having information
about the current commit would be impossible).
.
.IP \[bu]
.BR "Subdirectory inclusion (blogging directive)" .
-The command \fC{incdir "\fIdirname\fC" \fInum\fC =\fImacroname\fC}\fP
+The command \fC{incdir "\fIdirname\fC" \fInum\fC =\fImacroname\fC}\fR
.RI ( num
and
.I macroname
@@ -605,7 +605,7 @@ are optional) will be expanded as follows:
.RS
.nr list 1 1
.IP \n[list]. 4
-A \fC<ul class="incdir">\fP tag will be inserted into the document instead of
+A \fC<ul class="incdir">\fR tag will be inserted into the document instead of
the directive.
.
.IP \n+[list].
@@ -613,14 +613,14 @@ For every subdirectory of
.IR dirname ,
relative to current directory and up to
.I num
-(if present) or 5 (if omitted) total subdirectories, a \fC<li>\fP
-tag will be inserted into the \fCul\fP tag.
+(if present) or 5 (if omitted) total subdirectories, a \fC<li>\fR
+tag will be inserted into the \fCul\fR tag.
.
.IP \n+[list].
-A \fC<details>\fP tag will be inserted into each \fC<li>\fP tag.
+A \fC<details>\fR tag will be inserted into each \fC<li>\fR tag.
.
.IP \n+[list].
-Inside the \fC<details>\fP tag, a \fC<summary>\fP tag will be inserted with the
+Inside the \fC<details>\fR tag, a \fC<summary>\fR tag will be inserted with the
name of the subdirectory. If
.I macroname
is present, the name of the subdirectory will be prepended with the body of a
@@ -631,8 +631,8 @@ macro
markup as arrows).
.
.IP \n+[list].
-After the \fC<summary>\fP tag a \fC<div>\fP tag will be inserted into
-\fC<details>\fP, containing the concatenated output from processing each of the
+After the \fC<summary>\fR tag a \fC<div>\fR tag will be inserted into
+\fC<details>\fR, containing the concatenated output from processing each of the
.I .slw
files inside that subdirectory in reverse lexicographical order, in a manner
similar to the
@@ -645,16 +645,16 @@ directive. (See
.IP \[bu]
.BR "TSV/CSV templating" .
Directive \fC{tsv "\f[CI]tsvfile\fC" \f[CI]iter\fC}{/tsv}\fR marks a template.
-Whatever is between \fC{tsv}\fP and \fC{/tsv}\fP will be processed by
+Whatever is between \fC{tsv}\fR and \fC{/tsv}\fR will be processed by
.B slweb
-and collected as a template. Afterwards, file \fItsvfile.tsv\fP will be read and
+and collected as a template. Afterwards, file \fItsvfile.tsv\fR will be read and
for each of its lines (up to
.IR iter ,
if present) the collected template will be output, substituting each occurrence
-of a register mark \fC$\f[CI]n\fR (where \fIn\fP is between 1 and 9, inclusive)
+of a register mark \fC$\f[CI]n\fR (where \fIn\fR is between 1 and 9, inclusive)
with the corresponding
.SM TSV
-field of the read line. All of this applies to the similar \fC{csv}\fP directive
+field of the read line. All of this applies to the similar \fC{csv}\fR directive
for
.SM CSV
files. In the case of
@@ -667,15 +667,15 @@ variable in the calling
.I .slw
file) and double quotation marks (") as field boundaries. First line in the
.SM TSV
-file is parsed as a header and associated with register marks \fC$#1\fP to
-\fC$#9\fP. The symbol $ is represented as \fC$$\fP. Consequently, math modes
+file is parsed as a header and associated with register marks \fC$#1\fR to
+\fC$#9\fR. The symbol $ is represented as \fC$$\fR. Consequently, math modes
(both inline and display) cannot be used within templates.
.
.IP "" 8
Parts of the template can be conditionally rendered by using the construct:
.
.CDS 8
-$?\f[CI]n\fP
+$?\f[CI]n\fR
<!-- code to include if $\f[CI]n\f[CR] nonempty -->
$?!
<!-- code to include if $\f[CI]n\f[CR] empty -->
@@ -683,8 +683,8 @@ $?/
.CDE
.
.IP "" 4
-where \fIn\fP is between 1 and 9, inclusive. For example, having a file
-\fIsales.tsv\fP:
+where \fIn\fR is between 1 and 9, inclusive. For example, having a file
+\fIsales.tsv\fR:
.
.CDS 8
Item Q1 2020 Q2 2020 Q3 2020 Q4 2020
@@ -740,18 +740,18 @@ directives can't be nested and doing so will produce an error.
.IP \[bu] 4
.BR add-article-header .
If set to \[lq]1\[rq], title, date and header text at the beginning of the
-output body will be enclosed in a \fC<header>\fP tag.
+output body will be enclosed in a \fC<header>\fR tag.
.
.IP \[bu]
.BR add-figcaption .
-If set to \[lq]0\[rq], \fC<figure>\fP and \fC<figcaption>\fP tags around images
+If set to \[lq]0\[rq], \fC<figure>\fR and \fC<figcaption>\fR tags around images
will not be added (otherwise they will by default, see
.BR Images ).
.
.IP \[bu]
.BR add-footnote-div .
If set to \[lq]1\[rq], list of footnotes preceded by a horizontal rule will be
-surrounded with a div having the id \[lq]\fCfootnotes\fP\[rq] (see
+surrounded with a div having the id \[lq]\fCfootnotes\fR\[rq] (see
.BR Footnotes ).
.
.IP \[bu]
@@ -763,13 +763,13 @@ will by default, see
.IP \[bu]
.BR author .
If set, the contents of this variable will be added to the start of the output
-body (inside a \fC<header>\fP tag if it is set), surrounded by
-\fC<address></address>\fP.
+body (inside a \fC<header>\fR tag if it is set), surrounded by
+\fC<address></address>\fR.
.
.IP \[bu]
.BR canonical .
-Contents of this variable will be added as a value of a \fCrel\fP attribute for
-the \fC<link rel="canonical" />\fP tag.
+Contents of this variable will be added as a value of a \fCrel\fR attribute for
+the \fC<link rel="canonical" />\fR tag.
.
.IP \[bu]
.BR csv-delimiter .
@@ -796,8 +796,8 @@ If set to \[lq]0\[rq], permalinks generated by the
.I incdir
directive will not have the extension included in the
.I href
-attribute. For example, instead of \fCblog/2020/august.html\fP, the resulting
-permalink will have \fCblog/2020/august\fP.
+attribute. For example, instead of \fCblog/2020/august.html\fR, the resulting
+permalink will have \fCblog/2020/august\fR.
.
.IP \[bu]
.BR favicon-url .
@@ -805,32 +805,32 @@ If present, this
.SM URL
will be used as a favicon
.SM URL
-instead of the default, \fC/favicon.ico\fP.
+instead of the default, \fC/favicon.ico\fR.
.
.IP \[bu]
.BR feed ", " feed-desc .
-If both are present, contents of those variables will be added as \fIhref\fP and
-\fItitle\fP attributes (respectively) to the \fC<link rel="alternate"
-type="application/rss+xml">\fP tag in the page's \fC<head>\fP.
+If both are present, contents of those variables will be added as \fIhref\fR and
+\fItitle\fR attributes (respectively) to the \fC<link rel="alternate"
+type="application/rss+xml">\fR tag in the page's \fC<head>\fR.
.
.IP \[bu]
.BR header-text .
The contents of this variable will be added to the start of the output body
-(inside a \fC<header>\fP tag if it is set), surrounded by \fC<p></p>\fP.
+(inside a \fC<header>\fR tag if it is set), surrounded by \fC<p></p>\fR.
.
.IP \[bu]
.BR image-file-prefix .
-If present, the value of \fCsrc\fP attribute will be appended to the contents of
+If present, the value of \fCsrc\fR attribute will be appended to the contents of
this variable, with path separator added as necessary, when determining the
actual file path to pass to the
.BR identify (1)
-command. Otherwise, \fCsrc\fP is appended to \[lq].\[rq].
+command. Otherwise, \fCsrc\fR is appended to \[lq].\[rq].
.
.IP \[bu]
.BR inline-stylesheet .
The contents of this variable will be treated as a
.SM CSS
-file name to be included inline in the header using the \fC<style>\fP tag. You
+file name to be included inline in the header using the \fC<style>\fR tag. You
can add more than one
.I inline-stylesheet
declaration per
@@ -839,8 +839,8 @@ file.
.
.IP \[bu]
.BR lang .
-Contents of this variable will be used for the \fClang\fP attribute of the
-\fC<html>\fP tag.
+Contents of this variable will be used for the \fClang\fR attribute of the
+\fC<html>\fR tag.
.
.IP \[bu]
.BR link-prefix .
@@ -861,7 +861,7 @@ content="\f[CI]secondcol\fC" />\fR is inserted, where
is the first column, and
.I secondcol
is the second column. If the values in the second column are surrounded with
-percent signs (\fC%\fP), the value between them is treated as the name of the
+percent signs (\fC%\fR), the value between them is treated as the name of the
YAML variable to insert. For example, having the file
.IR m.tsv :
.
@@ -912,18 +912,18 @@ directive.
.BR site-desc .
The contents of this variable will be inserted as the value of the
.I content
-attribute of the \fC<meta name="description">\fP tag.
+attribute of the \fC<meta name="description">\fR tag.
.
.IP \[bu]
.BR site-name .
-The contents of this variable will be inserted inside the \fC<title></title>\fP
+The contents of this variable will be inserted inside the \fC<title></title>\fR
tags.
.
.IP \[bu]
.BR stylesheet .
The contents of this variable will be treated as a
.SM CSS
-file name to be included using the \fC<link rel="stylesheet" />\fP tag. You can
+file name to be included using the \fC<link rel="stylesheet" />\fR tag. You can
add more than one
.I stylesheet
declaration per
@@ -933,10 +933,10 @@ file.
.IP \[bu]
.BR title .
If present, contents of this variable will be prepended to the body (inside a
-\fC<header>\fP tag if it is set) as a heading with the level determined by the
+\fC<header>\fR tag if it is set) as a heading with the level determined by the
.I title-heading-level
variable, defaulting
-to 2. (\fCtitle: Some title\fP becomes \fC<h2>Some title</h2>\fP).
+to 2. (\fCtitle: Some title\fR becomes \fC<h2>Some title</h2>\fR).
.
.IP \[bu]
.BR title-heading-level .
@@ -958,7 +958,7 @@ directive, similar to the macro-form of links.
.SH EXAMPLES
.
.LP
-Given the file \fCindex.slw\fP in the current directory:
+Given the file \fCindex.slw\fR in the current directory:
.CDS 4
---
site-name: Test website
@@ -976,7 +976,7 @@ after using the command:
.CDS 4
$ slweb index.slw > index.html
.CDE
-file \fCindex.html\fP contains:
+file \fCindex.html\fR contains:
.CDS 4
<!DOCTYPE html>
<html lang="en">
@@ -1003,7 +1003,7 @@ file \fCindex.html\fP contains:
.
.IP \[bu] 4
Currently there is no way to determine where the paragraph inside a tag should
-begin and end without adding blank lines or using the \fC{p}{/p}\fP notation.
+begin and end without adding blank lines or using the \fC{p}{/p}\fR notation.
For example, the code
.
.CDS 8
