Hi all,
I have a project that uses autotools (autoconf, automake and libtool).
I have been writing the manual for the project in docbook XML format
instead of tex. What is a common method for generating HTML (single
and multiple page) documentation from a docbook file within this
environment?
I
Rock Lobster wrote:
Hello,
I'm trying to convert our document into eclipse-help-html-files, and it
works, but the abbreviations for the output files are not too usable for me,
because I want to program an additional tool where I can group some themes
and chapters for some specific software
Hi Brendon,
I guess your approach is not that uncommon, and there's probably a few
success stories to learn from. I'm using two different approaches in
three projects. These are certainly not the only ways to do it, but
feel free to have a look at the setups.
Both libdbi
Hello,
In the chunked HTML output generated from a Docbook book document using
the html/chunk.xsl stylesheet with the params chunk.section.depth = 6
and use.id.as.filename = 1 some footer navigation links are wrong. For
example in the output files generated from the attached Docbook file the
Title: Re: [docbook-apps] list of figures in the TOC for
an appen
Hi Andreas
The code you tried needs to be
embedded in the template match=appendix copied from the
standard XSL stylesheet. You also need to ask for the TOC with
the xsl:param namegenerate.toc parameter.
Below is a copy direct
On Wed, Apr 11 2007 07:08:01 +0100, Brendon Costa wrote:
I have a project that uses autotools (autoconf, automake and libtool).
I have been writing the manual for the project in docbook XML format
instead of tex. What is a common method for generating HTML (single
and multiple page)
Hi,
Well, I use this very combination of tools that you describe, and I never
had such problems.
But I did copy your XML source and try it for myself. Interestingly, I got
the same error:
SEVERE: Exception
java.lang.ClassCastException:
org.apache.fop.layoutmgr.inline.WrapperLayoutManager
El Miércoles, 11 de Abril de 2007 22:50, Ron Catterall escribió:
fo:block xsl:use-attribute-sets=blockquote.properties
xsl:call-template name=anchor/
fo:block
!-- this test added --
xsl:if test=$keep.together != ''
xsl:attribute
El Miércoles, 11 de Abril de 2007 22:32, T.G. Mutato escribió:
?xml version=1.0 encoding=UTF-8?
!DOCTYPE book SYSTEM dtd/4.5/docbookx.dtd
book
bookinfo
titleMy First Book/title
authorfirstnameJane/firstnamesurnameDoe/surname/author
copyrightyear1998/yearholderJane
Thank you for the information Bob and Colin. The FOP 0.93 problem was
indeed related to the placement of the indexterm elements.
Thanks for the note too on fop1.extensions.
On 4/11/07, Bob Stayton [EMAIL PROTECTED] wrote:
While FOP 0.93 is better in many respects, it is still being actively
Title: Scott Hudson
Folks,
IHAC that needs to be able to support multiple sections within a
sidebar.
The model needs to support something like:
chapter
titleHow to Ensnare a Jedi/para
parablah/para
sidebar
titleWorking With Bounty Hunters/title
parablah/para
parablah/para
section
I can't duplicate this problem. Can you provide details of the stylesheet
version and processor? Are you using a customized chunking stylesheet? If
so, did you follow the guidelines for setting it up in two parts as
described in:
On 4/11/07, Scott Hudson [EMAIL PROTECTED] wrote:
IHAC that needs to be able to support multiple sections within a sidebar.
Ew...
Based on the current db v5 model, section is not allowed in a sidebar. How
would you handle these types of sections within a sidebar?
Bridgehead might work
Unfortunately, this is content that is outside the narrative flow of the
main text, and is about a page or two long. It's more like a feature
that you might see in many Trade publications...
Best regards,
--Scott
Keith Fahlgren wrote:
On 4/11/07, Scott Hudson [EMAIL PROTECTED] wrote:
IHAC
14 matches
Mail list logo
