The Unicode OVERLINE in the text backend documentation was probably supposed

to be quoted.

git-svn-id: svn://svn.tartarus.org/sgt/halibut@4299 cda61777-01e9-0310-a592-d414129be87e

diff --git a/doc/output.but b/doc/output.but
index 68fc04e..5706f7d 100644 (file)
--- 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
 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.
 
 the Unicode \q{OVERLINE} character where possible and fall back to
 the ASCII minus sign otherwise.