Vladimir Prus wrote:
Christopher Currie wrote:

> Given that this stylesheet still has issues with chunking, and doesn't
> pick up some of the lesser used Docbook markup, I'd like to propose that
> we use boostbook/xsl/html.xsl as a starting point; it's what I've been
> using to sanity check the Boost.Build user manual. There's definitely
> improvements we can make to it, but a lot of work has gone into it
> already that we should leverage.

I surely agree. It would be bad if I try to use some non-mainstream Docbook element just to find out it's not supported. So using Boost.Book is really good idea. Besides, I really liked when I saw Christopher's checkin, run bjam, and immediately got html docs.

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).


> Several people commented on the Boost.Build list that they like the look
> of the Spirit docs; do we want to copy this exact template, or simply
> evoke the spirit (no pun intended) of them?

I'm not sure about taking the entire template. For example, non-write background is a bit too progressive ;-) And in general, I think it's good to stay close to look of ordinary Boost docs.

But there are some spirit elements that I personally like.

1. Section headers which a visually distinguished -- in Spirit they are right at the top with prominent background. That's the same in Reece stylesheet, BTW.

This is easy to do in the CSS file. Simply define the '.title' style :). The problem is modifying chapter/section title rendering (should be possible, just require a little work, maybe with XSLT help for chapter/title elements?).


2. Nagivation arrows at the top of the page (not only bottom). It's much easier this way.

Shouldn't be too hard, I think.


3. Nice table. Tables with 3D borders that Docbook generates by default are not even near that.

Have you got an example of the sort of layout you'd like; that would help :).


4. Prominent code examples: with background and boundaries

This is a CSS problem: see the attachment :).


:D

Regards,
Reece

_________________________________________________________________
Sign-up for a FREE BT Broadband connection today! http://www.msn.co.uk/specials/btbroadband
th
{
   font-weight:      bold;
   text-align:       center;
}

.title
{
   font-weight:   bold;
   font-size:     2pc;
   font-family:   Times New Roman;
   margin-bottom: 1pc;
   text-align:    center;
}

.toc
{
   margin-left:   5%;
   margin-right:  5%;
   margin-bottom: 0pc;
   width:         50%;
}

.programlisting
{
   margin-left: 3pc;
   width:       50%;
}

.computeroutput
{
   font-family: Lucida Console;
   font-size:   80%;
}

.table
{
   text-align:    center;
   margin-bottom: 1pc;
}

@media screen
{
   a{ color: blue; }

   th, .title
   {
      background-color: lightskyblue;
   }

   .section-title
   {
      background-color: #EEE;
   }

   .programlisting
   {
      background-color: #EED;
      border:           0.1em ridge cyan;
      padding:          1pc;
   }

   .toc
   {
      border:           0.2em ridge lightcoral;
      padding:          0.5pc;
      background-color: #DDD;
   }
}

@media print
{
   a{ color: black; }
}


Reply via email to