On 6/19/07, John Maddock <[EMAIL PROTECTED]> wrote:
> Matias Capeletto wrote:
>
> > (a) __ website params __
> >    The new style, based on beta.boost.org including GroupedLinks and
> >    Google search box.
> >
> >    grouped.links.chapters.show   ( 'false'          )
> >    grouped.links.sections.show   ( 'false'          )
> >    search.box.show               ( 'false'          )
>
> I might be inclined to turn these on by default.

Ok, me too. The only one that makes me uncomfortable is the sections
GroupedLinks, because users must provide a version of his own now. If
I can manage to automate the creation of the xml definition when
boostbook runs, then this worry will vanished.

>
> > [[[[ proposed ]]]]]
> >
> > # only the new style is supported
> > page.style ( 'standard' )
> >
> > # other small js libs may appear, we support this from the beginning
> > javascript.lib.root ( concat($boost.root, '/doc/javascript/') )
> >
> > grouped.links.chapters.*   [ same as before,
> >                             but point to
> > boost.root/doc/boost_libs.xml ]
> > grouped.links.sections.*   [ same as before ]
> > search.box.*               [ same as before ]
> >
> >
> > Style sheet and graphics
> > -------------------------------------------------------------------
> > There are a lot of parameters here. IMO they can be reduced with
> > out loosing flexibility
> >
> > [[[[[ current ]]]]]
> >
> > html.stylesheet          ( 'boostbook.css' )
> > + Lots of parameters

> > [[[[[ proposed ]]]]]
> >
> > Only html.stylesheet          ( concat($boost.root,
> > '/doc/style/boostbook.css') )
>
> Yep.

Great.

> > Chunker params
> > ---------------------------------------------------------------
>
> If these are different from existing defaults, then we'll have to test the
> existing libraries, and make adjustments as required.

No, they are the same as before

> > fo params
> > ===========================
> > John? These are fine?
> >
> > # Needed for FOP 0.2, set to zero for FOP-0.9!
> > fop.extensions           ( 0     )
> > xep.extensions           ( 1     )
>
> I think it may be possible to turn on both FOP-1 and XEP extensions, which
> should keep most folks happy.  FOP-0.2 is pretty awful!  I'll check this.

Ok.

> > # pngs and pdf do not get along
> > admon.graphics.extension ( .svg  )
> > navig.graphics.extension ( .svg  )
>
> OK. The user can override these in his Jamfile anyway, so I think they
> should probably be moved to fo.xsl.

Good.

> > Unused params
> > ============================
> > These params will be removed
> >
> > doc.standalone          ( false )
>
> What does/did that do anyway?  I know some folks are using it?

I have no clue. It is not used anywhere! :)

> BTW, when/if you add docs for all this, don't forget to add a link to
> http://docbook.sourceforge.net/release/xsl/current/doc/ which is an
> invaluable reference for tweaking Docbook output.  The online book
> http://www.sagehill.net/docbookxsl/ is pretty useful too.

Agree. I have using both links a lot.

> Thanks for persevering with this, John.

The docs deserve it :)

King regards
Matias

PS: How we can check that my test of Strict XHTML validation are fine?
PS: Thanks to Daniel James, ie6 now support box-wrappers!

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Boost-docs mailing list
[email protected]
Unsubscribe and other administrative requests: 
https://lists.sourceforge.net/lists/listinfo/boost-docs

Reply via email to