Escape &<> when they appear in href text.

[sgt/halibut] / inputs / test.but

diff --git a/inputs/test.but b/inputs/test.but
index af1f2fc..dddc2dd 100644 (file)
--- a/inputs/test.but
+++ b/inputs/test.but
@@ -1,16 +1,23 @@
-\title Halibut: A Test Document With A Stupidly Long Title Just To
-See If Wrapping Titles Works OK. In Fact This Title Will Span Three
-Lines, Not Just Two. How's That For Ludicrous?
+\define{eur} \u20AC{EUR }
+
+\title Halibut: A Test Document With A Stupidly Long Title (worth \eur\.1000)
+Just To See If Wrapping Titles Works OK. In Fact This Title Will Span Three
+Lines, Not Just Two. How's That For Ludicrous?  More than that, though,
+we'd like to make it more than 255 characters long so that the PostScript
+backend has to treat it specially in order to pass it to pdfmark.

 
 \cfg{xhtml-leaf-smallest-contents}{2}
 
 \cfg{xhtml-leaf-smallest-contents}{2}

-\cfg{xhtml-leaf-contains-contents}{true}
+\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{info-dir-entry}{Sillinesses}{test.but}{Halibut test document}
 \cfg{info-dir-entry}{Florbles}{test.but}{Subsection of Halibut test
 document}{sub-sub}

+\cfg{info-section-underline}{2}{~}
+\cfg{info-charset}{utf-8}

 \cfg{man-headnumbers}{true}
 
 \cfg{man-headnumbers}{true}
 

-\cfg{contents}{Contents(edited)}
-\cfg{index}{Index(alsoedited)}
+\cfg{contents}{Contents - edited title}
+\cfg{index}{Index - also edited title}

 
 This paragraph is not labelled \q{preamble}, but should still appear
 as it.
 
 This paragraph is not labelled \q{preamble}, but should still appear
 as it.


@@ -33,8 +40,6 @@ a bit]
 
 \define{coopt} co\u00F6{-o}pt
 
 
 \define{coopt} co\u00F6{-o}pt
 

-\define{eur} \u20AC{EUR }
-

 \versionid $Id$
 
 \C{ch\\ap} First chapter title; for similar wrapping reasons this
 \versionid $Id$
 
 \C{ch\\ap} First chapter title; for similar wrapping reasons this


@@ -82,6 +87,8 @@ Here's a code paragraph:
 \c We can use discretionary bold and italic in code paragraphs!
 \e                          bbbb     iiiiii
 \c Isn't that ludicrous?
 \c We can use discretionary bold and italic in code paragraphs!
 \e                          bbbb     iiiiii
 \c Isn't that ludicrous?

+\c 
+\c man page tricky characters: command -o 'quoted' -o `backticks`

 
 This is a list:
 
 
 This is a list:
 


@@ -221,6 +228,36 @@ characters, to be precise. And their code equivalents, \c{\\},
 \i\c{\{}, \c{\}}.  The ` and ' characters (grave and apostrophe)
 are special in some output formats.
 
 \i\c{\{}, \c{\}}.  The ` and ' characters (grave and apostrophe)
 are special in some output formats.
 

+Now let's exercise the paper backends a little.  This is the entire
+Adobe Standard Latin character set, which should be enough to cause
+us to need to encode the main font twice:
+
+\cfg{input-charset}{ISO-8859-1}
+
+A Æ Á Â Ä À Å Ã B C Ç D E É Ê Ë È Ð F G H I Í Î Ï Ì J K L \u0141 M N Ñ O Ó Ô Ö
+\u0152 Ò Ø Õ P Q R S \u0160 T Þ U Ú Û Ü Ù V W X Y Ý \u017d
+a á â ´ ä æ à & å ^ ~ * @ ã b \\ | \{ \} [ ] ¦ \u2022
+c \u02c7 ç ¸ ¢ \u02c6 : , © ¤ d \u2020 \u2021 ° ¨ ÷ $ \u02d9 \u0131
+e é ê ë è 8 \u2026 \u2014 \u2013 = ð ! ¡ f \ufb01 5 \ufb02 \u0192 4 \u2044
+g ß \u2039 \u203a ` > « » h - \u02dd i í î ï ì j k l \u0142 < ¬
+m \u2212 \u00B5 × n 9 ñ # o ó ô ö \u0153 ò 1 ½ ¼ ¹ ª º ø õ
+p \u00b6 ( ) % \u2030 . · + ±
+q ? ¿ " \u201e \u201c \u201d \u2018 \u2019 \u201a '
+r ® \u02da s \u0161 \u00A7 ; 7 6 / £ t þ 3 ¾ ³ \u02dc \u2122 2 ²
+u ú û ü ù _ v w x y ý ÿ ¥ z \u017e 0
+
+\cfg{input-charset}{ASCII}
+
+Testing ligatures in normal (fi), empasised (\e{fi}), code (\c{fi}) and
+weak code (\cw{fi}).  The latter two should not be ligated.
+
+\c Also in a code paragraph (fi) with bold (fi) and italic (fi).
+\e                                          bb              ii
+\c There should be no ligation there.
+
+The following pair of characters map to different glyphs with the same name in
+some Microsoft TrueType fonts: \u0394{(missing)} \u2206{(missing)}
+

 \S{subhead} First subheading
 
 So here's a \I{subheading}\I{subsection}subsection. Just
 \S{subhead} First subheading
 
 So here's a \I{subheading}\I{subsection}subsection. Just


@@ -233,6 +270,25 @@ An index tag containing non-alternatived Unicode: \i{\u00BFChe?}
 
 An invisible index tag: \I{she seems to have an invisible tag}yeah.
 
 
 An invisible index tag: \I{she seems to have an invisible tag}yeah.
 

+An index tag inside another tag: jackdaws love my \e{big \i{sphinx}}
+of quartz.
+
+Similarly, we should support things like hyperlinks
+\e{\W{http://www.tartarus.org/}{at the beginning} of emphasised sections},
+and \e{in the \W{http://www.tartarus.org/}{middle} of them}, and also
+\e{at the \W{http://home.att.net/~cecw/lastpage.htm}{end}}.
+
+Here's a hyperlink containing some special characters:
+\W{http://a<b&c>d/}{here}. (Not that it'll \e{work}, but you can at
+least determine that it's been correctly escaped by inspection of
+the output HTML.)
+
+\#{FIXME: Unfortunately, we still don't quite do the right thing with
+references:
+How about a \e{reference to \k{subhead} here}? And at
+\e{the end: \k{subhead}} and \e{\k{subhead}: the start}?
+}
+

 \S2{sub-sub}{Florble} Smaller heading still
 
 A tiny section. Awww. How cute. Actually, this one's a \e{florble},
 \S2{sub-sub}{Florble} Smaller heading still
 
 A tiny section. Awww. How cute. Actually, this one's a \e{florble},


@@ -276,6 +332,11 @@ Umm.
 
 Ahh.
 
 
 Ahh.
 

+\H{app-\\two} Section with inconvenient keyword
+
+If you apply this file together with \cw{doc/chm.but}, this section
+should test \cw{html_sanitise_filename()}.
+

 \U Bibliography
 
 \B{book} Some text describing a book.
 \U Bibliography
 
 \B{book} Some text describing a book.