Framework for DocBook titlepage customisation?
Has anybody made a framework for DocBook titlepage customisation files [1] to, e.g., make it easy to run the transform to turn a template into the XSLT suitable for inclusion in a custom XSLT setup? Regards, Tony Graham tgraham@mentea.net Consultant http://www.mentea.net Mentea 13 Kelly's Bay Beach, Skerries, Co. Dublin, Ireland -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- XML, XSL-FO and XSLT consulting, training and programming
Hi, I think it is mainly just one XSLT transform which applies [Oxygen-folder]/frameworks/docbook/xsl/template/titlepage.xsl on a titlepage XML document, followed by importing the result of this transformation (that is a new XSLT stylesheet) in a DocBook customization layer (with an xsl:import element). You can use the Oxygen editor variables for the target folder of the XSLT titlepage customization transform, for example ${pd} for the current project directory or ${frameworksDir}/docbook/xsl for the directory of the Docbook XSL stylesheets. Please can you give more details about your custom XSLT setup? We did not provide a built-in framework for Docbook titlepage customization files in Oxygen because an Oxygen framework is usually created for more complex operations on a file type, like editing the files in Author mode with one or more CSS stylesheets, applying different XSLT stylesheets for different types of output, XML catalogs necessary for validation or transformation, etc. Best regards, Sorin http://www.oxygenxml.com Tony Graham wrote:
Has anybody made a framework for DocBook titlepage customisation files [1] to, e.g., make it easy to run the transform to turn a template into the XSLT suitable for inclusion in a custom XSLT setup?
Regards,
Tony Graham tgraham@mentea.net Consultant http://www.mentea.net Mentea 13 Kelly's Bay Beach, Skerries, Co. Dublin, Ireland -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- XML, XSL-FO and XSLT consulting, training and programming
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 If there were a schema for the titlepage xml file, then adding it and a "titlepage.framework" file to the DocBook framework might make sense to provide authoring assistance. David On 01/23/2012 08:48 AM, Sorin Ristache wrote:
Hi,
I think it is mainly just one XSLT transform which applies [Oxygen-folder]/frameworks/docbook/xsl/template/titlepage.xsl on a titlepage XML document, followed by importing the result of this transformation (that is a new XSLT stylesheet) in a DocBook customization layer (with an xsl:import element). You can use the Oxygen editor variables for the target folder of the XSLT titlepage customization transform, for example ${pd} for the current project directory or ${frameworksDir}/docbook/xsl for the directory of the Docbook XSL stylesheets. Please can you give more details about your custom XSLT setup?
We did not provide a built-in framework for Docbook titlepage customization files in Oxygen because an Oxygen framework is usually created for more complex operations on a file type, like editing the files in Author mode with one or more CSS stylesheets, applying different XSLT stylesheets for different types of output, XML catalogs necessary for validation or transformation, etc.
Best regards, Sorin
Has anybody made a framework for DocBook titlepage customisation files [1] to, e.g., make it easy to run the transform to turn a template into the XSLT suitable for inclusion in a custom XSLT setup?
Regards,
Tony Graham tgraham@mentea.net Consultant http://www.mentea.net Mentea 13 Kelly's Bay Beach, Skerries, Co. Dublin, Ireland -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- XML, XSL-FO and XSLT consulting, training and programming _______________________________________________ oXygen-user mailing
Tony Graham wrote: list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPHsotAAoJEMHeSXG7afUhlRIH/3mObFlEjCrEJ4nQsuWPTS6D iBEQAgGzrKHpxQq1gHG9fW4eLmX4NUa9lkMwo1ptPxDh1di0Nl+iRvwzHmTpKTqL ER84sptMt0DeWlM0Gx5nEQXUsxQrvUWM03N0j20/MS6izVSGljQdJYDbZMXCPbrm a8vjfa/xJ6hxn1RYzzEN6wlTx/ogo+0V889A+DBDN4hnly3288wSi35DeRBQMzrh Pwbar9EwhSpEX4DJuyZNHI2FQNfMlHJerNPGXafrKTxuToin4wnpd+L6eGNY2BK/ eUB5dXcgtZc9tLXT00ffdRqNCs+EKfB1qbiYXvpHZU8M69W2zUY9SosImM1UMK4= =I5dl -----END PGP SIGNATURE-----
On Tue, January 24, 2012 3:11 pm, David Cramer wrote:
If there were a schema for the titlepage xml file, then adding it and a "titlepage.framework" file to the DocBook framework might make sense to provide authoring assistance.
The "http://nwalsh.com/docbook/xsl/template/1.0" URL resolves to docbook.sourceforge.net but gives an error page rather than any useful hints about where to find the schema.
I think it is mainly just one XSLT transform which applies [Oxygen-folder]/frameworks/docbook/xsl/template/titlepage.xsl on a titlepage XML document, followed by importing the result of this
Two, if you're customising both HTML and FO output. Customising can be a highly iterative process that, IMO, begs for as much automation as possible. I had been checking to see if someone else had it preconfigured before I potentially reinvented that wheel by configuring it for my user. Putting the xsl:import in the right file is something to do once (or twice) by hand, but regenerating the customisation is a good candidate for a transformation scenario, at least. Regards, Tony Graham tgraham@mentea.net Consultant http://www.mentea.net Mentea 13 Kelly's Bay Beach, Skerries, Co. Dublin, Ireland -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- XML, XSL-FO and XSLT consulting, training and programming
participants (3)
-
David Cramer -
Sorin Ristache -
Tony Graham