Sorry Jen, just looked at your document again. In this case you should 
use bridgehead because simplesect "must be terminal".

(A description which always worried me...)

Simon Dew

Technical Author | Stanley Security Solutions
1 Park Gate Close, Bredbury, Stockport SK6 2SZ, U.K.

[email protected] | +44 (0) 161 406 3405
www.stanleysecuritysolutions.co.uk

Registered Office: Stanley House, Bramble Road, Swindon
Registered in England and Wales No. 181585 VAT No. 232 2446 95

On 28/11/2013 10:42, Dew, Simon wrote:

> Hi Jen
>
> Try bridgehead or simplesect.
>
> Simon Dew
>
> Technical Author | Stanley Security Solutions
> 1 Park Gate Close, Bredbury, Stockport SK6 2SZ, U.K.
>
> [email protected] | +44 (0) 161 406 3400
> www.stanleysecuritysolutions.co.uk
>
> Registered Office: Stanley House, Bramble Road, Swindon
> Registered in England and Wales No. 181585 VAT No. 232 2446 95
>
> On 28/11/2013 10:32, Jen wrote:
>
>> Hi,
>>
>> I'm trying to convert an existing document to DocBook and I'm struggling
>> with a structure that is not (I think!) supported in DocBook (H3 between
>> H1 and H2).
>>
>> Right now, the layout of this section is (in HTML) something like:
>>
>> <h1>Application Basics</h1>                   -> chapter name
>> <p>Description of application.</p>
>> <h3>Setting Up a Project</h3>
>> <p>Short description of project setup, plus links to relevant topics.</p>
>> <h3>Setting Up A Task</h3>
>> <p>Short description of task setup, plus links to relevant topics.</p>
>> <h2>How to Set Up a Project</h2>             -> first "true" section
>> <p>Procedure for setting up a project.</p>
>>
>> Now, I don't think this can work in DocBook, since you can't have
>> sect1>sect3>sect2... but I'd like to maintain the smaller headings in
>> the chapter introduction. Is there a tag that I can use for this? Worst
>> case scenario, I'll just have an <emphasis role="bold">, but I'd prefer
>> to use a dedicated tag so I could also change the font size and so on.
>>
>> Thanks in advance,
>> Jen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to