On Thu, 5 Feb 2004, Christopher Currie wrote:
> Reece Dunn wrote:
> > As far as I can see, modifying DocBook rendering should be a matter of
> > changing the reference.css stylesheet (see my attachment). This does a
> > lot of the customization of the rendering because DocBook adds class
> > elements in the same way my stylesheet does (makes it easier to change
> > rendering).
> >
>
> Very slick! Just had to drop this into my html directory to see the changes.
>
> One problem (on my browser, at least, Firebird 0.7+) certain
> <programlisting> elements are wider than the fixed box width allocated
> to them. The last listing on bbv2.tutorial.properties.html demonstrates
> this issue.
Long lines in <programlisting> elements are a bad idea anyway, because
they'll often go off the page when we generate printed documentation (PS,
PDF, etc.) or on man pages.
> Also, although the code block looks great in normal flow, sometimes
> programlisting is used within a table, which doesn't look as clean.
> Build the Boost.Signals docs to see what I'm talking about. I'm assuming
> we either have to use some CSS selector to fix this, or make the xsl
> smarter about assigning element classes.
Or dub the Boost.Signals docs an oddity that should be fixed. I've never
been happy with the use of tables there, but I haven't been able to find a
clear way to say "write it this way, or equivalently this way". In other
words, don't spend too much time dealing with <programlisting> in tables:
it's probably a bad idea to start with.
Doug
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Boost-docs mailing list
[EMAIL PROTECTED]
Unsubscribe and other administrative requests:
https://lists.sourceforge.net/lists/listinfo/boost-docs
