Re: [docbook-apps] XSL FO parameter admonition.properties (and more!)

["Scott Parnell" <scott at knowmeta dot com>]

Sorry if this come too late to help. I haven't checked the list in a while.

If I understand your question correctly, you are interested in the DocBook
stylesheet parameters, rather than the FO properties (or maybe it's both).
I've been fooling around with a similar stylesheet customization application
off and on. You may find the techniques I used work for you. Both process
the existing DocBook XSL files at start up to avoid hardwiring anything that
might change.

One option is to use SAX to process all of the .xml files located in params
directory and construct a parameter set from what you find. This has the
advantage of allowing you to grab <refpurpose> and/or  <refsect1> content to
use as a tooltip in the UI. The problem (which you seem to have found), is
that you won't necessarily get all of the parameters that are actually
present in the stylesheets. It does provide a useful base set of parameters
that can be used as a drag source when constructing a customization
stylesheet.

The other option is to use an XSL processor (I've used Xalan), then walk the
resulting Stylesheet object to get the parameters and their values. This
method hands you every parameter defined in the root stylesheet, plus those
from any included/imported stylesheets. Constructing the parameter set this
way has the advantage of only showing those parameters that are actually
present (and presumably used by a template).

In my case, the parameters and their values are displayed in a table widget
so that they can be easily sorted and edited.  I plunk the individual
stylesheets in a tree widget to show the nesting. Selecting a stylesheet
node filters the table to show only the parameters from that particular
stylesheet.

As far as constraining the 'allowed' values, I think you're going to have to
rely on the documentation. Since it mostly consists of passing strings into
the stylesheets, just about anything is allowed, but only some values will
make sense. It depends on what the template is trying to do with the value
it receives. HTH.

Regards,
Scott

----- Original Message ----- 
From: "Steve Whitlatch" <swhitlat@getnet.net>
Sent: Monday, April 12, 2004 9:13 PM

> My current little tiny problem is that ~/fo/param.xml does not explicitly
> state all the attributes that are part of the admonition.properties
> attribute-set. I expect that I may come across other attribute-sets for
which
> there is no explicit, all-inclusive listing of the legal attributes. In
those
> cases where an attribute-set is unlimited, infinite, or undefined, I think
> I'll just provide choices for some of the most likely options. But for
those
> attribute-sets that are limited (according to whatever the current state
of
> DocBook XSL), I want to include all options.


To unsubscribe from this list, send a post to docbook-apps-unsubscribe@lists.oasis-open.org, or visit http://www.oasis-open.org/mlmanage/.