Dave,
Thanks for the suggestion; I think it makes sense to
add an example. It's probably about time for me to
look at the section again anyway and see what else it
needs.
Thanks,
Dick
> -----Original Message-----
> From: Dave Pawson [mailto:]
> Sent: Thursday, September 06, 2007 12:45 AM
> To: Dick Hamilton
> Cc: 'Jirka Kosek'; 'Docbook List'
> Subject: Re: [docbook] v5 extension elements
>
>
> Dick Hamilton wrote:
> > Dave,
> >
> >>> <define name="db.ubiq.inlines" combine="choice">
> >>> <choice>
> >>> <ref name="shLft"/>
> >>> <ref name='shRt'/>
> >>> </choice>
> >>> </define>
> >>>
> >> In an external file Jirka.. then include the main db file?
> >>
> >
> > That's the way I would suggest doing this. The DocBook 5.0
> > Howto mentions this in the section on customization:
> >
> > http://docbook.org/docs/howto/#customconsiderations
>
> Thanks Dick.
> Suggest an example would help others understand.
> Simple para explaining how the combine attribute works
> perhaps?
> <add>
> For example
>
> <define name="db.ubiq.inlines" combine="choice">
> <choice>
> <ref name="myelement1"/>
> <ref name='myelement2'/>
> </choice>
> </define>
>
>
> <define name="myelement1">
> <text/>
> </define>
>
> This replaces or merges with the definition within the main
> schema, due to the 'combine' attribute being set to 'choice'.
> These two elements are added to the main definition.
>
> Then when the schema is updated, the elements remain defined
> without further work.
>
> </add>
>
> regards
>
> --
> Dave Pawson
> XSLT XSL-FO FAQ.
> http://www.dpawson.co.uk
>
