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{info-section-underline}{2}{~}
16 \cfg{man-headnumbers}{true}
18 \cfg{contents}{Contents(edited)}
19 \cfg{index}{Index(alsoedited)}
21 This paragraph is not labelled \q{preamble}, but should still appear
24 \preamble This manual is a small joke effort, designed to use every
25 feature \#{ comment } that Halibut's input format supports. Creation
26 date \date{%Y.%m.%d} (default format is \date).
28 \c Here is a code paragraph in the preamble, just to stress that all
29 \c things are possible. Ooh!
31 \copyright Copyright 1999 Simon \#{second comment}Tatham. All rights
34 Here's another \i{preamble paragraph}, which goes after the copyright.
36 \define{metacoopt} [this is a nested,
37 multi-line macro, talking about \coopt
40 \define{coopt} co\u00F6{-o}pt
44 \C{ch\\ap} First chapter title; for similar wrapping reasons this
45 chapter title will be ludicrously long. I wonder how much more
46 chapter title I can write before feeling silly.
48 This is a para\#{another{} comment}graph of text. It
49 has line\#{yet another one} breaks in between words, multiple
50 spaces (ignored), and \e{emphasised text} as well as \c{code
53 \#{This is an inline comment alone in a paragraph.}
55 \cw{This} is weak code; \cq{this} is quoted code. And \k{head}
56 contains some other stuff. \K{subhead} does too.
58 To test the man page back end:
68 \\Sping\\Spong\\Spoing
70 \H{head} First section title (very long again, no prizes for
71 guessing the reason why this time, and here's yet more text to pad
72 it out to three lines of output)
74 \cfg{winhelp-topic}{M359HPEHGW}
76 Here's a code paragraph:
80 \c Two blank lines follow this one.
83 \c Two blank lines precede this one.
85 \c We can use \ { and } with impunity here.
86 \c We can use discretionary bold and italic in code paragraphs!
88 \c Isn't that ludicrous?
98 This bulletted list contains a list continuation. This is an
99 additional paragraph, or more than one, indented at the same level
100 as the list items, and able to contain nested sublists and other
101 features. For example, here's a code paragraph:
106 And here's a sublist. Numbered, just for variety.
123 \lcont{This is an even sillier one: a continuation of a list item in
124 a continuation of a list item in a continuation of a list item!}
136 This is a horizontal rule:
140 This is a numbered list:
146 \n Eek. \q{Aah} is point \k{keyword}.
148 This is a description list:
152 \dd A piscine creature, often to be found swimming aimlessly around
153 in the sea eating things and not contributing to the global economy.
157 Here's another of those funky list continuation things, just to keep
164 \dd A non-piscine creature, often to be found snuffling around on
165 land, not contributing to the global economy, and not even swimming
166 to make up for it. I don't know. These mammals. Pa-thetic.
168 \dt "SAUSAGE SALESMAN"
170 \dd An exemplary contributor to the global economy. Unless he's CMOT
173 This is a much more interesting description list, testing
174 consecutive \c{\\dt}s and consecutive \c{\\dd}s:
192 A-paragraph-full-of-hyphens-to-test-the-idea-that-word-wrapping-can-happen-somewhere-in-all-this-hyphenatory-nonsense.
194 A\-paragraph\-full\-of\-nonbreaking\-hyphens\-to\-test\-the\-idea\-that\-word\-wrapping\-misses\-them.
196 A\_paragraph\_full\_of\_nonbreaking\_spaces\_to\_test\_the\_idea\_that\_word\_wrapping\_misses\_them\_too.
198 Use of macros: let's talk about \coopt. And about \coopt some more.
199 And a nested macro: \metacoopt.
201 A slightly more difficult macro: \eur\.2500.
203 Test of input character set switching.
205 \n 8859 character in ASCII mode: expect nothing useful. [coöpt]
207 \cfg{input-charset}{ISO-8859-1}
209 \n 8859 character in 8859 mode: expect the right thing. [coöpt]
211 \cfg{input-charset}{UTF-8}
213 \n 8859 character in UTF-8 mode: expect the wrong thing. [coöpt]
215 \cfg{silliness}{coöpt}
217 \n UTF-8 sequence in UTF-8 mode: expect the right thing again. [coöpt]
219 \cfg{input-charset}{ASCII}
223 Oh, while I'm here: some special characters. The \\, \{ and \}
224 characters, to be precise. And their code equivalents, \c{\\},
225 \i\c{\{}, \c{\}}. The ` and ' characters (grave and apostrophe)
226 are special in some output formats.
228 Now let's exercise the paper backends a little. This is the entire
229 Adobe Standard Latin character set, which should be enough to cause
230 us to need to encode the main font twice:
232 \cfg{input-charset}{ISO-8859-1}
234 A Æ Á Â Ä À Å Ã B C Ç D E É Ê Ë È Ð F G H I Í Î Ï Ì J K L \u0141 M N Ñ O Ó Ô Ö
235 \u0152 Ò Ø Õ P Q R S \u0160 T Þ U Ú Û Ü Ù V W X Y Ý \u017d
236 a á â ´ ä æ à & å ^ ~ * @ ã b \\ | \{ \} [ ] ¦ \u2022
237 c \u02c7 ç ¸ ¢ \u02c6 : , © ¤ d \u2020 \u2021 ° ¨ ÷ $ \u02d9 \u0131
238 e é ê ë è 8 \u2026 \u2014 \u2013 = ð ! ¡ f \ufb01 5 \ufb02 \u0192 4 \u2044
239 g ß \u2039 \u203a ` > « » h - \u02dd i í î ï ì j k l \u0142 < ¬
240 m \u2212 \u00B5 × n 9 ñ # o ó ô ö \u0153 ò 1 ½ ¼ ¹ ª º ø õ
241 p \u00b6 ( ) % \u2030 . · + ±
242 q ? ¿ " \u201e \u201c \u201d \u2018 \u2019 \u201a '
243 r ® \u02da s \u0161 \u00A7 ; 7 6 / £ t þ 3 ¾ ³ \u02dc \u2122 2 ²
244 u ú û ü ù _ v w x y ý ÿ ¥ z \u017e 0
246 \cfg{input-charset}{ASCII}
248 Testing ligatures in normal (fi), empasised (\e{fi}), code (\c{fi}) and
249 weak code (\cw{fi}). The latter two should not be ligated.
251 \c Also in a code paragraph (fi) with bold (fi) and italic (fi).
253 \c There should be no ligation there.
255 The following pair of characters map to different glyphs with the same name in
256 some Microsoft TrueType fonts: \u0394{(missing)} \u2206{(missing)}
258 \S{subhead} First subheading
260 So here's a \I{subheading}\I{subsection}subsection. Just
261 incidentally, \q{this} is in quotes. \ii{Those} quotes had better work
264 We'll try for some Unicode here: \i{Schr\u00F6{oe}dinger}.
266 An index tag containing non-alternatived Unicode: \i{\u00BFChe?}
268 An invisible index tag: \I{she seems to have an invisible tag}yeah.
270 An index tag inside another tag: jackdaws love my \e{big \i{sphinx}}
273 Similarly, we should support things like hyperlinks
274 \e{\W{http://www.tartarus.org/}{at the beginning} of emphasised sections},
275 and \e{in the \W{http://www.tartarus.org/}{middle} of them}, and also
276 \e{at the \W{http://home.att.net/~cecw/lastpage.htm}{end}}.
278 \#{FIXME: Unfortunately, we still don't quite do the right thing with
280 How about a \e{reference to \k{subhead} here}? And at
281 \e{the end: \k{subhead}} and \e{\k{subhead}: the start}?
284 \S2{sub-sub}{Florble} Smaller heading still
286 A tiny section. Awww. How cute. Actually, this one's a \e{florble},
287 and here's a reference to it: \k{sub-sub}.
289 \A{app} Needless appendix
291 \# \cfg{winhelp-topic}{Y5VQEXZQVJ} (uncomment this and it clashes)
293 Here's an \i{appendix}, for no terribly good reason at all. See
294 __\k{book}__ (please excuse those underscores, I'm testing
297 It also contains a \W{http://www.tartarus.org/}{hyperlink}.
299 Also I'm going to index \i\c{-output} to ensure that its two
300 components are displayed as a joined-up code fragment in the index.
302 Here are \I{testone}some \I{testtwo}subsections \I{testthree}with
303 silly chapter titles and interesting use of Unicode. The Unicode
304 oddities are in the titles rather than the body text because that
305 way I get to test their handling in the PDF document outline.
307 \H{app-one} The 1024 \u00D7{x} 768 screen resolution
311 \H{app-two} How about Spongletech\u2122{(TM)}?
315 \# I'm going to label one of these with a carefully chosen fragment
316 \# name "i1", because I know this will also be generated as an index
317 \# fragment name and this allows me to test the fragment name clash
320 \# To actually run this test you need to configure html-leaf-level
321 \# to 0 and html-template-fragment to %k.
323 \H{i1} Or just Erd\u0151{\u00F6{o}}s?
327 \H{app-\\two} Section with inconvenient keyword
329 If you apply this file together with \cw{doc/chm.but}, this section
330 should test \cw{html_sanitise_filename()}.
334 \B{book} Some text describing a book.
336 \B{nocite} Some text describing a book. This text should appear in
337 the document even though there is no \cw{\\k} citing it.
339 \BR{book} [SillyCitation]
344 \B{uncited} If this text appears, there's an actual error.
346 \# This is a comment.
348 \# Now for the index section.
350 \IM{she seems to have an invisible tag}{appendix} Invisible tags
353 \# The display forms of these three index terms differ only in case.
354 \# This is a fiddly special case in the Windows Help backend,
355 \# because Windows Help's index mechanism is case-insensitive...