Hi John.
All the below is just our experience, if it helps!
To better exploit DocBook, I use the IncludePage (UnfoldSubpages
should also work), with quiet=0 (which includes the page title), and
have changed the stylesheet to have that IncludePage page title
render as an h1... and i set html2db to respond to each 'h1' then as
a new chapter.
The same approach works with our (DocBook-sidestepping) use of
htmldoc, to create full pdf's right from html without true DocBook in
the intermediate step.
Added benefits of true DocBook? 'list of tables' (for all
'caption'-ed tables), 'list of figures' (for all 'alt'-ed images),
and index entries that auto-render (div tags, with indexterm:primary,
indexterm:secondary, etc.).
Thanks, and at least, I hope that helps you think about your scenario a bit!
Micki
At 12:24 PM -0700 8/5/04, php...@li... wrote:
>Message: 3
>From: John Cole <joh...@ua...>
>To: php...@li...
>Date: Thu, 5 Aug 2004 09:16:51 -0500
>Subject: [Phpwiki-talk] UnfoldSubpages patch...
>
>This message is in MIME format. Since your mail reader does not understand
>this format, some or all of this message may not be legible.
>
>------_=_NextPart_000_01C47AF5.ACED5230
>Content-Type: text/plain;
> charset="iso-8859-1"
>
>Reini,
> Here is another stab at fixing UnfoldSubpages...
>
> The problem is that the way it flows now, the options don't get used (and
>my DocBook stuff relies on them).
>
> Also, I'd like to add another parameter to UnfoldSubpages called divclass
>to optionally put the contenets of the plugin inside a user defined div tag.
>I'm attaching another patch to do that, called UnfoldSubpages_wish.patch :-)
>
> The reason for adding this is so that the html2db.xsl file can transform
>different plugin calls to differnt DocBook types (like one for chapter or
>prefix, etc)...
>
> I didn't know if it would be better to use class or id, it doesn't matter
>which one, but I'd like to add the same to the IncludePage plugin as well.
>
>Thanks,
>
>John
--
Micki
mailto:mic...@co...
|
