~mdw
/
sgt
/
halibut
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
Various HTML backend cleanups.
[sgt/halibut]
/
doc
/
input.but
diff --git
a/doc/input.but
b/doc/input.but
index
d696fc4
..
d99f5ce
100644
(file)
--- a/
doc/input.but
+++ b/
doc/input.but
@@
-192,7
+192,8
@@
Here is some \q{text in quotes}.
}
and in every output format Halibut generates, it will choose the
}
and in every output format Halibut generates, it will choose the
-best quote characters available to it in that format.
+best quote characters available to it in that format. (The quote
+characters to use can be configured with the \c{\\cfg} command.)
You can still use the ordinary quote characters of your choice if
you prefer; or you could even use the \c{\\u} command (see
You can still use the ordinary quote characters of your choice if
you prefer; or you could even use the \c{\\u} command (see
@@
-1368,6
+1369,10
@@
Halibut would fall back to using the ASCII double quote character as
\e{both} open and close quotes. (No known character set is that
silly; I mention it only as an example.)
\e{both} open and close quotes. (No known character set is that
silly; I mention it only as an example.)
+\cw{\\cfg\{quotes\}} (and the backend-specific versions) apply to the
+\e{entire} output; it's not possible to change quote characters
+partway through the output.
+
}
In addition to these configuration commands, there are also
}
In addition to these configuration commands, there are also