Re: [docbook] What is the use of allowing variablelists within variablelists?

[Bob Stayton <bobs@sagehill.net>]

Hi,
There is a good reason.  All of the lists allow, before the first list 
item, the inclusion of introductory content that could be used to 
explain the list.  That introductory content can be of any block-level 
content.

The RNC model looks like this:

element variablelist {
  db.variablelist.attlist,
  db.variablelist.info,
  db.all.blocks*,
  db.varlistentry+
}

and db.all.blocks contains variablelist and many other block elements.


So although such an intro is typically just a para, it could also be any 
mix of blocks that includes variablelist.  In output, any intro content 
precedes the list, so such a nested list would appear as preceding the 
main list, not nested in it.

Bob Stayton
Sagehill Enterprises
bobs@sagehill.net

On 11/19/2015 3:32 AM, Stefan Knorr wrote:
> Hi all,
>
> Tom (CCd) and I were wondering about a quirk (?) in the DocBook 5 schema:
> What is the rationale for allowing the following construct?
>
>   <variablelist>
>     <variablelist>
>   [...]
>
> (The same works for other kinds of lists within variablelist.)
>
> Regards,
>
> Stefan.
>
>
> ---                                                                    .
> SUSE Linux GmbH, Geschäftsführer: Felix Imendörffer, Jane Smithard,
> Graham Norton. HRB 21284 (AG Nürnberg)
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docbook-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: docbook-help@lists.oasis-open.org