Since you're happy with simplesects, which look like sections except
they don't chunk, I'm guessing that the main thing you want is that each
use case not be on a separate chunk. So if there existed a processing
instruction, <?dbhtml stop-chunking?>, that caused the xsls to stop
chunking from that point on, you could do this:
<section>
<?dbhtml stop-chunking?>
<title>Use cases</title>
<section><title>Use Case 1: Blah</title>
<informaltable>...</informaltable>
</section>
....
<section><title>Create Zone</title>
<section><title>Use Case 5.1: Create Small Zone</title>
...
</section>
<section><title>Use Case 5.2: Create Big Zone</title>
...
</section>
</section>
<section><title>Use Case 6: Another simple one</title>
<informaltable>...</informaltable>
</section>
...
</section>
This would be better because simplesects not chunking might actually be
a bug and could be fixed later. I've wanted this very feature and have
looked into implementing it. It's doable (only tricky because of the
next and previous links). I do plan to work on it again, but I'm not
sure when I'll have time. I went ahead an opened a feature request with
the notes I made in case someone else wants to do it:
http://sourceforge.net/tracker/index.php?func=detail&aid=1842739&group_i
d=21935&atid=373750
In the mean time, this is a little ugly, but might give you something
that works for now:
<section><title>Use cases</title>
<simplesect><title>Use Case 1: Blah</title>
<informaltable>...</informaltable>
</simplesect>
....
<simplesect><title>Create Zone</title>
<example><title>Use Case 5.1: Create Small Zone</title>
...
</example>
<example><title>Use Case 5.2: Create Big Zone</title>
...
</example>
</simplesect>
<simplesect><title>Use Case 6: Another simple one</title>
<informaltable>...</informaltable>
</simplesect>
...
</section>
David
> -----Original Message-----
> From: Jean Jordaan [mailto:[EMAIL PROTECTED]
> Sent: Saturday, December 01, 2007 11:56 PM
> To: David Cramer
> Cc: [email protected]
> 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///\\
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
