1 \title Halibut: A Test Document With A Stupidly Long Title Just To
2 See If Wrapping Titles Works OK. In Fact This Title Will Span Three
3 Lines, Not Just Two. How's That For Ludicrous?
5 \cfg{xhtml-leaf-smallest-contents}{2}
6 \cfg{xhtml-leaf-contains-contents}{true}
7 \cfg{info-dir-entry}{Sillinesses}{test.but}{Halibut test document}
8 \cfg{info-dir-entry}{Florbles}{test.but}{Subsection of Halibut test
10 \cfg{man-headnumbers}{true}
12 \cfg{contents}{Contents(edited)}
13 \cfg{index}{Index(alsoedited)}
15 This paragraph is not labelled \q{preamble}, but should still appear
18 \preamble This manual is a small joke effort, designed to use every
19 feature \#{ comment } that Halibut's input format supports. Creation
20 date \date{%Y.%m.%d} (default format is \date).
22 \c Here is a code paragraph in the preamble, just to stress that all
23 \c things are possible. Ooh!
25 \copyright Copyright 1999 Simon \#{second comment}Tatham. All rights
28 Here's another \i{preamble paragraph}, which goes after the copyright.
30 \define{metacoopt} [this is a nested,
31 multi-line macro, talking about \coopt
34 \define{coopt} co\u00F6{-o}pt
36 \define{eur} \u20AC{EUR }
40 \C{ch\\ap} First chapter title; for similar wrapping reasons this
41 chapter title will be ludicrously long. I wonder how much more
42 chapter title I can write before feeling silly.
44 This is a para\#{another{} comment}graph of text. It
45 has line\#{yet another one} breaks in between words, multiple
46 spaces (ignored), and \e{emphasised text} as well as \c{code
49 \#{This is an inline comment alone in a paragraph.}
51 \cw{This} is weak code; \cq{this} is quoted code. And \k{head}
52 contains some other stuff. \K{subhead} does too.
54 To test the man page back end:
64 \\Sping\\Spong\\Spoing
66 \H{head} First section title (very long again, no prizes for
67 guessing the reason why this time, and here's yet more text to pad
68 it out to three lines of output)
70 \cfg{winhelp-topic}{M359HPEHGW}
72 Here's a code paragraph:
76 \c Two blank lines follow this one.
79 \c Two blank lines precede this one.
81 \c We can use \ { and } with impunity here.
82 \c We can use discretionary bold and italic in code paragraphs!
84 \c Isn't that ludicrous?
94 This bulletted list contains a list continuation. This is an
95 additional paragraph, or more than one, indented at the same level
96 as the list items, and able to contain nested sublists and other
97 features. For example, here's a code paragraph:
102 And here's a sublist. Numbered, just for variety.
119 \lcont{This is an even sillier one: a continuation of a list item in
120 a continuation of a list item in a continuation of a list item!}
132 This is a horizontal rule:
136 This is a numbered list:
142 \n Eek. \q{Aah} is point \k{keyword}.
144 This is a description list:
148 \dd A piscine creature, often to be found swimming aimlessly around
149 in the sea eating things and not contributing to the global economy.
153 Here's another of those funky list continuation things, just to keep
160 \dd A non-piscine creature, often to be found snuffling around on
161 land, not contributing to the global economy, and not even swimming
162 to make up for it. I don't know. These mammals. Pa-thetic.
164 \dt "SAUSAGE SALESMAN"
166 \dd An exemplary contributor to the global economy. Unless he's CMOT
169 This is a much more interesting description list, testing
170 consecutive \c{\\dt}s and consecutive \c{\\dd}s:
188 A-paragraph-full-of-hyphens-to-test-the-idea-that-word-wrapping-can-happen-somewhere-in-all-this-hyphenatory-nonsense.
190 A\-paragraph\-full\-of\-nonbreaking\-hyphens\-to\-test\-the\-idea\-that\-word\-wrapping\-misses\-them.
192 A\_paragraph\_full\_of\_nonbreaking\_spaces\_to\_test\_the\_idea\_that\_word\_wrapping\_misses\_them\_too.
194 Use of macros: let's talk about \coopt. And about \coopt some more.
195 And a nested macro: \metacoopt.
197 A slightly more difficult macro: \eur\.2500.
199 Test of input character set switching.
201 \n 8859 character in ASCII mode: expect nothing useful. [coöpt]
203 \cfg{input-charset}{ISO-8859-1}
205 \n 8859 character in 8859 mode: expect the right thing. [coöpt]
207 \cfg{input-charset}{UTF-8}
209 \n 8859 character in UTF-8 mode: expect the wrong thing. [coöpt]
211 \cfg{silliness}{coöpt}
213 \n UTF-8 sequence in UTF-8 mode: expect the right thing again. [coöpt]
215 \cfg{input-charset}{ASCII}
219 Oh, while I'm here: some special characters. The \\, \{ and \}
220 characters, to be precise. And their code equivalents, \c{\\},
221 \i\c{\{}, \c{\}}. The ` and ' characters (grave and apostrophe)
222 are special in some output formats.
224 \S{subhead} First subheading
226 So here's a \I{subheading}\I{subsection}subsection. Just
227 incidentally, \q{this} is in quotes. \ii{Those} quotes had better work
230 We'll try for some Unicode here: \i{Schr\u00F6{oe}dinger}.
232 An index tag containing non-alternatived Unicode: \i{\u00BFChe?}
234 An invisible index tag: \I{she seems to have an invisible tag}yeah.
236 \S2{sub-sub}{Florble} Smaller heading still
238 A tiny section. Awww. How cute. Actually, this one's a \e{florble},
239 and here's a reference to it: \k{sub-sub}.
241 \A{app} Needless appendix
243 \# \cfg{winhelp-topic}{Y5VQEXZQVJ} (uncomment this and it clashes)
245 Here's an \i{appendix}, for no terribly good reason at all. See
246 __\k{book}__ (please excuse those underscores, I'm testing
249 It also contains a \W{http://www.tartarus.org/}{hyperlink}.
251 Also I'm going to index \i\c{-output} to ensure that its two
252 components are displayed as a joined-up code fragment in the index.
254 Here are \I{testone}some \I{testtwo}subsections \I{testthree}with
255 silly chapter titles and interesting use of Unicode. The Unicode
256 oddities are in the titles rather than the body text because that
257 way I get to test their handling in the PDF document outline.
259 \H{app-one} The 1024 \u00D7{x} 768 screen resolution
263 \H{app-two} How about Spongletech\u2122{(TM)}?
267 \# I'm going to label one of these with a carefully chosen fragment
268 \# name "i1", because I know this will also be generated as an index
269 \# fragment name and this allows me to test the fragment name clash
272 \# To actually run this test you need to configure html-leaf-level
273 \# to 0 and html-template-fragment to %k.
275 \H{i1} Or just Erd\u0151{\u00F6{o}}s?
281 \B{book} Some text describing a book.
283 \B{nocite} Some text describing a book. This text should appear in
284 the document even though there is no \cw{\\k} citing it.
286 \BR{book} [SillyCitation]
291 \B{uncited} If this text appears, there's an actual error.
293 \# This is a comment.
295 \# Now for the index section.
297 \IM{she seems to have an invisible tag}{appendix} Invisible tags
300 \# The display forms of these three index terms differ only in case.
301 \# This is a fiddly special case in the Windows Help backend,
302 \# because Windows Help's index mechanism is case-insensitive...