X-Git-Url: https://git.distorted.org.uk/~mdw/sgt/halibut/blobdiff_plain/4b3c5afb39849b3d0e738248daec9ab7dd8aac6d..e0e55d4168c693e814dbeea1604acd01d330c61f:/inputs/test.but diff --git a/inputs/test.but b/inputs/test.but index cfefbdb..58d10ef 100644 --- a/inputs/test.but +++ b/inputs/test.but @@ -4,22 +4,35 @@ 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.21 2004/03/24 19:23:21 simon Exp $ +\define{eur} \u20AC{EUR } + +\versionid $Id: test.but,v 1.34 2004/07/16 11:54:04 simon Exp $ \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,8 @@ 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. +\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: @@ -87,6 +100,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 @@ -148,6 +166,28 @@ 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{\}}. @@ -179,6 +219,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. @@ -199,3 +267,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