Well, if that's the goal, then I'd like to add another option for consideration: maybe called 'generate.header.css', or something, that would cause the generated css to appear in the HTML header rather than in a separate file.
2009/11/29 Jirka Kosek <>
Chris Maloney wrote:
>> 2. A new param named 'generate.css', which when set to 1
>
> Why would this be necessary? Presumably one, or possibly a set of static
> CSS files could be supplied that provide all the basic styling based on
> classes used in the generated output. Or, are you suggesting that the XSL
> generate a per-output CSS with just the subset of the "master CSS" styles?
Generating CSS file on the fly simplifies deployment -- user doesn't
have to copy CSS into target directory. This is easy, but for newcomers
it is much more handy if there are no additional steps required to
generate working output.
Jirka
--
------------------------------------------------------------------
Jirka Kosek e-mail: http://xmlguru.cz
------------------------------------------------------------------
Professional XML consulting and training services
DocBook customization, custom XSLT/XSL-FO document processing
------------------------------------------------------------------
OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member
------------------------------------------------------------------
