Re: [docbook-apps] Simpler XHTML output

["Bob Stayton" <bobs at sagehill dot net>]

Let me first clarify that I think a clean XHTML would have to be an
additional output mode for the DocBook stylesheets.  I don't propose that it
be the default XHTML output, because not everyone wants to be dependent on
CSS, nor do they want their output to radically change with a new release.
I'm not sure yet if it would be a parameter setting, or a new stylesheet
directory.

I think a specification could have three parts.  The first part would
outline the guiding principles for clean XHTML output that is dependent on
CSS for its styling.  For example, use CSS layout features instead of layout
tables, and follow the published accessibility guidelines, and such.  The
second part would provide detailed descriptions of how specific elements
would be handled.  It would not have to cover *all* elements, as long as the
principles from the first part can be followed to handle elements that are
not yet covered.  And the third part would provide the skeleton of a CSS
file to support the first parts, so that the default output is useful.

I think the statement of principles part could be usefully discussed on this
list, because there are a lot of knowledgeable and experienced people that
could contribute.  The other two parts could be developed offline, as long
as they are publicly accessible for those who are interested in contributing
to this project.

If this seems like a reasonable approach, then someone could post a draft of
the first part to get the project moving.

Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs@sagehill.net


----- Original Message ----- 
From: "Rene Hache" <rene.hache@gmail.com>
To: "Bob Stayton" <bobs@sagehill.net>
Cc: <docbook-apps@lists.oasis-open.org>
Sent: Friday, April 22, 2005 8:15 AM
Subject: Re: [docbook-apps] Simpler XHTML output


Bob,

I would love to take on this task of specify how the XHTML should look
like, as long as I can get a little bit of help along the way. Since I
am not a "technical user" of DocBook (for example, I would never have
a need for a calloutlist), I would also need a XML Docbook file that
has an example of all the potential outputs.

To answer Larry's questions about what I mean by simpler, I certainly
would like tables-less layout (in the header for example) as well as
the cleanest code possible. I admit, I am a bit of a web standards
purist. For example, the extra DIVs around a UL tags ARE indeed a
hindrance, since it's an extra hassle styling wise. It makes it much
more difficult if not impossible in some browsers, to have a list be
displayed inline within a paragraph. A DIV around a UL tag is not
necessary, since a UL tag is already a block element. Also, anchors
tags currently surround a heading tag, which makes the entire
paragraph act as link, when ideally it should be place at the
beginning. These are just two simple example of how the code could be
simpler and more effective.

As for creating a default CSS file, I do believe that I am up to the
task if that is what is required, as well as creating accompanying
graphics. The CSS, of course, would be well commented so that others
could work their way around the file.

Sincerely,
Rene




---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org