OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: XSL FO parameter admonition.properties (and more!)


Hello, 

I am creating a program that builds a Java data structure (TreeMap) that 
contains String array entries for all (?) the DocBook XSL FO parameters. 
Several classes work together to produce a text file (.xsl) containing a 
DocBook XSL customization layer. I plan to eventually provide a GUI so that 
users can point and click through the XSL building process, and also apply 
the XSL to a valid instance of DocBook XML.

So far so good; however, the capability of the XSL produced is limited by what 
the TreeMap contains. I can always extend the contents of the TreeMap and 
provide XSL that is not controlled by FO parameters, but it is important that 
I include all the easy stuff that is already available, like FO parameters.  

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.    

Here is an example of what I've found. Looking at the FO Parameter Reference 
documentation (~/fo/param.xml) for  admonition.properties, I see:

******************
  Name
  admonition.properties — To set the style for admonitions.

  Synopsis
  <xsl:attribute-set name="admonition.properties"></xsl:attribute-set>

  Description
  How do you want admonitions styled?

  Set the font-size, weight, etc. to the style required
******************

and I am needing to know each and every attribute in this set. Or, given the 
constraints of the current, as-shipped DocBook XSL package (prior to 
customization), is there such a thing as "each and every"? 

For example, the FO Parameter Reference documentation for 
admonition.title.properties lists:

****************
<xsl:attribute-set name="admonition.title.properties">
  <xsl:attribute name="font-size">14pt</xsl:attribute>
  <xsl:attribute name="font-weight">bold</xsl:attribute>
  <xsl:attribute name="hyphenate">false</xsl:attribute>
  <xsl:attribute name="keep-with-next.within-column">always</xsl:attribute>
</xsl:attribute-set>
****************

and I am wanting to think that is "each and every"? Can I safely do that?

For the admonition.properties attribute set, can I just repeat the attributes 
listed for admonition.title.properties attribute set? 

In general, how am I to know what attributes an attribute-set can legally 
contain? I have not been able to figure this out exploring the DocBook XSL, 
not yet.

How do I know what are all the possible legal settings for an attribute?

Excluding the GUI implementation, most of the work before me is really just 
copy paste in creating the data structure, which simply contains a whole 
bunch of Strings that get combined and written to an XSL file. Right now, 
this looks so easy I wonder why no-one else has done it already. Am I missing 
something? Most of the work is already done in the DocBook XSL package.

Thanks to all, 

Steve Whitlatch
 




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]