Hi, Indeed we've had problems reported in the past with certain PNGs causing out of memory errors when read with the default Java libraries: https://www.oxygenxml.com/forum/post20919.html Ideally you could identify that particular image which causes the problem and use a free image editing utility like GIMP to open and save it again. Maybe this will fix any problems it may have. Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 2/14/2018 12:25 AM, Eliot Kimber wrote:

From the trace it looks like an issue with a large graphic since the code involves appears to be the PNGImageReader.

So nothing to do with the size of the chapter but to do with the size of an image.

Cheers,

E.

--

Eliot Kimber

http://contrext.com

*From: *oXygen-user <oxygen-user-bounces@oxygenxml.com> on behalf of Bernhard Kleine <bernhard.kleine@gmx.net> *Date: *Tuesday, February 13, 2018 at 3:04 PM *To: *<oxygen-user@oxygenxml.com> *Subject: *[oXygen-user] Strange error while transforming docbook 5 to pdf

Good evening!

I encountered the following error while transforming a chapter of my bool:

The process 'Apache FOP' ended with code: 1.

The error was:

Exception in thread "main" java.lang.OutOfMemoryError: Java heap space

at java.awt.image.DataBufferByte.<init>(Unknown Source)

at java.awt.image.ComponentSampleModel.createDataBuffer(Unknown Source)

at java.awt.image.Raster.createWritableRaster(Unknown Source)

at javax.imageio.ImageTypeSpecifier.createBufferedImage(Unknown Source)

at javax.imageio.ImageReader.getDestination(Unknown Source)

at com.sun.imageio.plugins.png.PNGImageReader.readImage(Unknown Source)

at com.sun.imageio.plugins.png.PNGImageReader.read(Unknown Source)

at org.apache.xmlgraphics.image.loader.impl.imageio.ImageLoaderImageIO.loadImage(ImageLoaderImageIO.java:129)

at org.apache.xmlgraphics.image.loader.pipeline.ImageProviderPipeline.execute(ImageProviderPipeline.java:154)

at org.apache.xmlgraphics.image.loader.pipeline.ImageProviderPipeline.execute(ImageProviderPipeline.java:99)

at org.apache.xmlgraphics.image.loader.ImageManager.getImage(ImageManager.java:269)

at org.apache.fop.render.intermediate.AbstractIFPainter.drawImageUsingImageHandler(AbstractIFPainter.java:159)

at org.apache.fop.render.pdf.PDFPainter.drawImageUsingURI(PDFPainter.java:218)

at org.apache.fop.render.pdf.PDFPainter.drawImage(PDFPainter.java:181)

at org.apache.fop.render.intermediate.IFRenderer.drawImage(IFRenderer.java:1294)

at org.apache.fop.render.intermediate.IFRenderer.renderImage(IFRenderer.java:1281)

at org.apache.fop.render.AbstractRenderer.renderInlineViewport(AbstractRenderer.java:858)

at org.apache.fop.render.AbstractPathOrientedRenderer.renderInlineViewport(AbstractPathOrientedRenderer.java:832)

at org.apache.fop.render.intermediate.IFRenderer.renderInlineViewport(IFRenderer.java:862)

at org.apache.fop.render.AbstractRenderer.renderInlineArea(AbstractRenderer.java:715)

at org.apache.fop.render.intermediate.IFRenderer.renderInlineArea(IFRenderer.java:926)

at org.apache.fop.render.AbstractRenderer.renderLineArea(AbstractRenderer.java:690)

at org.apache.fop.render.AbstractRenderer.renderBlocks(AbstractRenderer.java:572)

at org.apache.fop.render.AbstractRenderer.renderBlock(AbstractRenderer.java:613)

at org.apache.fop.render.intermediate.IFRenderer.renderBlock(IFRenderer.java:998)

at org.apache.fop.render.AbstractRenderer.renderBlocks(AbstractRenderer.java:557)

at org.apache.fop.render.AbstractRenderer.renderBlock(AbstractRenderer.java:613)

at org.apache.fop.render.intermediate.IFRenderer.renderBlock(IFRenderer.java:998)

at org.apache.fop.render.AbstractRenderer.renderBlocks(AbstractRenderer.java:557)

at org.apache.fop.render.AbstractRenderer.renderBlock(AbstractRenderer.java:613)

at org.apache.fop.render.intermediate.IFRenderer.renderBlock(IFRenderer.java:998)

at org.apache.fop.render.AbstractRenderer.renderBlocks(AbstractRenderer.java:557)

Specify more memory for the 'Apache FOP' as explained in the section 'Performance Problems', subsection 'External Processes' in the User Manual.

Since it is not the largest chapter and those larger ones could be transformed without any problem, I ask for any help or ideas to tackle the problem.

Regards Bernhard

--

spitzhalde9

D-79853 lenzkirch

bernhard.kleine@gmx.net<mailto:bernhard.kleine@gmx.net>

www.b-kleine.com<http://www.b-kleine.com>, www.urseetal.net<http://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

I found a culprit: Opening the file in GIMP, scaling it down and saving, allowed compilation of the chapter. Thanks for your help and suggestions. 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, We need more info. If you have a sample Docbook document to test with, please send it to us (support@oxygenxml.com) and we can take a look at it. Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 2/14/2018 3:39 PM, Bernhard Kleine wrote:

Compiling the glossary gives:

...

Processing terminated by xsl:message at line 164

The glossary itself around line looks as shown:

-- 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

Hi Bernhard, Usually Oxygen tries to pick up the problems reported by Apache Fop and report them in a better manner, but without reproducing the problem on my side I am unable to investigate further. If you look at the error you receive, at some point it has something like:

file:/K:/BuchprojektSpringer/VierteAuflageXmlDeutsch/Lehrbuch.xml_xslt:5447:5425

That "5447:5425" part means line 5447 and column "5425". The file "Lehrbuch.xml_xslt" is automatically created by Oxygen by applying the XSLT over the XML and then automatically deleted at the end of the transformation. But you can create another transformation scenario (or duplicate the current one), choose in the "FO Processors" tab not to perform FO processing and in the output tab to save the file as "result.fo" for example. This will allow you to look at what the "result.fo" contains, open it up and look at a certain line and column. After you open the "result.fo" the "Configure Transformation Scenarios" dialog should contain a "FO PDF" transformation scenario allowing you to create a PDF out of it. Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 2/14/2018 4:14 PM, Bernhard Kleine wrote:

I have successfully transformed all the different chapters of the book and the appendix. Still when transforming the entire book I get two errors. The one about png as before and

...

ERROR - Invalid property value encountered in text-align="char": org.apache.fop.fo.expr.PropertyException: file:/K:/BuchprojektSpringer/VierteAuflageXmlDeutsch/Lehrbuch.xml_xslt:5447:5425: No conversion defined char; property:'text-align' (Siehe Position 5447:5557) org.apache.fop.fo.expr.PropertyException: file:/K:/BuchprojektSpringer/VierteAuflageXmlDeutsch/Lehrbuch.xml_xslt:5447:5425: No conversion defined char; property:'text-align' at org.apache.fop.fo.properties.PropertyMaker.make(PropertyMaker.java:446) at org.apache.fop.fo.PropertyList.convertAttributeToProperty(PropertyList.java:499) at org.apache.fop.fo.PropertyList.addAttributesToList(PropertyList.java:386) at org.apache.fop.fo.FObj.processNode(FObj.java:124) at org.apache.fop.fo.flow.table.TableFObj.processNode(TableFObj.java:232) at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.startElement(FOTreeBuilder.java:291) at org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:179) at net.sf.saxon.event.ContentHandlerProxy.startContent(Unknown Source) at net.sf.saxon.event.NamespaceReducer.startContent(NamespaceReducer.java:216) at net.sf.saxon.event.ComplexContentOutputter.startContent(ComplexContentOutputter.java:714) at net.sf.saxon.event.ReceivingContentHandler.startElement(ReceivingContentHandler.java:370) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(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:451) at net.sf.saxon.event.Sender.send(Sender.java:153) at net.sf.saxon.jaxp.IdentityTransformer.transform(IdentityTransformer.java:375) 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)

BTW I would accept these error messages when they could point to the place they occur. The way it is now is totally unhelpfull, from the stone age of computing like MS Windows 3.1 error messages!

--

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