For me, if content were allowed after a section, it's hard to imagine
how you would render it in a way that made it clear which section it
belongs to. What you have may be a <sidebar>. Worst case you could use
<bridgehead>s to match the "structure" of the legacy content. 
 
David


________________________________

        From: Dick Hamilton [mailto:[email protected]] 
        Sent: Thursday, March 25, 2010 1:13 PM
        To: 'PC Thoms'; [email protected]
        Subject: RE: [docbook-apps] para-section-para
        
        
        According to the schema, you can have a para before the first
section, but once you start using sections, you cannot have a para
outside of some other structure (section, etc.).
         
        I believe that is intentional and has been that way for a while.
         
        Best Regards,
        Dick Hamilton
        ---------------------------------
        XML Press
        XML for Technical Communicators
        http://xmlpress.net <http://xmlpress.net/> 
        (970) 231-3624
        

                -----Original Message-----
                From: PC Thoms [mailto:[email protected]] 
                Sent: Thursday, March 25, 2010 10:40 AM
                To: [email protected]
                Subject: [docbook-apps] para-section-para
                
                
                While preparing an article in the following format I
receive a not allowed instruction. 
                Editor: Oxygen 10.3
                

                <article xmlns="http://docbook.org/ns/docbook";
                    xmlns:xlink="http://www.w3.org/1999/xlink";
version="5.0">
                  <section>
                    <para>text</para>
                    <section>
                      <para>text</para>
                    </section>
                  <para>text</para> (This paragraph shows as not
allowed. Why?)
                  </section>
                </article>

                Exports to the browser fine.
                Must I follow a <section> with a <section>, that works,
but this would break up the flow of the document, which is an old
report.
                Or is this a bug?

Reply via email to