summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJacob Nevins <jacobn@chiark.greenend.org.uk>2004-06-19 17:08:59 +0000
committerJacob Nevins <jacobn@chiark.greenend.org.uk>2004-06-19 17:08:59 +0000
commitd54440be970569f644958a4473c2bb6c913d2887 (patch)
treebbd55071ee52de707677667e8b45df779bcdf43d
parentc648a1864a7a6c3067c49e8dba1d9339f807357f (diff)
downloadhalibut-d54440be970569f644958a4473c2bb6c913d2887.zip
halibut-d54440be970569f644958a4473c2bb6c913d2887.tar.gz
halibut-d54440be970569f644958a4473c2bb6c913d2887.tar.bz2
halibut-d54440be970569f644958a4473c2bb6c913d2887.tar.xz
The Unicode OVERLINE in the text backend documentation was probably supposed
to be quoted. [originally from svn r4299]
-rw-r--r--doc/output.but2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/output.but b/doc/output.but
index 68fc04e..5706f7d 100644
--- a/doc/output.but
+++ b/doc/output.but
@@ -110,7 +110,7 @@ example, \cw{\\text-title-underline\{=\}} but
You can also specify more than one underline setting, and Halibut
will choose the first one that the output character set supports.
So, for example, you could write
-\cw{\\text-chapter-underline\{\u203e\}\{\-\}}, and Halibut would use
+\cw{\\text-chapter-underline\{\\u203e\}\{\-\}}, and Halibut would use
the Unicode \q{OVERLINE} character where possible and fall back to
the ASCII minus sign otherwise.