1 \define{eur} \u20AC{EUR }
3 \title Halibut: A Test Document With A Stupidly Long Title (worth \eur\.1000)
4 Just To See If Wrapping Titles Works OK. In Fact This Title Will Span Three
5 Lines, Not Just Two. How's That For Ludicrous? More than that, though,
6 we'd like to make it more than 255 characters long so that the PostScript
7 backend has to treat it specially in order to pass it to pdfmark.
9 \cfg{xhtml-leaf-smallest-contents}{2}
10 \cfg{xhtml-leaf-contains-contents}
12 \cfg{info-dir-entry}{Sillinesses}{test.but}{Halibut test document}
13 \cfg{info-dir-entry}{Florbles}{test.but}{Subsection of Halibut test
15 \cfg{man-headnumbers}{true}
17 \cfg{contents}{Contents(edited)}
18 \cfg{index}{Index(alsoedited)}
20 This paragraph is not labelled \q{preamble}, but should still appear
23 \preamble This manual is a small joke effort, designed to use every
24 feature \#{ comment } that Halibut's input format supports. Creation
25 date \date{%Y.%m.%d} (default format is \date).
27 \c Here is a code paragraph in the preamble, just to stress that all
28 \c things are possible. Ooh!
30 \copyright Copyright 1999 Simon \#{second comment}Tatham. All rights
33 Here's another \i{preamble paragraph}, which goes after the copyright.
35 \define{metacoopt} [this is a nested,
36 multi-line macro, talking about \coopt
39 \define{coopt} co\u00F6{-o}pt
43 \C{ch\\ap} First chapter title; for similar wrapping reasons this
44 chapter title will be ludicrously long. I wonder how much more
45 chapter title I can write before feeling silly.
47 This is a para\#{another{} comment}graph of text. It
48 has line\#{yet another one} breaks in between words, multiple
49 spaces (ignored), and \e{emphasised text} as well as \c{code
52 \#{This is an inline comment alone in a paragraph.}
54 \cw{This} is weak code; \cq{this} is quoted code. And \k{head}
55 contains some other stuff. \K{subhead} does too.
57 To test the man page back end:
67 \\Sping\\Spong\\Spoing
69 \H{head} First section title (very long again, no prizes for
70 guessing the reason why this time, and here's yet more text to pad
71 it out to three lines of output)
73 \cfg{winhelp-topic}{M359HPEHGW}
75 Here's a code paragraph:
79 \c Two blank lines follow this one.
82 \c Two blank lines precede this one.
84 \c We can use \ { and } with impunity here.
85 \c We can use discretionary bold and italic in code paragraphs!
87 \c Isn't that ludicrous?
97 This bulletted list contains a list continuation. This is an
98 additional paragraph, or more than one, indented at the same level
99 as the list items, and able to contain nested sublists and other
100 features. For example, here's a code paragraph:
105 And here's a sublist. Numbered, just for variety.
122 \lcont{This is an even sillier one: a continuation of a list item in
123 a continuation of a list item in a continuation of a list item!}
135 This is a horizontal rule:
139 This is a numbered list:
145 \n Eek. \q{Aah} is point \k{keyword}.
147 This is a description list:
151 \dd A piscine creature, often to be found swimming aimlessly around
152 in the sea eating things and not contributing to the global economy.
156 Here's another of those funky list continuation things, just to keep
163 \dd A non-piscine creature, often to be found snuffling around on
164 land, not contributing to the global economy, and not even swimming
165 to make up for it. I don't know. These mammals. Pa-thetic.
167 \dt "SAUSAGE SALESMAN"
169 \dd An exemplary contributor to the global economy. Unless he's CMOT
172 This is a much more interesting description list, testing
173 consecutive \c{\\dt}s and consecutive \c{\\dd}s:
191 A-paragraph-full-of-hyphens-to-test-the-idea-that-word-wrapping-can-happen-somewhere-in-all-this-hyphenatory-nonsense.
193 A\-paragraph\-full\-of\-nonbreaking\-hyphens\-to\-test\-the\-idea\-that\-word\-wrapping\-misses\-them.
195 A\_paragraph\_full\_of\_nonbreaking\_spaces\_to\_test\_the\_idea\_that\_word\_wrapping\_misses\_them\_too.
197 Use of macros: let's talk about \coopt. And about \coopt some more.
198 And a nested macro: \metacoopt.
200 A slightly more difficult macro: \eur\.2500.
202 Test of input character set switching.
204 \n 8859 character in ASCII mode: expect nothing useful. [coöpt]
206 \cfg{input-charset}{ISO-8859-1}
208 \n 8859 character in 8859 mode: expect the right thing. [coöpt]
210 \cfg{input-charset}{UTF-8}
212 \n 8859 character in UTF-8 mode: expect the wrong thing. [coöpt]
214 \cfg{silliness}{coöpt}
216 \n UTF-8 sequence in UTF-8 mode: expect the right thing again. [coöpt]
218 \cfg{input-charset}{ASCII}
222 Oh, while I'm here: some special characters. The \\, \{ and \}
223 characters, to be precise. And their code equivalents, \c{\\},
224 \i\c{\{}, \c{\}}. The ` and ' characters (grave and apostrophe)
225 are special in some output formats.
227 \S{subhead} First subheading
229 So here's a \I{subheading}\I{subsection}subsection. Just
230 incidentally, \q{this} is in quotes. \ii{Those} quotes had better work
233 We'll try for some Unicode here: \i{Schr\u00F6{oe}dinger}.
235 An index tag containing non-alternatived Unicode: \i{\u00BFChe?}
237 An invisible index tag: \I{she seems to have an invisible tag}yeah.
239 \S2{sub-sub}{Florble} Smaller heading still
241 A tiny section. Awww. How cute. Actually, this one's a \e{florble},
242 and here's a reference to it: \k{sub-sub}.
244 \A{app} Needless appendix
246 \# \cfg{winhelp-topic}{Y5VQEXZQVJ} (uncomment this and it clashes)
248 Here's an \i{appendix}, for no terribly good reason at all. See
249 __\k{book}__ (please excuse those underscores, I'm testing
252 It also contains a \W{http://www.tartarus.org/}{hyperlink}.
254 Also I'm going to index \i\c{-output} to ensure that its two
255 components are displayed as a joined-up code fragment in the index.
257 Here are \I{testone}some \I{testtwo}subsections \I{testthree}with
258 silly chapter titles and interesting use of Unicode. The Unicode
259 oddities are in the titles rather than the body text because that
260 way I get to test their handling in the PDF document outline.
262 \H{app-one} The 1024 \u00D7{x} 768 screen resolution
266 \H{app-two} How about Spongletech\u2122{(TM)}?
270 \# I'm going to label one of these with a carefully chosen fragment
271 \# name "i1", because I know this will also be generated as an index
272 \# fragment name and this allows me to test the fragment name clash
275 \# To actually run this test you need to configure html-leaf-level
276 \# to 0 and html-template-fragment to %k.
278 \H{i1} Or just Erd\u0151{\u00F6{o}}s?
282 \H{app-\\two} Section with inconvenient keyword
284 If you apply this file together with \cw{doc/chm.but}, this section
285 should test \cw{html_sanitise_filename()}.
289 \B{book} Some text describing a book.
291 \B{nocite} Some text describing a book. This text should appear in
292 the document even though there is no \cw{\\k} citing it.
294 \BR{book} [SillyCitation]
299 \B{uncited} If this text appears, there's an actual error.
301 \# This is a comment.
303 \# Now for the index section.
305 \IM{she seems to have an invisible tag}{appendix} Invisible tags
308 \# The display forms of these three index terms differ only in case.
309 \# This is a fiddly special case in the Windows Help backend,
310 \# because Windows Help's index mechanism is case-insensitive...