Re: Forcing a chapter to start on new page (FO)

Hi,
You could set the stylesheet parameter named double.sided to 1.  That will force new 
chapters to start on an odd page.

Bob Stayton
Sagehill Enterprises
bobs <at> sagehill.net

----- Original Message ----- 
From: "Jeffrey Trimble" <jtrimble <at> cc.ysu.edu>
To: "DocBook Apps" <docbook-apps <at> lists.oasis-open.org>
Sent: Sunday, February 28, 2010 3:54 PM
Subject: [docbook-apps] Forcing a chapter to start on new page (FO)

> Is there a quick (and maybe dirty) way to force each chapter to start  on a new page 
> (odd number page) via the print.xsl
> stylesheet for PDF generation?
>
> For example, my Chapter 1 is only one page.  Chapter 2 begins on page  two, instead 
> of page 3.
>
> Thanks in advance,
>
>
> Jeffrey Trimble
> System LIbrarian
> William F.  Maag Library
> Youngstown State University
> 330.941.2483 (Office)
> jtrimble <at> cc.ysu.edu

Re: Footer odd/even page problem when chapters do not begin on an odd page

On Sat, Feb 27, 2010 at 12:29 AM, Bob Stayton <bobs <at> sagehill.net> wrote:
> Hi,

Hi Bob,

Many thanks for your help.

> Did you customize the page-sequence-masters as well?

No, I did not -- my knowledge of the stylesheets is limited and I
didn't know what to try next.

With the customisation, per your advice, I managed to have chapters on
auto and the footers rendered correctly.

When I attempted to do the same for all book parts, however, I
encountered another problem:

- My book has parts and my first part falls on an odd page (left).

- The first part is just a single page, and the second page in the
book is the first page of the first chapter. It falls on an even page
(right).

- The initial.page.number template will return 1 for the first page of
the first part because it's the first page of the book (the front
matter uses roman numerals)

- The footer of the second page (even) will be rendered using the odd
layout. (And, from then on, all the pages will have the footer layouts

RE: RE: Test condition to check if the current node is the first child

Larry,

Thanks for the suggestion. But it does not work if white spaces exist
between <note> and <para> such 
As

<note>       

   <para>
...
</para></note>

Sherwood

-----Original Message-----
From: Rowland, Larry [mailto:larry.rowland <at> hp.com] 
Sent: Wednesday, February 24, 2010 6:04 PM
To: Sherwood Hu; docbook-apps <at> lists.oasis-open.org
Subject: [docbook-apps] RE: Test condition to check if the current node
is the first child

You might try testing for there being no preceding sibling:

   preceding-sibling::node() = ''

Regards,
Larry Rowland

________________________________

RE: RE: Test condition to check if the current node is the first child

Sherwood,

Sorry, my mistake.

Try preceding-sibling::element (or preceding-sibling::*) to avoid the white space issue.

LRR 

-----Original Message-----
From: Sherwood Hu [mailto:sherwood <at> morovia.com] 
Sent: Monday, March 01, 2010 9:35 AM
To: docbook-apps <at> lists.oasis-open.org
Subject: RE: [docbook-apps] RE: Test condition to check if the current node is the first child

Larry,

Thanks for the suggestion. But it does not work if white spaces exist
between <note> and <para> such 
As

<note>       

   <para>
...
</para></note>

Sherwood

-----Original Message-----
From: Rowland, Larry [mailto:larry.rowland <at> hp.com] 

RE: Re: [docbook] DocBook and Google Summer of Code ?

Stefan and the DocBook community,

Stefan, thanks for bringing the deadline to everyone's attention.

I would be glad to act as administrator for the DocBook project.

To that end, there are a few things that need to happen that I cannot do
on my own:

1) We need some mentors; so far, Stefan is the only person who has
signed on as a mentor. Seems to me that we need at least two or three
projects with mentors to make a credible application.

2) We need backup mentor for each project. It's not essential, but it
would help the application and would also make sure that students have
more than one person to work with in case someone is out of town, etc.

I suggest the following schedule:

1) Until March 8 (next Monday) I'll leave the wiki open
(http://docbook.xmlpress.net) for anyone to edit (for those just looking
into this, you need to sign up, but it's automatic and easy). Please
look at the projects, add any you are willing to be mentor for, and sign
up as mentor or backup mentor for any project. Also, if you sign up as a
mentor, please fill out the description if it needs some extra
information, and send me your contact information.

2) On March 8, I'll remove any projects that don't have mentors, and if
we have at least two projects with mentors, I'll begin preparing the
application.

Missing toc levels in Javahelp

Hello,

I tried to generate some javahelp from the file
docsrc/reference.xml.included from the DocBook XSL packages for usage
with the dbdoclet gui.

I run into a problem, because the generated navigation tree always ended
at the part level. It never showed the reference level or anything
deeper nested.

The structure of the file is:

set
  book
    part
      reference
        refentry
        ...

The problem seems to be the following template from javahelp.xsl

If it matches a part element, it doesn't look for reference child nodes,
but only for direct refentry tags. If I add the reference element to the
apply-templates call, everything seems to function correctly.

<xsl:template match="part|reference|preface|chapter|appendix|article"
              mode="jhtoc">
  <xsl:variable name="id">
    <xsl:call-template name="object.id"/>
  </xsl:variable>

Re: Forcing a chapter to start on new page (FO)

Re: Convert OpenDocument Presentation [.odp] to docbook

On Wed, Feb 24, 2010 at 1:40 PM, Mathieu Malaterre
<mathieu.malaterre <at> gmail.com> wrote:
> On Wed, Feb 24, 2010 at 1:19 PM, Markus Hoenicka
> <markus.hoenicka <at> mhoenicka.de> wrote:
>> Mathieu Malaterre <mathieu.malaterre <at> gmail.com> was heard to say:
>>
>>>  After reading the recent post about converting OpenOffice document
>>> to docbook. I tried using OO to convert an old presentation (in odp)
>>> to docbook. However I cannot select docbook as output format from the
>>> GUI. Does anyone knows if this is possible ? Or is there another way
>>> to convert an odp to docbook ?
>>>
>>
>> OO allows to save presentations to HTML though. I've never tried that, but
>> you may be able to recover the textual information and maybe some of the
>> structural information from there.
>
> I gave it a shot. I have lost all complex figures (multiples images)
> and all vectorial drawing are also lost...
>

Just FYI. The export function from OpenOffice 3.1 (debian/linux) did
not work for me. Any graphic with vectorial stuff were badly exported,
or worse where not even legal SVG file.

I found out one can achieve decent result, by exporting the odp to
pdf. Then use pdf2svg:

http://www.cityinthesky.co.uk/pdf2svg.html

Please note that any text is simply lost, as fonts are converted to
vectorial objects.

HTH
--

-- 
Mathieu

More on double-sided mystery error

Here's the output when I attempt to transform my docbook into a PDF.   
This output error came up:

WARNING: Mismatch: root (http://www.w3.org/1999/XSL/Format) vs. page- 
sequence (http://www.w3.org/1999/XSL/Format)
Mar 2, 2010 8:55:57 AM org.apache.fop.fo.FOTreeBuilder fatalError
SEVERE: javax.xml.transform.TransformerException:  
java.lang.IllegalStateException: endElement() called for fo:root where  
there is no current element.
Mar 2, 2010 8:55:57 AM org.apache.fop.cli.Main startFOP
SEVERE: Exception
Throwable occurred: javax.xml.transform.TransformerException:  
java.lang.IllegalStateException: endElement() called for fo:root where  
there is no current element.
        at  
org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:168)
        at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java: 
115)
        at org.apache.fop.cli.Main.startFOP(Main.java:166)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at  
sun 
.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 
39)
        at  
sun 
.reflect 
.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java: 
37)
        at java.lang.reflect.Method.invoke(Method.java:599)
        at  
org.apache.fop.cli.Main.startFOPWithDynamicClasspath(Main.java:132)
        at org.apache.fop.cli.Main.main(Main.java:199)

---------

; SystemID: http://docbook.sourceforge.net/release/xsl/current/fo/docbook.xsl 
; Line#: 224; Column#: 59
javax.xml.transform.TransformerException:  
java.lang.IllegalStateException: endElement() called for fo:root where  
there is no current element.
        at  
org 
.apache 
.xalan.transformer.TransformerImpl.executeChildTemplates(Unknown Source)
        at org.apache.xalan.templates.ElemIf.execute(Unknown Source)
        at  
org 
.apache 
.xalan.transformer.TransformerImpl.executeChildTemplates(Unknown Source)
        at org.apache.xalan.templates.ElemChoose.execute(Unknown Source)
        at  
org 
.apache 
.xalan.transformer.TransformerImpl.executeChildTemplates(Unknown Source)
        at org.apache.xalan.templates.ElemChoose.execute(Unknown Source)
        at  
org 
.apache 
.xalan.transformer.TransformerImpl.executeChildTemplates(Unknown Source)
        at org.apache.xalan.templates.ElemChoose.execute(Unknown Source)
        at  
org 
.apache 
.xalan.transformer.TransformerImpl.executeChildTemplates(Unknown Source)
        at  
org 
.apache.xalan.transformer.TransformerImpl.applyTemplateToNode(Unknown  
Source)
        at  
org.apache.xalan.transformer.TransformerImpl.transformNode(Unknown  
Source)
        at  
org.apache.xalan.transformer.TransformerImpl.transform(Unknown Source)
        at  
org.apache.xalan.transformer.TransformerImpl.transform(Unknown Source)
        at  
org.apache.xalan.transformer.TransformerImpl.transform(Unknown Source)
        at  
org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:165)
        at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java: 
115)
        at org.apache.fop.cli.Main.startFOP(Main.java:166)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at  
sun 
.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 
39)
        at  
sun 
.reflect 
.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java: 
37)
        at java.lang.reflect.Method.invoke(Method.java:599)
        at  
org.apache.fop.cli.Main.startFOPWithDynamicClasspath(Main.java:132)
        at org.apache.fop.cli.Main.main(Main.java:199)
Caused by: java.lang.IllegalStateException: endElement() called for  
fo:root where there is no current element.
        at org.apache.fop.fo.FOTreeBuilder 
$MainFOHandler.endElement(FOTreeBuilder.java:367)
        at  
org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:194)
        at  
org.apache.xml.serializer.ToXMLSAXHandler.endElement(Unknown Source)
        at  
org.apache.xalan.templates.ElemLiteralResult.execute(Unknown Source)
        at  
org 
.apache 
.xalan.templates.ElemApplyTemplates.transformSelectedNodes(Unknown  
Source)
        at  
org.apache.xalan.templates.ElemApplyTemplates.execute(Unknown Source)
        at  
org 
.apache 
.xalan.templates.ElemApplyTemplates.transformSelectedNodes(Unknown  
Source)
        at  
org.apache.xalan.templates.ElemApplyTemplates.execute(Unknown Source)
        ... 23 more

Jeffrey Trimble
System LIbrarian
William F.  Maag Library
Youngstown State University
330.941.2483 (Office)
jtrimble <at> cc.ysu.edu
http://www.maag.ysu.edu
http://digital.maag.ysu.edu
"The spice must flow..."

Jeffrey Trimble
System LIbrarian
William F.  Maag Library
Youngstown State University
330.941.2483 (Office)
jtrimble <at> cc.ysu.edu
http://www.maag.ysu.edu
http://digital.maag.ysu.edu
"The spice must flow..."

RE: Compile xsl with xalan

|  -----Original Message-----
|  From: Compagnon Christopher 
|  
|  I try to compile a docbook xsl with xalan and XSLTC option 
|  but it does not work.
|  
|  java -jar E:\Programmes\xalan-j_2_7_1\xalan.jar -XSLTC -XJ 
|  bk2html.jar -XSL 
|  E:\Programmes\docbook\docbook-xsl-1.75.0\xhtml-1_1\docbook.xsl
|  ERREUR :  'null'
|  ERREUR BLOQUANTE : 'Impossible de compiler la feuille de style'

XSLTC is known to have problems with DocBook-XSL. I have tried to make it
work, but without success.

Some more information:
http://sourceforge.net/tracker/index.php?func=detail&aid=1501592&group_id=21
935&atid=373750
http://issues.apache.org/jira/browse/XALANJ-2318
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5056688

Mauritz