DO NOT REPLY [Bug 47711] [PATCH] Wrong CIDSet when embedding CID font subset in a PDF.
https://issues.apache.org/bugzilla/show_bug.cgi?id=47711 Jeremias Maerki jerem...@apache.org changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #1 from Jeremias Maerki jerem...@apache.org 2009-10-22 02:18:10 UTC --- Applied. Thanks a lot for catching that and sorry for the delay processing the patch. http://svn.apache.org/viewvc?rev=828516view=rev -- 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: OutOfMemoryError on IntermediateFormatTestSuite
Hmm, what did you change? I'm sorry but I've never seen that exception before. My question remains open: what JVM are you using? Something is still not right. On 22.10.2009 14:39:38 DELCROIX Guillaume wrote: It works ! Thanks Jeremias. Now I've got a SAXParserException : [junit] Testcase: filename.xml(org.apache.fop.intermediate.IntermediateFormatTestSuite$1): Caused an ERROR [junit] src-resolve: Cannot resolve the name 'xml:space' to a(n) 'attribute declaration' component. [junit] org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name 'xml:space' to a(n) 'attribute declaration' component. It seems to be a xerces problem but I don't work if there is a workaround or a particular setting to do ? Guillaume -Message d'origine- De : Jeremias Maerki [mailto:d...@jeremias-maerki.ch] Envoyé : jeudi 22 octobre 2009 12:13 À : fop-dev@xmlgraphics.apache.org Objet : Re: OutOfMemoryError on IntermediateFormatTestSuite No, the latest FOP Trunk runs through just fine for me. You could run with -XX:+HeapDumpOnOutOfMemoryError and then analyze the heap dump to identify what eats so much memory. My usual ANT_OPTS: ANT_OPTS=-Xmx512M -XX:MaxPermSize=128M But I've also just run this at default settings (max 64M heap) and it ran through just fine. What JVM are you using? On 19.10.2009 15:27:44 DELCROIX Guillaume wrote: Thanks Jeremias. When I try with -Xmx1024m, I have exactly the same problem. After about 3 hours of test, the OutOfMemoryError is raised. Do you have the same result ? If you reproduce this behaviour, do you know the last revision ID passing all tests ? Guillaume -Message d'origine- De : Jeremias Maerki [mailto:d...@jeremias-maerki.ch] Envoyé : dimanche 18 octobre 2009 17:34 À : fop-dev@xmlgraphics.apache.org Objet : Re: OutOfMemoryError on IntermediateFormatTestSuite Hi Guillaume No, that happens to me, too. I believe it's because of the TrueType fonts that are loaded into memory that the default 64MB are not sufficient. Just increase the heap size (-Xmx256M). On 16.10.2009 16:11:16 DELCROIX Guillaume wrote: Hi, I've got an OutOfMemoryError running IntermediateFormatTestSuite on the FOP trunk ( Rev ID : 825646 ) junit-intermediate-format: [echo] Running intermediate format tests... [junit] Testsuite: org.apache.fop.intermediate.IntermediateFormatTestSuite [junit] Exception in thread main java.lang.OutOfMemoryError: Java heap space [junit] Test org.apache.fop.intermediate.IntermediateFormatTestSuite FAILED (crashed) All others test suites are Ok ... Is there something special for this test suite ? Am I the only one to have this error ? What is the last revision ID which pass all tests ? Jeremias Maerki Jeremias Maerki Jeremias Maerki
DO NOT REPLY [Bug 47941] AFP Renderer Truncates TLE Values
https://issues.apache.org/bugzilla/show_bug.cgi?id=47941 Adrian Cumiskey d...@cumiskey.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #9 from Adrian Cumiskey d...@cumiskey.com 2009-10-22 06:21:17 UTC --- This bug was originally misdiagnosed. The TLE values were not being truncated as Chris suggested. As I see it, Harald is correct in his description of the issue. Triplets are a maximum of 254 bytes, therefore Attribute Value Triplets can legally hold a maximum of 250 bytes including the header. So the solution as I see it is that the value must be truncated to 250 characters and a warning provided. I have now resolved this in trunk. Adrian. -- 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 47941] AFP Renderer Truncates TLE Values
https://issues.apache.org/bugzilla/show_bug.cgi?id=47941 --- Comment #10 from Chris Bowditch bowditch_ch...@hotmail.com 2009-10-22 08:01:43 UTC --- Thanks for the fix Adrian. You are correct that my original report wasn't technically accurate but then I didn't have time to look into the details. Still I am happy with the final resolution. -- 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: OutOfMemoryError on IntermediateFormatTestSuite
I work with JVM 1.6.0_01 Guillaume -Message d'origine- De : Jeremias Maerki [mailto:d...@jeremias-maerki.ch] Envoyé : jeudi 22 octobre 2009 15:01 À : fop-dev@xmlgraphics.apache.org Objet : Re: OutOfMemoryError on IntermediateFormatTestSuite Hmm, what did you change? I'm sorry but I've never seen that exception before. My question remains open: what JVM are you using? Something is still not right. On 22.10.2009 14:39:38 DELCROIX Guillaume wrote: It works ! Thanks Jeremias. Now I've got a SAXParserException : [junit] Testcase: filename.xml(org.apache.fop.intermediate.IntermediateFormatTestSuite$1): Caused an ERROR [junit] src-resolve: Cannot resolve the name 'xml:space' to a(n) 'attribute declaration' component. [junit] org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name 'xml:space' to a(n) 'attribute declaration' component. It seems to be a xerces problem but I don't work if there is a workaround or a particular setting to do ? Guillaume -Message d'origine- De : Jeremias Maerki [mailto:d...@jeremias-maerki.ch] Envoyé : jeudi 22 octobre 2009 12:13 À : fop-dev@xmlgraphics.apache.org Objet : Re: OutOfMemoryError on IntermediateFormatTestSuite No, the latest FOP Trunk runs through just fine for me. You could run with -XX:+HeapDumpOnOutOfMemoryError and then analyze the heap dump to identify what eats so much memory. My usual ANT_OPTS: ANT_OPTS=-Xmx512M -XX:MaxPermSize=128M But I've also just run this at default settings (max 64M heap) and it ran through just fine. What JVM are you using? On 19.10.2009 15:27:44 DELCROIX Guillaume wrote: Thanks Jeremias. When I try with -Xmx1024m, I have exactly the same problem. After about 3 hours of test, the OutOfMemoryError is raised. Do you have the same result ? If you reproduce this behaviour, do you know the last revision ID passing all tests ? Guillaume -Message d'origine- De : Jeremias Maerki [mailto:d...@jeremias-maerki.ch] Envoyé : dimanche 18 octobre 2009 17:34 À : fop-dev@xmlgraphics.apache.org Objet : Re: OutOfMemoryError on IntermediateFormatTestSuite Hi Guillaume No, that happens to me, too. I believe it's because of the TrueType fonts that are loaded into memory that the default 64MB are not sufficient. Just increase the heap size (-Xmx256M). On 16.10.2009 16:11:16 DELCROIX Guillaume wrote: Hi, I've got an OutOfMemoryError running IntermediateFormatTestSuite on the FOP trunk ( Rev ID : 825646 ) junit-intermediate-format: [echo] Running intermediate format tests... [junit] Testsuite: org.apache.fop.intermediate.IntermediateFormatTestSuite [junit] Exception in thread main java.lang.OutOfMemoryError: Java heap space [junit] Test org.apache.fop.intermediate.IntermediateFormatTestSuite FAILED (crashed) All others test suites are Ok ... Is there something special for this test suite ? Am I the only one to have this error ? What is the last revision ID which pass all tests ? Jeremias Maerki Jeremias Maerki Jeremias Maerki
DO NOT REPLY [Bug 42808] table footer overflows region-body area without warnings
https://issues.apache.org/bugzilla/show_bug.cgi?id=42808 --- Comment #2 from Jonathan Levinson levin...@intersystems.com 2009-10-22 09:13:49 UTC --- I tried this with FOP 0.95 and it looks fixed. The table footer remains in blue area which is region body. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
Generation of *EventProducer.xml [was: Re: svn commit: r828747...]
Hi, Log: Issue an error when attempting to render an intermediate XML file in accessibility mode, but that file wasn't generated with accessibility (i.e., does not contain the structure tree) Added: xmlgraphics/fop/branches/Temp_Accessibility/src/java/org/apache/fop/accessibility/AccessibilityEventProducer.java (with props) xmlgraphics/fop/branches/Temp_Accessibility/src/java/org/apache/fop/accessibility/AccessibilityEventProducer.xml (with props) After creating the AccessibilityEventProducer.xml file and running ‘ant resourcegen’ I discovered that an empty message had been added to src/java/org/apache/fop/events/EventFormatter.xml. Why? Also, after re-building FOP I regularly find myself with modified *EventProducer.xml files, where the sole modification is an added/removed line break. This is annoying. How can that be avoided? Thanks, Vincent
Re: OutOfMemoryError on IntermediateFormatTestSuite
So that is most probably a Sun JVM, although an older version. You might want to upgrade your JVM because that version had a number of issues. But I'm not sure that it explains what you're seeing here. At any rate, it must have something to do with XML parsing, so maybe, if updating the JVM doesn't help, I'd explicitely switch to the latest Xerces-J release (copy to jre/lib/endorsed) to see if that changes anything. You could also try a Sun Java 1.4 or 1.5 to see if anything changes. A bit difficult to help here if I can't reproduce what you're seeing. On 22.10.2009 17:11:48 DELCROIX Guillaume wrote: I work with JVM 1.6.0_01 Guillaume -Message d'origine- De : Jeremias Maerki [mailto:d...@jeremias-maerki.ch] Envoyé : jeudi 22 octobre 2009 15:01 À : fop-dev@xmlgraphics.apache.org Objet : Re: OutOfMemoryError on IntermediateFormatTestSuite Hmm, what did you change? I'm sorry but I've never seen that exception before. My question remains open: what JVM are you using? Something is still not right. On 22.10.2009 14:39:38 DELCROIX Guillaume wrote: It works ! Thanks Jeremias. Now I've got a SAXParserException : [junit] Testcase: filename.xml(org.apache.fop.intermediate.IntermediateFormatTestSuite$1): Caused an ERROR [junit] src-resolve: Cannot resolve the name 'xml:space' to a(n) 'attribute declaration' component. [junit] org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name 'xml:space' to a(n) 'attribute declaration' component. It seems to be a xerces problem but I don't work if there is a workaround or a particular setting to do ? Guillaume -Message d'origine- De : Jeremias Maerki [mailto:d...@jeremias-maerki.ch] Envoyé : jeudi 22 octobre 2009 12:13 À : fop-dev@xmlgraphics.apache.org Objet : Re: OutOfMemoryError on IntermediateFormatTestSuite No, the latest FOP Trunk runs through just fine for me. You could run with -XX:+HeapDumpOnOutOfMemoryError and then analyze the heap dump to identify what eats so much memory. My usual ANT_OPTS: ANT_OPTS=-Xmx512M -XX:MaxPermSize=128M But I've also just run this at default settings (max 64M heap) and it ran through just fine. What JVM are you using? On 19.10.2009 15:27:44 DELCROIX Guillaume wrote: Thanks Jeremias. When I try with -Xmx1024m, I have exactly the same problem. After about 3 hours of test, the OutOfMemoryError is raised. Do you have the same result ? If you reproduce this behaviour, do you know the last revision ID passing all tests ? Guillaume -Message d'origine- De : Jeremias Maerki [mailto:d...@jeremias-maerki.ch] Envoyé : dimanche 18 octobre 2009 17:34 À : fop-dev@xmlgraphics.apache.org Objet : Re: OutOfMemoryError on IntermediateFormatTestSuite Hi Guillaume No, that happens to me, too. I believe it's because of the TrueType fonts that are loaded into memory that the default 64MB are not sufficient. Just increase the heap size (-Xmx256M). On 16.10.2009 16:11:16 DELCROIX Guillaume wrote: Hi, I've got an OutOfMemoryError running IntermediateFormatTestSuite on the FOP trunk ( Rev ID : 825646 ) junit-intermediate-format: [echo] Running intermediate format tests... [junit] Testsuite: org.apache.fop.intermediate.IntermediateFormatTestSuite [junit] Exception in thread main java.lang.OutOfMemoryError: Java heap space [junit] Test org.apache.fop.intermediate.IntermediateFormatTestSuite FAILED (crashed) All others test suites are Ok ... Is there something special for this test suite ? Am I the only one to have this error ? What is the last revision ID which pass all tests ? Jeremias Maerki Jeremias Maerki Jeremias Maerki Jeremias Maerki
Re: [VOTE] Merge the Temp_Accessibility Branch Back to Trunk
I followed what you did in the branch and I like it, although I can't really follow why accessibility needed to be backported to the old PDFRenderer. So entirely +1 from me. And thanks for diving into this. It's good to know that this knowledge has a broader foundation in the project. And of course, FOP gets exciting new functionality. On 22.10.2009 18:12:00 Vincent Hennebert wrote: Hi, Work on PDF accessibility is basically done. There are still some tests to perform and maybe a few tweaks here and there, but the main functionality is in place. So Iâd like to start a vote for merging the branch back to the Trunk: https://svn.eu.apache.org/repos/asf/xmlgraphics/fop/branches/Temp_Accessibility The vote will last the usual 3 days but, since itâs a non-trivial new feature, if any committer would like more time to review it, feel free to say so and we can extend the vote to 1 week. Attached is the diff between the branch and the Trunk, if this is of any help. +1 from me. Thanks, Vincent Jeremias Maerki
Re: Generation of *EventProducer.xml [was: Re: svn commit: r828747...]
On 22.10.2009 19:36:14 Vincent Hennebert wrote: Hi, Log: Issue an error when attempting to render an intermediate XML file in accessibility mode, but that file wasn't generated with accessibility (i.e., does not contain the structure tree) Added: xmlgraphics/fop/branches/Temp_Accessibility/src/java/org/apache/fop/accessibility/AccessibilityEventProducer.java (with props) xmlgraphics/fop/branches/Temp_Accessibility/src/java/org/apache/fop/accessibility/AccessibilityEventProducer.xml (with props) After creating the AccessibilityEventProducer.xml file and running ‘ant resourcegen’ I discovered that an empty message had been added to src/java/org/apache/fop/events/EventFormatter.xml. Why? Because the new files wasn't reflected in the build. All events not specifically directed into a special file go into the catch-all file in the events package. I've updated the build accordingly: http://svn.apache.org/viewvc?rev=828805view=rev Also, after re-building FOP I regularly find myself with modified *EventProducer.xml files, where the sole modification is an added/removed line break. This is annoying. How can that be avoided? These are small differences in behaviour of XML serializers. I guess if that is so annoying, we'd have to make sure we always use the same serializer (make version) somehow. We could also experiment with removing the XML declaration [1] at the beginning of the file. That might get rid of the problem but that's not for sure. I've stumbled over this myself a number of times but found it to be only a minor nuisance which is why I didn't do anything about it. [1] http://java.sun.com/j2se/1.4.2/docs/api/javax/xml/transform/OutputKeys.html#OMIT_XML_DECLARATION Jeremias Maerki
DO NOT REPLY [Bug 48013] Image processing makes FOP really slow
https://issues.apache.org/bugzilla/show_bug.cgi?id=48013 --- Comment #4 from Jonathan Levinson levin...@intersystems.com 2009-10-22 11:59:13 UTC --- Fixed in patch. http://svn.apache.org/viewvc?rev=828814view=rev -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
Event system
Producing and sending an event is simple enough. But why should I go through the dynamic proxy, with an EventProducer interface and event model, instead of simply produce and send the event? This is the part that makes producing and sending a new type of event difficult to understand for me. Simon -- Simon Pepping home page: http://www.leverkruid.eu
Re: [VOTE] Merge the Temp_Accessibility Branch Back to Trunk
On Thu, Oct 22, 2009 at 05:12:00PM +0100, Vincent Hennebert wrote: Hi, Work on PDF accessibility is basically done. There are still some tests to perform and maybe a few tweaks here and there, but the main functionality is in place. So I???d like to start a vote for merging the branch back to the Trunk: https://svn.eu.apache.org/repos/asf/xmlgraphics/fop/branches/Temp_Accessibility Can you summarize what the branch tries to achieve? The vote will last the usual 3 days but, since it???s a non-trivial new feature, if any committer would like more time to review it, feel free to say so and we can extend the vote to 1 week. Can you make that 3 working days? Simon -- Simon Pepping home page: http://www.leverkruid.eu
Re: Event system
http://wiki.apache.org/xmlgraphics-fop/ProcessingFeedback is from the design phase and lists the reasons: - type safety - check mechanism to detect missing translations - check mechanism to make sure all necessary parameters are really dealt with, especially when calling the same event from multiple places. I concede that overall the whole thing might look complex, but the end result makes for quite clean code on the message production side. Adding a new event isn't a big deal at all: 1. Add a new method to the EventProducer interface 2. Run the resourcegen task to update the model and translations 3. Fill in the translation I believe the whole thing worked out quite nicely. Only recently did I have a chance to make use of the event subsystem on a project where I needed to detect certain layout problems. That was easily done and works nicely. I sometimes think this whole mechanism would even warrant it own Apache Commons subproject. Design discussions: http://markmail.org/thread/bkfrub4334pcmrjd HTH On 22.10.2009 21:12:38 Simon Pepping wrote: Producing and sending an event is simple enough. But why should I go through the dynamic proxy, with an EventProducer interface and event model, instead of simply produce and send the event? This is the part that makes producing and sending a new type of event difficult to understand for me. Simon -- Simon Pepping home page: http://www.leverkruid.eu Jeremias Maerki
Re: [VOTE] Merge the Temp_Accessibility Branch Back to Trunk
On 22.10.2009 21:15:40 Simon Pepping wrote: On Thu, Oct 22, 2009 at 05:12:00PM +0100, Vincent Hennebert wrote: Hi, Work on PDF accessibility is basically done. There are still some tests to perform and maybe a few tweaks here and there, but the main functionality is in place. So I???d like to start a vote for merging the branch back to the Trunk: https://svn.eu.apache.org/repos/asf/xmlgraphics/fop/branches/Temp_Accessibility Can you summarize what the branch tries to achieve? I'll try. In short: it provides the Tagged PDF feature that some people have always wanted. Long story: Without the accessibility/document structure feature, FOP simply produces pages with visual content. Visually impaired people need tools like a screen reader to read document to them. For that the reader needs to know which parts of a page are important and which are not, and in which order the elements should be read. It needs to know that a sentence continues on the next page without stumbling over the page footer in the middle of the sentence. An image tells a blind person nothing, so it needs a descriptive text that the screen reader will read aloud in place of the image. There are laws in various countries that require certain organizations to produce barrier-free documents. The accessibility branches' main purpose is just to help with these requirements. PDF is the only format we support that has such features. If FOP implemented PDFXML or XPS, we could later support accessibility there, too, based on the work started here. There's another side-effect to tagged PDF: It allows for better text extraction from the document. PDF even describes ways to make round-trips from XML - PDF - XML - PDF if certain conditions were met. However, we don't do that. Finally, with tagged PDF it is possible to create PDF/A-1a conformant documents in addition to the PDF/A-1b that we already support. That's important for long-term archival of documents. The vote will last the usual 3 days but, since it???s a non-trivial new feature, if any committer would like more time to review it, feel free to say so and we can extend the vote to 1 week. Can you make that 3 working days? Does that imply you don't work 7 days a week? ;-) Working days are what we usually apply here, don't we? Simon -- Simon Pepping home page: http://www.leverkruid.eu Jeremias Maerki
Re: [VOTE] Merge the Temp_Accessibility Branch Back to Trunk
Sounds like a lofty and honorable goal. +1 from me. Clay -- the.webmaes...@gmail.com - http://ourlil.com/ My religion is simple. My religion is kindness. - HH The 14th Dalai Lama of Tibet
