X-Git-Url: https://git.distorted.org.uk/~mdw/sgt/halibut/blobdiff_plain/7136a6c7f094fa423c48ec319748c4fd7e1fa645..8a5af2bee151af73cd7806ec281536b693b48475:/inputs/test.but

diff --git a/inputs/test.but b/inputs/test.but
index 059567e..2e37c19 100644
--- a/inputs/test.but
+++ b/inputs/test.but
@@ -3,23 +3,36 @@ See If Wrapping Titles Works OK. In Fact This Title Will Span Three
 Lines, Not Just Two. How's That For Ludicrous?
 
 \cfg{xhtml-leaf-smallest-contents}{2}
-
 \cfg{xhtml-leaf-contains-contents}{true}
+\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{man-headnumbers}{true}
+
+This paragraph is not labelled \q{preamble}, but should still appear
+as it.
 
 \preamble This manual is a small joke effort, designed to use every
 feature \#{ comment } that Halibut's input format supports. Creation
 date \date{%Y.%m.%d} (default format is \date).
 
+\c Here is a code paragraph in the preamble, just to stress that all
+\c things are possible. Ooh!
+
 \copyright Copyright 1999 Simon \#{second comment}Tatham. All rights
 reserved.
 
+Here's another \i{preamble paragraph}, which goes after the copyright.
+
 \define{metacoopt} [this is a nested,
 multi-line macro, talking about \coopt
 a bit]
 
 \define{coopt} co\u00F6{-o}pt
 
-\versionid $Id: test.but,v 1.20 2004/03/23 20:10:23 simon Exp $
+\define{eur} \u20AC{EUR }
+
+\versionid $Id$
 
 \C{ch\\ap} First chapter title; for similar wrapping reasons this
 chapter title will be ludicrously long. I wonder how much more
@@ -30,8 +43,10 @@ has line\#{yet another one} breaks in   between words, multiple
   spaces (ignored), and \e{emphasised text} as well as \c{code
 fragments}.
 
-\cw{This} is weak code. And \k{head} contains some other stuff.
-\K{subhead} does too.
+\#{This is an inline comment alone in a paragraph.}
+
+\cw{This} is weak code; \cq{this} is quoted code. And \k{head}
+contains some other stuff. \K{subhead} does too.
 
 To test the man page back end:
 
@@ -39,6 +54,10 @@ To test the man page back end:
 
 'Directive
 
+\cw{.Directive}
+
+\cw{'Directive}
+
 \\Sping\\Spong\\Spoing
 
 \H{head} First section title (very long again, no prizes for
@@ -57,6 +76,9 @@ Here's a code paragraph:
 \c Two blank lines precede this one.
 \c   Two leading spaces
 \c We can use \ { and } with impunity here.
+\c We can use discretionary bold and italic in code paragraphs!
+\e                          bbbb     iiiiii
+\c Isn't that ludicrous?
 
 This is a list:
 
@@ -84,6 +106,11 @@ And here's a sublist. Numbered, just for variety.
 
 \n 1b.
 
+\lcont{
+\c Code
+\c Paragraph
+}
+
 \n 1c.
 
 \lcont{This is an even sillier one: a continuation of a list item in
@@ -136,6 +163,25 @@ to make up for it. I don't know. These mammals. Pa-thetic.
 \dd An exemplary contributor to the global economy. Unless he's CMOT
 Dibbler.
 
+This is a much more interesting description list, testing
+consecutive \c{\\dt}s and consecutive \c{\\dd}s:
+
+\dt One
+
+\dt Two
+
+\dt Three
+
+\dd Ay
+
+\dt Four
+
+\dd Bee
+
+\dd Cee
+
+\dd Dee
+
 A-paragraph-full-of-hyphens-to-test-the-idea-that-word-wrapping-can-happen-somewhere-in-all-this-hyphenatory-nonsense.
 
 A\-paragraph\-full\-of\-nonbreaking\-hyphens\-to\-test\-the\-idea\-that\-word\-wrapping\-misses\-them.
@@ -145,9 +191,32 @@ A\_paragraph\_full\_of\_nonbreaking\_spaces\_to\_test\_the\_idea\_that\_word\_wr
 Use of macros: let's talk about \coopt. And about \coopt some more.
 And a nested macro: \metacoopt.
 
+A slightly more difficult macro: \eur\.2500.
+
+Test of input character set switching.
+
+\n 8859 character in ASCII mode: expect nothing useful. [coöpt]
+
+\cfg{input-charset}{ISO-8859-1}
+
+\n 8859 character in 8859 mode: expect the right thing. [coöpt]
+
+\cfg{input-charset}{UTF-8}
+
+\n 8859 character in UTF-8 mode: expect the wrong thing. [coöpt]
+
+\cfg{silliness}{coöpt}
+
+\n UTF-8 sequence in UTF-8 mode: expect the right thing again. [coöpt]
+
+\cfg{input-charset}{ASCII}
+
+Back to ASCII again.
+
 Oh, while I'm here: some special characters. The \\, \{ and \}
 characters, to be precise. And their code equivalents, \c{\\},
-\i\c{\{}, \c{\}}.
+\i\c{\{}, \c{\}}.  The ` and ' characters (grave and apostrophe)
+are special in some output formats.
 
 \S{subhead} First subheading
 
@@ -176,6 +245,34 @@ whitespace).
 
 It also contains a \W{http://www.tartarus.org/}{hyperlink}.
 
+Also I'm going to index \i\c{-output} to ensure that its two
+components are displayed as a joined-up code fragment in the index.
+
+Here are \I{testone}some \I{testtwo}subsections \I{testthree}with
+silly chapter titles and interesting use of Unicode. The Unicode
+oddities are in the titles rather than the body text because that
+way I get to test their handling in the PDF document outline.
+
+\H{app-one} The 1024 \u00D7{x} 768 screen resolution
+
+Err.
+
+\H{app-two} How about Spongletech\u2122{(TM)}?
+
+Umm.
+
+\# I'm going to label one of these with a carefully chosen fragment
+\# name "i1", because I know this will also be generated as an index
+\# fragment name and this allows me to test the fragment name clash
+\# detection.
+\#
+\# To actually run this test you need to configure html-leaf-level
+\# to 0 and html-template-fragment to %k.
+
+\H{i1} Or just Erd\u0151{\u00F6{o}}s?
+
+Ahh.
+
 \U Bibliography
 
 \B{book} Some text describing a book.
@@ -196,3 +293,11 @@ the document even though there is no \cw{\\k} citing it.
 
 \IM{she seems to have an invisible tag}{appendix} Invisible tags
 and/or appendices
+
+\# The display forms of these three index terms differ only in case.
+\# This is a fiddly special case in the Windows Help backend,
+\# because Windows Help's index mechanism is case-insensitive...
+
+\IM{testone} Test
+\IM{testtwo} TesT
+\IM{testthree} test