
I can savely transform each chapter of my book, but when I try to transform the entire book, I encounter the following error: The process 'Apache FOP' ended with code: 1. The error was: ERROR - Exception org.apache.fop.apps.FOPException java.util.NoSuchElementException at org.apache.fop.cli.InputHandlerFOP.transformTo(Unknown Source) at org.apache.fop.cli.InputHandlerFOP.renderTo(Unknown Source) at org.apache.fop.cli.Main.startFOP(Main.java:186) at org.apache.fop.cli.Main.main(Main.java:217) Caused by: java.util.NoSuchElementException at org.apache.fop.layoutmgr.LMiter.next(LMiter.java:69) at org.apache.fop.layoutmgr.LMiter.next(LMiter.java:27) at org.apache.fop.layoutmgr.AbstractLayoutManager.setCurrentChildLM(AbstractLayoutManager.java:132) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:275) at org.apache.fop.layoutmgr.list.ListItemContentLayoutManager.getNextKnuthElements(ListItemContentLayoutManager.java:234) at org.apache.fop.layoutmgr.list.ListItemLayoutManager.getNextKnuthElements(ListItemLayoutManager.java:251) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:500) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:293) at org.apache.fop.layoutmgr.list.ListBlockLayoutManager.getNextKnuthElements(ListBlockLayoutManager.java:103) at org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:148) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:293) at org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113) at org.apache.fop.layoutmgr.FlowLayoutManager.getNextChildElements(FlowLayoutManager.java:225) at org.apache.fop.layoutmgr.FlowLayoutManager.addChildElements(FlowLayoutManager.java:147) at org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:121) at org.apache.fop.layoutmgr.PageBreaker.getNextKnuthElements(PageBreaker.java:269) at org.apache.fop.layoutmgr.AbstractBreaker.getNextBlockList(AbstractBreaker.java:787) at org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:178) at org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:451) at org.apache.fop.layoutmgr.PageBreaker.doLayout(PageBreaker.java:112) at org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:141) at org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:267) at org.apache.fop.fo.pagination.PageSequence.endOfNode(PageSequence.java:130) at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilder.java:360) at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:190) at net.sf.saxon.event.ContentHandlerProxy.endElement(Unknown Source) at net.sf.saxon.event.NamespaceReducer.endElement(NamespaceReducer.java:228) at net.sf.saxon.event.ComplexContentOutputter.endElement(ComplexContentOutputter.java:578) at net.sf.saxon.event.ReceivingContentHandler.endElement(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImplXerces.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at net.sf.saxon.event.Sender.sendSAXSource(Sender.java:427) at net.sf.saxon.event.Sender.send(Sender.java:138) at net.sf.saxon.jaxp.IdentityTransformer.transform(IdentityTransformer.java:383) ... 4 more --------- java.util.NoSuchElementException at org.apache.fop.layoutmgr.LMiter.next(LMiter.java:69) at org.apache.fop.layoutmgr.LMiter.next(LMiter.java:27) at org.apache.fop.layoutmgr.AbstractLayoutManager.setCurrentChildLM(AbstractLayoutManager.java:132) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:275) at org.apache.fop.layoutmgr.list.ListItemContentLayoutManager.getNextKnuthElements(ListItemContentLayoutManager.java:234) at org.apache.fop.layoutmgr.list.ListItemLayoutManager.getNextKnuthElements(ListItemLayoutManager.java:251) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:500) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:293) at org.apache.fop.layoutmgr.list.ListBlockLayoutManager.getNextKnuthElements(ListBlockLayoutManager.java:103) at org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:148) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:293) at org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113) at org.apache.fop.layoutmgr.FlowLayoutManager.getNextChildElements(FlowLayoutManager.java:225) at org.apache.fop.layoutmgr.FlowLayoutManager.addChildElements(FlowLayoutManager.java:147) at org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:121) at org.apache.fop.layoutmgr.PageBreaker.getNextKnuthElements(PageBreaker.java:269) at org.apache.fop.layoutmgr.AbstractBreaker.getNextBlockList(AbstractBreaker.java:787) at org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:178) at org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:451) at org.apache.fop.layoutmgr.PageBreaker.doLayout(PageBreaker.java:112) at org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:141) at org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:267) at org.apache.fop.fo.pagination.PageSequence.endOfNode(PageSequence.java:130) at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilder.java:360) at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:190) at net.sf.saxon.event.ContentHandlerProxy.endElement(Unknown Source) at net.sf.saxon.event.NamespaceReducer.endElement(NamespaceReducer.java:228) at net.sf.saxon.event.ComplexContentOutputter.endElement(ComplexContentOutputter.java:578) at net.sf.saxon.event.ReceivingContentHandler.endElement(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImplXerces.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at net.sf.saxon.event.Sender.sendSAXSource(Sender.java:427) at net.sf.saxon.event.Sender.send(Sender.java:138) at net.sf.saxon.jaxp.IdentityTransformer.transform(IdentityTransformer.java:383) at org.apache.fop.cli.InputHandlerFOP.transformTo(Unknown Source) at org.apache.fop.cli.InputHandlerFOP.renderTo(Unknown Source) at org.apache.fop.cli.Main.startFOP(Main.java:186) at org.apache.fop.cli.Main.main(Main.java:217) I have already increased the size of memory to be used. I donot see where the error occurs. Please point me to the source of the trouble. Thanks a lot Bernhard -- spitzhalde9 D-79853 lenzkirch bernhard.kleine@gmx.net www.b-kleine.com, www.urseetal.net - thunderbird mit enigmail GPG schlüssel: D5257409 fingerprint: 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09

I have analyzed the situation: When I transform the glossar of my book, transformation is without trouble. However, when transforming the whole book plus the glossar, it stumbles I then analyzed the glossar: It has seven glossdivs. The last one consists of some 20 glossdefs, of which I show the last ones: <glossentry xml:id="glo.Tumor"> <glossterm>Tumor</glossterm> <glossdef> <para>Als Tumor wird zunächst eine raumfordernde Wucherung von Zellen bezeichnet, ein synonymer Ausdruck ist Neoplasie. Dabei gibt es gutartige Tumoren und bösartige. Je nach Ort der Geschwulst und nach Art des verdrängten und geschädigten Gewebes können Krankheiten bis hin zum Tod entstehen. Bösartige Tumoren sind die Ursache von Krebs, bei dem sich ausgehend von den ursprünglichen Tumorzellen weitere Geschwulste (Metatasen) in anderen Körperregionen bilden.</para> </glossdef> </glossentry> <glossentry xml:id="glo.geneticCode" xreflabel="Glo.T Genetischer Code"> <glossterm>Genetischer Code<indexterm> <primary>Genetischer Code</primary> </indexterm></glossterm> <glossdef> <para> <table frame="sides" rowsep="0" colsep="0"> [163 lines] </para> </glossdef> </glossentry> </glossdiv> </glossary> </sect2> It is this table which made the transformation choke. But only in the context of the book, not in the glossar itself. Can you please explain to me what I do wrong and how to change the behaviour? I have changed the transformation scenario to: and are using the following stylesheet: <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:d="http://docbook.org/ns/docbook" version="1.0"> <xsl:import href="http://docbook.sourceforge.net/release/xsl-ns/current/fo/docbook.xsl"/> <xsl:param name="caption.align">justify</xsl:param> <xsl:template match="d:mediaobject/d:caption"> <fo:block role="caption"> <xsl:if test="$caption.align = 'right' or $caption.align = 'left' or $caption.align = 'justify' or $caption.align = 'center'"> <xsl:attribute name="text-align"> <xsl:value-of select="$caption.align"/> </xsl:attribute> </xsl:if> <xsl:apply-templates/> </fo:block> </xsl:template> </xsl:stylesheet> Regards Bernhard -- spitzhalde9 D-79853 lenzkirch bernhard.kleine@gmx.net www.b-kleine.com, www.urseetal.net - thunderbird mit enigmail GPG schlüssel: D5257409 fingerprint: 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09

Hi Bernhard, I’m not an FO expert, but have you tried omitting the para around the table in the glossdef? It will be equally valid and maybe it will pass the processor’s quirks. Gerrit On 08.10.2018 22:02, Bernhard Kleine wrote:
I have analyzed the situation:
When I transform the glossar of my book, transformation is without trouble. However, when transforming the whole book plus the glossar, it stumbles
I then analyzed the glossar: It has seven glossdivs. The last one consists of some 20 glossdefs, of which I show the last ones:
<glossentry xml:id="glo.Tumor"> <glossterm>Tumor</glossterm> <glossdef> <para>Als Tumor wird zunächst eine raumfordernde Wucherung von Zellen bezeichnet, ein synonymer Ausdruck ist Neoplasie. Dabei gibt es gutartige Tumoren und bösartige. Je nach Ort der Geschwulst und nach Art des verdrängten und geschädigten Gewebes können Krankheiten bis hin zum Tod entstehen. Bösartige Tumoren sind die Ursache von Krebs, bei dem sich ausgehend von den ursprünglichen Tumorzellen weitere Geschwulste (Metatasen) in anderen Körperregionen bilden.</para> </glossdef> </glossentry> <glossentry xml:id="glo.geneticCode" xreflabel="Glo.T Genetischer Code"> <glossterm>Genetischer Code<indexterm> <primary>Genetischer Code</primary> </indexterm></glossterm> <glossdef> <para> <table frame="sides" rowsep="0" colsep="0"> [163 lines] </para> </glossdef> </glossentry> </glossdiv> </glossary> </sect2>
It is this table which made the transformation choke. But only in the context of the book, not in the glossar itself. Can you please explain to me what I do wrong and how to change the behaviour?
I have changed the transformation scenario to:
and are using the following stylesheet:
<?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:d="http://docbook.org/ns/docbook" version="1.0"> <xsl:import href="http://docbook.sourceforge.net/release/xsl-ns/current/fo/docbook.xsl"/> <xsl:param name="caption.align">justify</xsl:param>
<xsl:template match="d:mediaobject/d:caption"> <fo:block role="caption"> <xsl:if test="$caption.align = 'right' or $caption.align = 'left' or $caption.align = 'justify' or $caption.align = 'center'"> <xsl:attribute name="text-align"> <xsl:value-of select="$caption.align"/> </xsl:attribute> </xsl:if> <xsl:apply-templates/> </fo:block> </xsl:template> </xsl:stylesheet>
Regards Bernhard
-- spitzhalde9 D-79853 lenzkirch bernhard.kleine@gmx.net www.b-kleine.com,www.urseetal.net - thunderbird mit enigmail GPG schlüssel: D5257409 fingerprint: 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com https://www.oxygenxml.com/mailman/listinfo/oxygen-user
-- Gerrit Imsieke Geschäftsführer / Managing Director le-tex publishing services GmbH Weissenfelser Str. 84, 04229 Leipzig, Germany Phone +49 341 355356 110, Fax +49 341 355356 510 gerrit.imsieke@le-tex.de, http://www.le-tex.de Registergericht / Commercial Register: Amtsgericht Leipzig Registernummer / Registration Number: HRB 24930 Geschäftsführer / Managing Directors: Gerrit Imsieke, Svea Jelonek, Thomas Schmidt ---------------------------------------------- Warum wir dieses Jahr nicht auf der Frankfurter Buchmesse sind: https://www.le-tex.de/de/stellungnahme_buchmesse-2018.html

Hi Bernhard, If you publish to PDF without your customizations do you obtain the same problem? You will probably have to trim down your DocBook file to a minimum until you have a minimal sample with which the PDF processor problem can be reproduced. Then you can send it over to "support@oxygenxml.com" and we can take a look at it. Regards, Radu Radu Coravu <oXygen/> XML Editor http://www.oxygenxml.com On 10/8/2018 11:02 PM, Bernhard Kleine wrote:
I have analyzed the situation:
When I transform the glossar of my book, transformation is without trouble. However, when transforming the whole book plus the glossar, it stumbles
I then analyzed the glossar: It has seven glossdivs. The last one consists of some 20 glossdefs, of which I show the last ones:
<glossentry xml:id="glo.Tumor"> <glossterm>Tumor</glossterm> <glossdef> <para>Als Tumor wird zunächst eine raumfordernde Wucherung von Zellen bezeichnet, ein synonymer Ausdruck ist Neoplasie. Dabei gibt es gutartige Tumoren und bösartige. Je nach Ort der Geschwulst und nach Art des verdrängten und geschädigten Gewebes können Krankheiten bis hin zum Tod entstehen. Bösartige Tumoren sind die Ursache von Krebs, bei dem sich ausgehend von den ursprünglichen Tumorzellen weitere Geschwulste (Metatasen) in anderen Körperregionen bilden.</para> </glossdef> </glossentry> <glossentry xml:id="glo.geneticCode" xreflabel="Glo.T Genetischer Code"> <glossterm>Genetischer Code<indexterm> <primary>Genetischer Code</primary> </indexterm></glossterm> <glossdef> <para> <table frame="sides" rowsep="0" colsep="0"> [163 lines] </para> </glossdef> </glossentry> </glossdiv> </glossary> </sect2>
It is this table which made the transformation choke. But only in the context of the book, not in the glossar itself. Can you please explain to me what I do wrong and how to change the behaviour?
I have changed the transformation scenario to:
and are using the following stylesheet:
<?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:d="http://docbook.org/ns/docbook" version="1.0"> <xsl:import href="http://docbook.sourceforge.net/release/xsl-ns/current/fo/docbook.xsl"/> <xsl:param name="caption.align">justify</xsl:param>
<xsl:template match="d:mediaobject/d:caption"> <fo:block role="caption"> <xsl:if test="$caption.align = 'right' or $caption.align = 'left' or $caption.align = 'justify' or $caption.align = 'center'"> <xsl:attribute name="text-align"> <xsl:value-of select="$caption.align"/> </xsl:attribute> </xsl:if> <xsl:apply-templates/> </fo:block> </xsl:template> </xsl:stylesheet>
Regards Bernhard
-- spitzhalde9 D-79853 lenzkirch bernhard.kleine@gmx.net www.b-kleine.com, www.urseetal.net - thunderbird mit enigmail GPG schlüssel: D5257409 fingerprint: 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com https://www.oxygenxml.com/mailman/listinfo/oxygen-user

For the moment I have solved the problem by changing ..\Oxygen XML Editor 20\frameworks\docbook\xsl\fo\docbook_custom.xsl and adding the lines from my customization. This worked. Copying docbook_custom.xsl to the xsl/fo/ subfolder of my project doesnot work since it links to further stylesheets. Having docbook_custom.xsl added as another stylesheet did not work since "cascading stylesheet" did not work. The error I reported has obviously nothing to do with the content of the Buch.xsl stylesheet, but with the customization I have shown to you. I am lost to see the reason for that. Regards Bernhard Am 09.10.2018 um 07:26 schrieb Oxygen XML Editor Support (Radu Coravu):
Hi Bernhard,
If you publish to PDF without your customizations do you obtain the same problem? You will probably have to trim down your DocBook file to a minimum until you have a minimal sample with which the PDF processor problem can be reproduced. Then you can send it over to "support@oxygenxml.com" and we can take a look at it.
Regards, Radu
Radu Coravu <oXygen/> XML Editor http://www.oxygenxml.com
On 10/8/2018 11:02 PM, Bernhard Kleine wrote:
I have analyzed the situation:
When I transform the glossar of my book, transformation is without trouble. However, when transforming the whole book plus the glossar, it stumbles
I then analyzed the glossar: It has seven glossdivs. The last one consists of some 20 glossdefs, of which I show the last ones:
<glossentry xml:id="glo.Tumor"> <glossterm>Tumor</glossterm> <glossdef> <para>Als Tumor wird zunächst eine raumfordernde Wucherung von Zellen bezeichnet, ein synonymer Ausdruck ist Neoplasie. Dabei gibt es gutartige Tumoren und bösartige. Je nach Ort der Geschwulst und nach Art des verdrängten und geschädigten Gewebes können Krankheiten bis hin zum Tod entstehen. Bösartige Tumoren sind die Ursache von Krebs, bei dem sich ausgehend von den ursprünglichen Tumorzellen weitere Geschwulste (Metatasen) in anderen Körperregionen bilden.</para> </glossdef> </glossentry> <glossentry xml:id="glo.geneticCode" xreflabel="Glo.T Genetischer Code"> <glossterm>Genetischer Code<indexterm> <primary>Genetischer Code</primary> </indexterm></glossterm> <glossdef> <para> <table frame="sides" rowsep="0" colsep="0"> [163 lines] </para> </glossdef> </glossentry> </glossdiv> </glossary> </sect2>
It is this table which made the transformation choke. But only in the context of the book, not in the glossar itself. Can you please explain to me what I do wrong and how to change the behaviour?
I have changed the transformation scenario to:
and are using the following stylesheet:
<?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:d="http://docbook.org/ns/docbook" version="1.0"> <xsl:import href="http://docbook.sourceforge.net/release/xsl-ns/current/fo/docbook.xsl"/>
<xsl:param name="caption.align">justify</xsl:param>
<xsl:template match="d:mediaobject/d:caption"> <fo:block role="caption"> <xsl:if test="$caption.align = 'right' or $caption.align = 'left' or $caption.align = 'justify' or $caption.align = 'center'"> <xsl:attribute name="text-align"> <xsl:value-of select="$caption.align"/> </xsl:attribute> </xsl:if> <xsl:apply-templates/> </fo:block> </xsl:template> </xsl:stylesheet>
Regards Bernhard
-- spitzhalde9 D-79853 lenzkirch bernhard.kleine@gmx.net www.b-kleine.com, www.urseetal.net - thunderbird mit enigmail GPG schlüssel: D5257409 fingerprint: 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com https://www.oxygenxml.com/mailman/listinfo/oxygen-user
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com https://www.oxygenxml.com/mailman/listinfo/oxygen-user
-- spitzhalde9 D-79853 lenzkirch bernhard.kleine@gmx.net www.b-kleine.com, www.urseetal.net - thunderbird mit enigmail GPG schlüssel: D5257409 fingerprint: 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09

Hi Bernhard, As I previously said I do not have enough details on my side (the XSL-FO file on which the PDF processor is applied to produce the PDF or a sample Docbook XML + XSLT customization) in order to understand better what's going on. Regards, Radu Radu Coravu <oXygen/> XML Editor http://www.oxygenxml.com On 10/9/2018 1:23 PM, Bernhard Kleine wrote:
For the moment I have solved the problem by changing ..\Oxygen XML Editor 20\frameworks\docbook\xsl\fo\docbook_custom.xsl and adding the lines from my customization. This worked. Copying docbook_custom.xsl to the xsl/fo/ subfolder of my project doesnot work since it links to further stylesheets. Having docbook_custom.xsl added as another stylesheet did not work since "cascading stylesheet" did not work.
The error I reported has obviously nothing to do with the content of the Buch.xsl stylesheet, but with the customization I have shown to you. I am lost to see the reason for that.
Regards
Bernhard
Am 09.10.2018 um 07:26 schrieb Oxygen XML Editor Support (Radu Coravu):
Hi Bernhard,
If you publish to PDF without your customizations do you obtain the same problem? You will probably have to trim down your DocBook file to a minimum until you have a minimal sample with which the PDF processor problem can be reproduced. Then you can send it over to "support@oxygenxml.com" and we can take a look at it.
Regards, Radu
Radu Coravu <oXygen/> XML Editor http://www.oxygenxml.com
On 10/8/2018 11:02 PM, Bernhard Kleine wrote:
I have analyzed the situation:
When I transform the glossar of my book, transformation is without trouble. However, when transforming the whole book plus the glossar, it stumbles
I then analyzed the glossar: It has seven glossdivs. The last one consists of some 20 glossdefs, of which I show the last ones:
<glossentry xml:id="glo.Tumor"> <glossterm>Tumor</glossterm> <glossdef> <para>Als Tumor wird zunächst eine raumfordernde Wucherung von Zellen bezeichnet, ein synonymer Ausdruck ist Neoplasie. Dabei gibt es gutartige Tumoren und bösartige. Je nach Ort der Geschwulst und nach Art des verdrängten und geschädigten Gewebes können Krankheiten bis hin zum Tod entstehen. Bösartige Tumoren sind die Ursache von Krebs, bei dem sich ausgehend von den ursprünglichen Tumorzellen weitere Geschwulste (Metatasen) in anderen Körperregionen bilden.</para> </glossdef> </glossentry> <glossentry xml:id="glo.geneticCode" xreflabel="Glo.T Genetischer Code"> <glossterm>Genetischer Code<indexterm> <primary>Genetischer Code</primary> </indexterm></glossterm> <glossdef> <para> <table frame="sides" rowsep="0" colsep="0"> [163 lines] </para> </glossdef> </glossentry> </glossdiv> </glossary> </sect2>
It is this table which made the transformation choke. But only in the context of the book, not in the glossar itself. Can you please explain to me what I do wrong and how to change the behaviour?
I have changed the transformation scenario to:
and are using the following stylesheet:
<?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:d="http://docbook.org/ns/docbook" version="1.0"> <xsl:import href="http://docbook.sourceforge.net/release/xsl-ns/current/fo/docbook.xsl"/>
<xsl:param name="caption.align">justify</xsl:param>
<xsl:template match="d:mediaobject/d:caption"> <fo:block role="caption"> <xsl:if test="$caption.align = 'right' or $caption.align = 'left' or $caption.align = 'justify' or $caption.align = 'center'"> <xsl:attribute name="text-align"> <xsl:value-of select="$caption.align"/> </xsl:attribute> </xsl:if> <xsl:apply-templates/> </fo:block> </xsl:template> </xsl:stylesheet>
Regards Bernhard
-- spitzhalde9 D-79853 lenzkirch bernhard.kleine@gmx.net www.b-kleine.com, www.urseetal.net - thunderbird mit enigmail GPG schlüssel: D5257409 fingerprint: 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com https://www.oxygenxml.com/mailman/listinfo/oxygen-user
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com https://www.oxygenxml.com/mailman/listinfo/oxygen-user
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com https://www.oxygenxml.com/mailman/listinfo/oxygen-user

Hi Rdu I can understand this. What I find problematic that I can savely transform the 700 pages book when I have changes docbook-custom.xsl, but changing the customization from to renders the transformation faulty. That in my opinion is the problem. It has nothing to do with the modified xls stylesheet. And I am lost how debug this since the error is erratic in my opinion besides fop not giving any log. Regards Bernhard Am 09.10.2018 um 14:44 schrieb Oxygen XML Editor Support (Radu Coravu):
Hi Bernhard,
As I previously said I do not have enough details on my side (the XSL-FO file on which the PDF processor is applied to produce the PDF or a sample Docbook XML + XSLT customization) in order to understand better what's going on.
Regards, Radu
Radu Coravu <oXygen/> XML Editor http://www.oxygenxml.com
On 10/9/2018 1:23 PM, Bernhard Kleine wrote:
For the moment I have solved the problem by changing ..\Oxygen XML Editor 20\frameworks\docbook\xsl\fo\docbook_custom.xsl and adding the lines from my customization. This worked. Copying docbook_custom.xsl to the xsl/fo/ subfolder of my project doesnot work since it links to further stylesheets. Having docbook_custom.xsl added as another stylesheet did not work since "cascading stylesheet" did not work.
The error I reported has obviously nothing to do with the content of the Buch.xsl stylesheet, but with the customization I have shown to you. I am lost to see the reason for that.
Regards
Bernhard
Am 09.10.2018 um 07:26 schrieb Oxygen XML Editor Support (Radu Coravu):
Hi Bernhard,
If you publish to PDF without your customizations do you obtain the same problem? You will probably have to trim down your DocBook file to a minimum until you have a minimal sample with which the PDF processor problem can be reproduced. Then you can send it over to "support@oxygenxml.com" and we can take a look at it.
Regards, Radu
Radu Coravu <oXygen/> XML Editor http://www.oxygenxml.com
On 10/8/2018 11:02 PM, Bernhard Kleine wrote:
I have analyzed the situation:
When I transform the glossar of my book, transformation is without trouble. However, when transforming the whole book plus the glossar, it stumbles
I then analyzed the glossar: It has seven glossdivs. The last one consists of some 20 glossdefs, of which I show the last ones:
<glossentry xml:id="glo.Tumor"> <glossterm>Tumor</glossterm> <glossdef> <para>Als Tumor wird zunächst eine raumfordernde Wucherung von Zellen bezeichnet, ein synonymer Ausdruck ist Neoplasie. Dabei gibt es gutartige Tumoren und bösartige. Je nach Ort der Geschwulst und nach Art des verdrängten und geschädigten Gewebes können Krankheiten bis hin zum Tod entstehen. Bösartige Tumoren sind die Ursache von Krebs, bei dem sich ausgehend von den ursprünglichen Tumorzellen weitere Geschwulste (Metatasen) in anderen Körperregionen bilden.</para> </glossdef> </glossentry> <glossentry xml:id="glo.geneticCode" xreflabel="Glo.T Genetischer Code"> <glossterm>Genetischer Code<indexterm> <primary>Genetischer Code</primary> </indexterm></glossterm> <glossdef> <para> <table frame="sides" rowsep="0" colsep="0"> [163 lines] </para> </glossdef> </glossentry> </glossdiv> </glossary> </sect2>
It is this table which made the transformation choke. But only in the context of the book, not in the glossar itself. Can you please explain to me what I do wrong and how to change the behaviour?
I have changed the transformation scenario to:
and are using the following stylesheet:
<?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:d="http://docbook.org/ns/docbook" version="1.0"> <xsl:import href="http://docbook.sourceforge.net/release/xsl-ns/current/fo/docbook.xsl"/>
<xsl:param name="caption.align">justify</xsl:param>
<xsl:template match="d:mediaobject/d:caption"> <fo:block role="caption"> <xsl:if test="$caption.align = 'right' or $caption.align = 'left' or $caption.align = 'justify' or $caption.align = 'center'"> <xsl:attribute name="text-align"> <xsl:value-of select="$caption.align"/> </xsl:attribute> </xsl:if> <xsl:apply-templates/> </fo:block> </xsl:template> </xsl:stylesheet>
Regards Bernhard
-- spitzhalde9 D-79853 lenzkirch bernhard.kleine@gmx.net www.b-kleine.com, www.urseetal.net - thunderbird mit enigmail GPG schlüssel: D5257409 fingerprint: 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com https://www.oxygenxml.com/mailman/listinfo/oxygen-user
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com https://www.oxygenxml.com/mailman/listinfo/oxygen-user
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com https://www.oxygenxml.com/mailman/listinfo/oxygen-user
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com https://www.oxygenxml.com/mailman/listinfo/oxygen-user
-- spitzhalde9 D-79853 lenzkirch bernhard.kleine@gmx.net www.b-kleine.com, www.urseetal.net - thunderbird mit enigmail GPG schlüssel: D5257409 fingerprint: 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09
participants (3)
-
Bernhard Kleine
-
Imsieke, Gerrit, le-tex
-
Oxygen XML Editor Support (Radu Coravu)