From 674cfb5f4f4ed5a7e8df0fe330120784df889bbf Mon Sep 17 00:00:00 2001 From: Simon Tatham Date: Wed, 24 Mar 2004 19:23:21 +0000 Subject: Cleanups to complete the man page backend. Also, an additional new markup feature: a \c line in a code paragraph can now be followed by an optional \e line indicating emphasised bits of its preceding \c. This allows discretionary bolding and (italic/underline) emphasis within code paragraphs, but without introducing an escape character or breaking any existing input files. Users are warned that not all backends are required to actually render these hints, and so they should avoid depending on them 100% to convey semantic information unless they know they're writing for a restricted range of backends. [originally from svn r3965] --- inputs/test.but | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) (limited to 'inputs') diff --git a/inputs/test.but b/inputs/test.but index 059567e..cfefbdb 100644 --- a/inputs/test.but +++ b/inputs/test.but @@ -3,8 +3,8 @@ See If Wrapping Titles Works OK. In Fact This Title Will Span Three Lines, Not Just Two. How's That For Ludicrous? \cfg{xhtml-leaf-smallest-contents}{2} - \cfg{xhtml-leaf-contains-contents}{true} +\cfg{man-headnumbers}{true} \preamble This manual is a small joke effort, designed to use every feature \#{ comment } that Halibut's input format supports. Creation @@ -19,7 +19,7 @@ a bit] \define{coopt} co\u00F6{-o}pt -\versionid $Id: test.but,v 1.20 2004/03/23 20:10:23 simon Exp $ +\versionid $Id: test.but,v 1.21 2004/03/24 19:23:21 simon Exp $ \C{ch\\ap} First chapter title; for similar wrapping reasons this chapter title will be ludicrously long. I wonder how much more @@ -57,6 +57,9 @@ Here's a code paragraph: \c Two blank lines precede this one. \c Two leading spaces \c We can use \ { and } with impunity here. +\c We can use discretionary bold and italic in code paragraphs! +\e bbbb iiiiii +\c Isn't that ludicrous? This is a list: -- cgit v1.1