Re: [docbook-apps] computeroutput vs screen vs xmllint

2012-09-11 Thread Stefan Hinz
Bonjour Mathieu, We are internally using different docbook editors (vi, emacs, serna and xmlmind). To some extent, we would like to preserve a nice and clear history of revision of our XML files in SVN (subversion). For this we use a script based on xmllint --format to reformat to a unique

Re: [docbook-apps] titlepage.xsl anomaly

2012-09-11 Thread Jirka Kosek
On 11.9.2012 0:02, Richard Hamilton wrote: The titlepage template file (I presume you mean titlepage.xml) does have a default declaration (xhtml, as expected). In fact, once this started happening, I re-generated the distributed titlepage.xml file and got a generated titlepage.xsl file that

Re: [docbook-apps] titlepage.xsl anomaly

2012-09-11 Thread Gabor Kovesdan
Em 11-09-2012 10:02, Jirka Kosek escreveu: Ah, you have been using xsl-ns, right? I see the problem now, template/titlepage.xsl in xsl-ns distribution doesn't support ns parameter which is cruical. I have to investigate how xsl-ns is generated, I'm not using them regularly. I also remember

Re: [docbook-apps] computeroutput vs screen vs xmllint

2012-09-11 Thread Mathieu Malaterre
Stefan, On Tue, Sep 11, 2012 at 10:01 AM, Stefan Hinz stefan.h...@oracle.com wrote: We are internally using different docbook editors (vi, emacs, serna and xmlmind). To some extent, we would like to preserve a nice and clear history of revision of our XML files in SVN (subversion). For

Re: [docbook-apps] titlepage.xsl anomaly

2012-09-11 Thread Jirka Kosek
On 11.9.2012 0:02, Richard Hamilton wrote: So, I can manually fix the problem by adding a default namespace declaration to the generated titlepage.xsl file. However, I don't know why the epub3/titlepage.xsl file in the distribution puts div in a namespace, but a file generated from the

Re: [docbook-apps] titlepage.xsl anomaly

2012-09-11 Thread Gabor Kovesdan
Em 11-09-2012 10:14, Jirka Kosek escreveu: On 11.9.2012 0:02, Richard Hamilton wrote: So, I can manually fix the problem by adding a default namespace declaration to the generated titlepage.xsl file. However, I don't know why the epub3/titlepage.xsl file in the distribution puts div in a

Re: [docbook-apps] titlepage.xsl anomaly

2012-09-11 Thread Jirka Kosek
On 11.9.2012 10:39, Gabor Kovesdan wrote: For Slides, it works nicely! But it should be generated there as a part of the build process. Is there any way I can easily adjust this parameter? Build process sets this paremeter, for example makefile for epub3 says: include

[docbook-apps] Symbols section in index and specialized index

2012-09-11 Thread Maxime Bégnis
Hello, I'm using the specialized index feature in a document. The terms are filtered OK, but I have the "Symbols" section appearing in the specialized index with no content in it, which is expected since there is no symbols for the specialized index. It

Re: [docbook-apps] computeroutput vs screen vs xmllint

2012-09-11 Thread Stefan Hinz
Bonjour Mathieu, On Tue, Sep 11, 2012 at 10:01 AM, Stefan Hinz stefan.h...@oracle.com wrote: We are internally using different docbook editors (vi, emacs, serna and xmlmind). To some extent, we would like to preserve a nice and clear history of revision of our XML files in SVN

Re: [docbook-apps] computeroutput vs screen vs xmllint

2012-09-11 Thread Mathieu Malaterre
On Tue, Sep 11, 2012 at 11:33 AM, Stefan Hinz stefan.h...@oracle.com wrote: Bonjour Mathieu, On Tue, Sep 11, 2012 at 10:01 AM, Stefan Hinz stefan.h...@oracle.com wrote: We are internally using different docbook editors (vi, emacs, serna and xmlmind). To some extent, we would like to

Re: [docbook-apps] Symbols section in index and specialized index

2012-09-11 Thread Maxime Bégnis
Answering myself: I found the solution, on line 92 of "autoidx.xsl"(template "generate-basic-index"): div class="index" -- xsl:if test="$others and ($type = '' or count($others[@type = $type]) 0)" div class="indexdiv" ... It

Re: [docbook-apps] titlepage.xsl anomaly

2012-09-11 Thread Jirka Kosek
On 11.9.2012 10:39, Gabor Kovesdan wrote: For Slides, it works nicely! But it should be generated there as a part of the build process. Is there any way I can easily adjust this parameter? Or you could try this:

Re: [docbook-apps] Pretty-printing HTML and FO output

2012-09-11 Thread Andy Hatton
My thanks to everyone who replied, that's helped some and given me some other avenues to explore. On 10/09/12 21:49, Jirka Kosek wrote: On 10.9.2012 18:37, andy.hat...@oracle.com wrote: For FO, I noticed the following comment in fo/docbook.xsl !-- It is important to use indent=no here,