- "Bob Stayton" wrote:
> I'd like to get clarification on what are considered excessive divs.
> Here
> is a sample of the XHTML output for the start of a chapter:
> To me, the only excessive divs are the two extra s without class
> attributes around the chapter title. The other divs with
Hi Dave,
It is not my intention that the stylesheet generates an XML file for the
CSS. Rather, an XML file containing CSS code is written and maintained by
hand in the SVN archive and included in the distribution.
The file that the param 'docbook.css.source' points to looks like this [not
re
uritz Jeanson"
Sent: Friday, December 04, 2009 7:35 AM
Subject: Re: [docbook-apps] improve DocBook's HTML output
>And perhaps someone has an opinion on the claim that the current (X)HTML
output suffers from "div-itis" (excessive use of elements). See
http://backtobase.wordpr
>And perhaps someone has an opinion on the claim that the current (X)HTML
>output suffers from "div-itis" (excessive use of elements). See
>http://backtobase.wordpress.com/2007/06/20/docbook-is-not-making-my-life-easier/.
I would like to see unnecessary divs removed. Is there a purpose for them?
On 04/12/09 07:28, Bob Stayton wrote:
Thanks to all for the helpful feedback. Based on that, here is my new
proposal for DocBook-generated CSS. I'm trying to balance flexibility
against
too much complexity. I've got it down to just four new params.
1. Add a new param 'make.clean.html', which wh
Thanks to all for the helpful feedback. Based on that, here is my new
proposal for DocBook-generated CSS. I'm trying to balance flexibility
against
too much complexity. I've got it down to just four new params.
1. Add a new param 'make.clean.html', which when set to 1 will cause the
HTML s
On Wed, Dec 2, 2009 at 1:12 PM, Mauritz Jeanson wrote:
> | -Original Message-
> | From: Bob Stayton
> |
> | I have had a long standing goal to modernize the HTML output
> | from the
> | DocBook XSL stylesheets. We have too many instances of
> | hardcoded styles like
> | and other t
| -Original Message-
| From: Bob Stayton
|
| I have had a long standing goal to modernize the HTML output
| from the
| DocBook XSL stylesheets. We have too many instances of
| hardcoded styles like
| and other transgressions of modern HTML practice.
One important point is to
2009/12/2 Tony Graham :
> On Tue, Dec 01 2009 20:19:33 +, andy.docb...@zambezi.org.uk wrote:
>> 2009/11/30 Bob Stayton :
>>> 5. You can customize the CSS input file beyond the minimal CSS styles that
>>> ship with distro. If so, then put your file with your customization layer
>>> and change
On Tue, Dec 01 2009 20:19:33 +, andy.docb...@zambezi.org.uk wrote:
> 2009/11/30 Bob Stayton :
>> 5. You can customize the CSS input file beyond the minimal CSS styles that
>> ship with distro. If so, then put your file with your customization layer
>> and change the 'docbook.css.file' paramet
2009/11/30 Bob Stayton :
> 5. You can customize the CSS input file beyond the minimal CSS styles that
> ship with distro. If so, then put your file with your customization layer
> and change the 'docbook.css.file' parameter to point to your customized
> version. You just need to keep the
I agree that the default should be a separate CSS file, not CSS in the head
element.
FYI, I was planning to implement this feature as follows.
1. Create and check in a new file 'docbook-css.xml' in the distro that
looks like:
[CSS styles go here]
This checked-in file would be updated b
-
From: Jirka Kosek [mailto:ji...@kosek.cz]
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
>
Well, it was just a suggestion. Sometimes it's useful to have a nice
looking document all in one file. Of course I'd agree that its default
value should be off.
On Mon, Nov 30, 2009 at 8:59 AM, wrote:
> Hi, guys,
>
> (Jumping in a bit - as somebody who uses DocBook regularly but has a day
> jo
Hi, guys,
(Jumping in a bit - as somebody who uses DocBook regularly but has a day
job doing bare-metal HTML/CSS coding)
As I understand the discussion thus far, what's wanted is an easy way for
new folks to generate/deploy DocBook-generated HTML that, as they progress
up the learning curve, they
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 o
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
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
Bob,
I like your ideas, especially strict [X]HTML output, but I wonder
about the danger of having one 'html.stylesheet' param that might
overwrite something we have modified manually:
At Sat, 28 Nov 2009 10:41:21 -0800, Bob Stayton wrote:
...
> I think two params could control this feature:
...
> 1. A new param named 'make.strict.html'
How about 'make.clean.html'? "strict" has a specific meaning with regard to
HTML.
> 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 pro
20 matches
Mail list logo
