DO NOT REPLY [Bug 48063] fop hangs, 100% cpu usage while rendering pdf
https://issues.apache.org/bugzilla/show_bug.cgi?id=48063 Karel Vervaeke karel.verva...@telenet.be changed: What|Removed |Added CC||br...@outerthought.org -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 43808] Apache FOP in a Servlet fails to work after upgrade to 0.94
https://issues.apache.org/bugzilla/show_bug.cgi?id=43808 Gerard Brouwer ger...@xsarus.nl changed: What|Removed |Added CC||ger...@xsarus.nl -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 48076] New: NPE when rendering a file containing a non-base14 font to IF XML then to PDF
https://issues.apache.org/bugzilla/show_bug.cgi?id=48076 Summary: NPE when rendering a file containing a non-base14 font to IF XML then to PDF Product: Fop Version: all Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: general AssignedTo: fop-dev@xmlgraphics.apache.org ReportedBy: vhenneb...@gmail.com Created an attachment (id=24435) -- (https://issues.apache.org/bugzilla/attachment.cgi?id=24435) FO file triggering the exception See attachments. Files should be placed at the root of a FOP copy. To reproduce: fop -c config.xconf non-standard-font -if application/pdf if.xml fop -c config.xconf -ifin if.xml non-standard-font.pdf You get the following exception: java.lang.NullPointerException: fontName must not be null at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:302) at org.apache.fop.cli.IFInputHandler.renderTo(IFInputHandler.java:77) at org.apache.fop.cli.Main.startFOP(Main.java:174) at org.apache.fop.cli.Main.main(Main.java:205) Caused by: java.lang.NullPointerException: fontName must not be null at org.apache.fop.render.pdf.PDFPainter.getTypeface(PDFPainter.java:285) at org.apache.fop.render.pdf.PDFPainter.drawText(PDFPainter.java:320) at org.apache.fop.render.intermediate.IFParser$Handler$TextHandler.endElement(IFParser.java:569) at org.apache.fop.render.intermediate.IFParser$Handler.endElement(IFParser.java:352) at org.apache.xalan.transformer.TransformerIdentityImpl.endElement(TransformerIdentityImpl.java:1101) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.endElement(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 org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:484) at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:299) ... 3 more -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 48076] NPE when rendering a file containing a non-base14 font to IF XML then to PDF
https://issues.apache.org/bugzilla/show_bug.cgi?id=48076 --- Comment #1 from Vincent Hennebert vhenneb...@gmail.com 2009-10-28 09:44:33 UTC --- Created an attachment (id=24436) -- (https://issues.apache.org/bugzilla/attachment.cgi?id=24436) Font configuration file -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 48077] Values in PDF Number Trees must be indirect references
https://issues.apache.org/bugzilla/show_bug.cgi?id=48077 --- Comment #1 from Vincent Hennebert vhenneb...@gmail.com 2009-10-28 09:59:16 UTC --- Created an attachment (id=24438) -- (https://issues.apache.org/bugzilla/attachment.cgi?id=24438) The resulting PDF. See object 9 0 -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
Re: svn commit: r830476 - in /xmlgraphics/fop/trunk/src/java: META-INF/services/org.apache.fop.events.model.EventModelFactory org/apache/fop/accessibility/AccessibilityEventProducer.java
On Wed, Oct 28, 2009 at 12:07:20PM +, Vincent Hennebert wrote: Jeremias Maerki wrote: http://xmlgraphics.apache.org/fop/trunk/events.html#event-model For a given application, there can be multiple event models active at the same time. In FOP, each renderer is considered to be a plug-in and provides its own specific event model. The individual event models are provided through an EventModelFactory. This interface is implemented for each event model and registered through the service provider mechanism (see the plug-ins section for details). Ok. Maybe that???s just me, but after reading that section, I still fail to understand what an ???event object model??? is. And since that section starts by explaining implementation details (names of parameters not provided by the JVM, need of QDox), I???m inclined to skip it all. After all, I???m not a developer, but a user of the library. And http://xmlgraphics.apache.org/fop/trunk/events.html#plug-ins That section starts with ???The event subsystem is extensible.??? I don???t want to extend it, I just want to use it! And nowhere is it written that something must also be added to the build file. This is all confusing. I agree with the observation that the documentation is not well suited to FOP developers who want to add events. I would like to see a 'howto add one or more events' document. The documentation page on the web site http://xmlgraphics.apache.org/fop/trunk/events.html stops too early. For me it was about sufficient, but only because I decided to reuse one of the event producers and added my message to the catch all EventFormatter.xml file. Even so, I had problems getting my event file rebuilt. Preferably the documentation page has a short and a longer writeup, without an explanation of the philosophy. It would probably also be good to have such a document for those who want to extend the system. Until now we were saved by the fact that Jeremias is around to check our actions, but we should be able to add events even without him, and we are not yet there. Simon -- Simon Pepping home page: http://www.leverkruid.eu
