X-Git-Url: https://git.distorted.org.uk/~mdw/sgt/halibut/blobdiff_plain/b9e27ab606985162d9b7168c9e0b6fc2a3df4579..0dfaac7284d7f1a54e957bba4a881d93328c1630:/inputs/test.but

diff --git a/inputs/test.but b/inputs/test.but
index 72f8719..dddc2dd 100644
--- a/inputs/test.but
+++ b/inputs/test.but
@@ -12,10 +12,12 @@ backend has to treat it specially in order to pass it to pdfmark.
 \cfg{info-dir-entry}{Sillinesses}{test.but}{Halibut test document}
 \cfg{info-dir-entry}{Florbles}{test.but}{Subsection of Halibut test
 document}{sub-sub}
+\cfg{info-section-underline}{2}{~}
+\cfg{info-charset}{utf-8}
 \cfg{man-headnumbers}{true}
 
-\cfg{contents}{Contents(edited)}
-\cfg{index}{Index(alsoedited)}
+\cfg{contents}{Contents - edited title}
+\cfg{index}{Index - also edited title}
 
 This paragraph is not labelled \q{preamble}, but should still appear
 as it.
@@ -85,6 +87,8 @@ Here's a code paragraph:
 \c We can use discretionary bold and italic in code paragraphs!
 \e                          bbbb     iiiiii
 \c Isn't that ludicrous?
+\c 
+\c man page tricky characters: command -o 'quoted' -o `backticks`
 
 This is a list:
 
@@ -244,6 +248,16 @@ u 
 
 \cfg{input-charset}{ASCII}
 
+Testing ligatures in normal (fi), empasised (\e{fi}), code (\c{fi}) and
+weak code (\cw{fi}).  The latter two should not be ligated.
+
+\c Also in a code paragraph (fi) with bold (fi) and italic (fi).
+\e                                          bb              ii
+\c There should be no ligation there.
+
+The following pair of characters map to different glyphs with the same name in
+some Microsoft TrueType fonts: \u0394{(missing)} \u2206{(missing)}
+
 \S{subhead} First subheading
 
 So here's a \I{subheading}\I{subsection}subsection. Just
@@ -264,6 +278,11 @@ Similarly, we should support things like hyperlinks
 and \e{in the \W{http://www.tartarus.org/}{middle} of them}, and also
 \e{at the \W{http://home.att.net/~cecw/lastpage.htm}{end}}.
 
+Here's a hyperlink containing some special characters:
+\W{http://a<b&c>d/}{here}. (Not that it'll \e{work}, but you can at
+least determine that it's been correctly escaped by inspection of
+the output HTML.)
+
 \#{FIXME: Unfortunately, we still don't quite do the right thing with
 references:
 How about a \e{reference to \k{subhead} here}? And at