[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [docbook] Re: [docbook-apps] A sequence of tables ..
Hi David > Ah, then maybe this: Slightly edited: > <section><title>Use cases</title> > <simplesect><title>Use Case 1: Blah</title> > <informaltable>...</informaltable> > </simplesect> > <simplesect><title>Use Case 2: Wooga</title> > <para>...</para> > <para>...</para> > <table>...</table> > </simplesect> > .... > <simplesect><title>Use Case 5: Create Zone</title> > <informaltable>...</informaltable> > </simplesect> > </section> Hmm, that's pretty close. Thanks. Now I have another issue. Some use cases are grouped; i.e. 5.1, 5.2, so I want something like this:: <section><title>Use cases</title> <simplesect><title>Use Case 1: Blah</title> <informaltable>...</informaltable> </simplesect> .... <section><title>Create Zone</title> <simplesect><title>Use Case 5.1: Create Small Zone</title> ... </simplesect> <simplesect><title>Use Case 5.2: Create Big Zone</title> ... </simplesect> </section> <simplesect><title>Use Case 6: Another simple one</title> <informaltable>...</informaltable> </simplesect> ... </section> This breaks, because you can have section,section,section or simplesect,simplesect,simplesect but not simplesect,section,simplesect Is there a reason why simplesect,section,simplesect shouldn't be allowed? -- jean . .. .... //\\\oo///\\
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]