[docbook-apps] Generating HTML from docbook in autotools project

2007-04-10 Thread Brendon Costa
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 am not sure which of the many tools are most commonly used, and
which is simplest to integrate into an automake based project. I would
think that many have at least attempted this and so was wondering if
people have any advice?



Thanks,
Brendon.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [docbook-apps] sorting Docbook

2007-04-10 Thread Bob Stayton

Hi,
Actually, your stylesheet does work.  When I downloaded your blog-sort.xsl
and blog.xml files, and applied the stylesheet with xsltproc:

xsltproc -o sorted.xml blog-sort.xsl blog.xml

I got a correctly sorted output, with the dates in this order in 
sorted.xml:


 2005-01-01
 2005-07-07
 2005-08-27
 2005-08-27
 2005-08-27
 2005-08-27
 2005-08-27
 2005-08-27
 2005-08-27
 2005-08-27
 2005-08-27
 2005-08-27
 2005-08-27
 2005-08-27
2005-08-27
2005-08-27
2005-08-27
2005-08-27
2005-08-27
2005-08-27
2005-08-27
 2005-08-28
2005-09-22
 2005-09-23
2005-09-23
 2005-10-05
2005-10-05
 2005-10-08
2005-11-03
 2005-11-26
2005-11-27
2005-12-05
2005-12-06
 2005-12-07
 2005-12-20
 2005-12-26
2005-12-26
 2005-12-28
 2006-01-05
 2006-01-30
 2006-02-20
2006-02-20
2006-04-27
 2006-05-09
2006-05-09
2006-05-26
2006-05-30
 2006-08-10
2006-08-10
 2006-12-01
 2006-12-01
 2006-12-04

I don't understand why it didn't work for you.

Bob Stayton
Sagehill Enterprises
DocBook Consulting
[EMAIL PROTECTED]


- Original Message - 
From: "Matej Cepl" <[EMAIL PROTECTED]>

To: 
Sent: Saturday, April 07, 2007 3:25 PM
Subject: [docbook-apps] sorting Docbook



Hi,

trying to switch my blog to Docbook (as source, of course HTML/Atom is to
be produced via XSLT), and I got stuck with one (I am afraid, rather
elementary) problem with XSLT. I have compiled all my blogs into one XML
file (it is not valid Docbook yet; http://www.ceplovi.cz/matej/blogdata/
blog.xml) and then tried to sort the entries according to their info/date
element using my own variant (http://www.ceplovi.cz/matej/blogdata/blog-
sort.xsl) of sorting XSLT stylesheet from http://www.xml.com/pub/
a/2002/07/03/transform.html However, xsltproc when running over the
document (and it is not sorted, for example entry "Mannheim’s Paradox" is
out of order) does exactly nothing (checked with diff).

I am doing probably some really stupid mistake, but I cannot find for the
world, what's that.

Can anybody help me, please?

Thanks,

Matej
--
http://www.ceplovi.cz/matej/blog/, Jabber: ceplmajabber.cz
GPG Finger: 89EF 4BC6 288A BF43 1BAB  25C3 E09F EF25 D964 84AC

He uses statistics as a drunken man uses lamp-posts... for
support, rather than illumination.
 -- Andrew Lang


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: [docbook-apps] Reusing where a should be - and the reverse

2007-04-10 Thread Johnson, Eric
I too have run into the same problem and resorted to using xincludes to
import all of the required paragraphs... It works but it is a pain. 

> -Original Message-
> From: Peter Desjardins [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, April 10, 2007 11:52 AM
> To: David Cramer (Tech Pubs); docbook-apps@lists.oasis-open.org
> Subject: RE: [docbook-apps] Reusing  where a 
>  should be - and the reverse
> 
> That xpointer did work perfectly.  Thank you!
> 
> This may be a question for the docbook list but is this a 
> common problem encountered when reusing content?  I've run 
> into it many times when making short excerpts of material in 
> larger technical references.
> 
> Now I have a working solution so I'm happy.  XMLMind won't 
> accept the syntax of the xpointer but since I'm actually 
> writing the content in other documents it doesn't matter.
> 
> Peter Desjardins
> 
> > -Original Message-
> > From: David Cramer (Tech Pubs) [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, April 10, 2007 09:39
> > To: Peter Desjardins; docbook-apps@lists.oasis-open.org
> > Subject: RE: [docbook-apps] Reusing  where a 
>  should 
> > be - and the reverse
> > 
> > Try this:
> > 
> > 
> >  href="docbook-file-containing-the-modular-content.xml"
> > xmlns:xi="http://www.w3.org/2001/XInclude";
> >  
> > xpointer="xpointer(//[EMAIL PROTECTED]'IdOfTheSectionElement']/*)"/>
> > 
> > 
> > David
> > 
> > > Reading Chapter 22. Modular DocBook files in DocBook XSL 
> led me to 
> > > believe that the following xi:include could solve the
> > problem for me.  
> > > I expect it to include every child element of a 
> > element in
> > > the  element.
> > > 
> > > 
> > >  > href="docbook-file-containing-the-modular-content.xml"
> > > xmlns:xi="http://www.w3.org/2001/XInclude";
> > > xpointer="element(IdOfTheSectionElement/*)" 
> > > /> 
> > > 
> > > But the xi:include fails.  I use xmllint to resolve
> > xi:includes.  It
> > > gives the following errors:
> > > 
> > > docbook-file-that-is-including.xml:11: element include: 
> > > XInclude error :
> > > XPointer evaluation failed: #element(IdOfTheSectionElement/*)
> > > docbook-file-that-is-including.xml:11: element include: 
> > > XInclude error :
> > > could not load
> > > docbook-file-containing-the-modular-content.xml, and no
> > fallback was
> > > found
> > > 
> > > Is my xpointer syntax incorrect?  Other xi:includes from the same 
> > > source file resolved without any trouble (they include entire 
> > > elements).
> > > 
> > > Is there a better way to reuse  and  
> elements in 
> > > each other's hierarchical places?
> > > 
> > > In case it matters, here's my xmllint version:
> > > 
> > > $ xmllint --version
> > > xmllint: using libxml version 20626
> > >compiled with: Threads Tree Output Push Reader Patterns Writer
> > > SAXv1 FTP HTTP DTDValid HTML Legacy C14N Catalog XPath XPointer 
> > > XInclude Iconv ISO8859X Unicode Regexps Automata Expr Schemas 
> > > Schematron Modules Debug
> > > 
> > > 
> > > Thanks for your help!
> > > 
> > > Peter Desjardins
> > > 
> > > 
> > 
> -
> > > To unsubscribe, e-mail: 
> > [EMAIL PROTECTED]
> > > For additional commands, e-mail: 
> > > [EMAIL PROTECTED]
> > > 
> > > 
> > 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: 
> [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: [docbook-apps] Reusing where a should be - and the reverse

2007-04-10 Thread Peter Desjardins
That xpointer did work perfectly.  Thank you!

This may be a question for the docbook list but is this a common problem
encountered when reusing content?  I've run into it many times when
making short excerpts of material in larger technical references.

Now I have a working solution so I'm happy.  XMLMind won't accept the
syntax of the xpointer but since I'm actually writing the content in
other documents it doesn't matter.

Peter Desjardins

> -Original Message-
> From: David Cramer (Tech Pubs) [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, April 10, 2007 09:39
> To: Peter Desjardins; docbook-apps@lists.oasis-open.org
> Subject: RE: [docbook-apps] Reusing  where a 
>  should be - and the reverse
> 
> Try this:
> 
> 
>  xmlns:xi="http://www.w3.org/2001/XInclude";
>  
> xpointer="xpointer(//[EMAIL PROTECTED]'IdOfTheSectionElement']/*)"/>
> 
> 
> David
> 
> > Reading Chapter 22. Modular DocBook files in DocBook XSL led me to 
> > believe that the following xi:include could solve the 
> problem for me.  
> > I expect it to include every child element of a  
> element in 
> > the  element.
> > 
> > 
> >  href="docbook-file-containing-the-modular-content.xml"
> > xmlns:xi="http://www.w3.org/2001/XInclude";
> > xpointer="element(IdOfTheSectionElement/*)" 
> > /> 
> > 
> > But the xi:include fails.  I use xmllint to resolve 
> xi:includes.  It 
> > gives the following errors:
> > 
> > docbook-file-that-is-including.xml:11: element include: 
> > XInclude error :
> > XPointer evaluation failed: #element(IdOfTheSectionElement/*)
> > docbook-file-that-is-including.xml:11: element include: 
> > XInclude error :
> > could not load
> > docbook-file-containing-the-modular-content.xml, and no 
> fallback was 
> > found
> > 
> > Is my xpointer syntax incorrect?  Other xi:includes from the same 
> > source file resolved without any trouble (they include entire 
> > elements).
> > 
> > Is there a better way to reuse  and  elements in 
> > each other's hierarchical places?
> > 
> > In case it matters, here's my xmllint version:
> > 
> > $ xmllint --version
> > xmllint: using libxml version 20626
> >compiled with: Threads Tree Output Push Reader Patterns Writer 
> > SAXv1 FTP HTTP DTDValid HTML Legacy C14N Catalog XPath XPointer 
> > XInclude Iconv ISO8859X Unicode Regexps Automata Expr Schemas 
> > Schematron Modules Debug
> > 
> > 
> > Thanks for your help!
> > 
> > Peter Desjardins
> > 
> > 
> -
> > To unsubscribe, e-mail: 
> [EMAIL PROTECTED]
> > For additional commands, e-mail: 
> > [EMAIL PROTECTED]
> > 
> > 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: [docbook-apps] Reusing where a should be - and the reverse

2007-04-10 Thread David Cramer (Tech Pubs)
Try this:


http://www.w3.org/2001/XInclude";
 
xpointer="xpointer(//[EMAIL PROTECTED]'IdOfTheSectionElement']/*)"/> 


David

> Reading Chapter 22. Modular DocBook files in DocBook XSL led 
> me to believe that the following xi:include could solve the 
> problem for me.  I expect it to include every child element 
> of a  element in the  element.
> 
> 
>  xmlns:xi="http://www.w3.org/2001/XInclude";
> xpointer="element(IdOfTheSectionElement/*)" 
> /> 
> 
> But the xi:include fails.  I use xmllint to resolve 
> xi:includes.  It gives the following errors:
> 
> docbook-file-that-is-including.xml:11: element include: 
> XInclude error :
> XPointer evaluation failed: #element(IdOfTheSectionElement/*)
> docbook-file-that-is-including.xml:11: element include: 
> XInclude error :
> could not load 
> docbook-file-containing-the-modular-content.xml, and no 
> fallback was found
> 
> Is my xpointer syntax incorrect?  Other xi:includes from the 
> same source file resolved without any trouble (they include 
> entire elements).
> 
> Is there a better way to reuse  and  
> elements in each other's hierarchical places?
> 
> In case it matters, here's my xmllint version:
> 
> $ xmllint --version
> xmllint: using libxml version 20626
>compiled with: Threads Tree Output Push Reader Patterns 
> Writer SAXv1 FTP HTTP DTDValid HTML Legacy C14N Catalog XPath 
> XPointer XInclude Iconv ISO8859X Unicode Regexps Automata 
> Expr Schemas Schematron Modules Debug
> 
> 
> Thanks for your help!
> 
> Peter Desjardins
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: 
> [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



AW: [docbook-apps] tables aren't breaking onto the next page

2007-04-10 Thread Hinrich Aue
For me the following worked.

 





auto

always



 

Hinrich

 

  _  

Von: Jeff Powanda [mailto:[EMAIL PROTECTED] 
Gesendet: Friday, April 06, 2007 3:52 AM
An: docbook-apps@lists.oasis-open.org
Betreff: [docbook-apps] tables aren't breaking onto the next page

 

When I output to PDF, long tables aren't breaking onto the next page, but
are running below the page margin. I've tried changing the keep together
properties like this.

 



 

  auto

  auto





 



 

But that doesn't work. How can I get long tables to break onto the next
page?

 

I'm using DocBook XSL 1.72 and FOP 0.93.

 

Regards,

Jeff