While I agree that embedding the CSS in the header is not the best solution, particularly for chunked output, we are sometimes required to deliver files into existing delivery environments that require file-per-file replacement of HTML files that were originally produced using output from Microsoft Word, which embedded all the style information in the header. I agree it should not be the default behavior, but it does serve a purpose. We have also had to mail some sample pages and mailing a single file is definitely easier.
Best Regards, Larry Rowland -----Original Message----- From: Jirka Kosek [mailto:[email protected]] Sent: Monday, November 30, 2009 6:38 AM To: Chris Maloney Cc: Bob Stayton; DocBook Apps Subject: Re: [docbook-apps] improve DocBook's HTML output Chris Maloney wrote: > 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. Why do you think that this has advantage over separate CSS file, especially for chunked output? -- ------------------------------------------------------------------ Jirka Kosek e-mail: [email protected] 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 ------------------------------------------------------------------ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
