gmane.text.xml.fop.devel

DO NOT REPLY [Bug 46319] New: OutOfMemoryError after generating several thousand pdfs

2008-12-01T22:40:04

https://issues.apache.org/bugzilla/show_bug.cgi?id=46319 Summary: OutOfMemoryError after generating several thousand pdfs Product: Fop Version: 0.95 Platform: Other OS/Version: Linux Status: NEW Severity: critical Priority: P1 Component: pdf AssignedTo: fop-dev< at >xmlgraphics.apache.org ReportedBy: adrian.meyer< at >crealogix.com After upgrading from fop 0.20.5 to fop 0.95 our web application crashes after generating about 15000 small size pdfs (max. 1-12 pages) with the following exception: (number of bytes varies) Exception java.lang.OutOfMemoryError: requested 65536000 bytes for GrET* in /BUILD_AREA/jdk1.5.0_10/hotspot/src/share/vm/utilities/growableArray.cpp. Out of swap space? Before crashing used heap and process memory are growing slowly but continously. (USER_MEM_ARGS="-Xmx3072m -XX:PermSize=128m") We already tried using newest xalan/xerces libraries (from 2.7.1 xalan distribution) and also appli

DO NOT REPLY [Bug 46315] New: fox:needs-balancing extension

2008-12-01T10:36:44

https://issues.apache.org/bugzilla/show_bug.cgi?id=46315 Summary: fox:needs-balancing extension Product: Fop Version: 1.0dev Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: general AssignedTo: fop-dev< at >xmlgraphics.apache.org ReportedBy: gd< at >geneon.de This is how far I got (if the attachment is correct): Parameter value is transfered from fo:flow to Flow. Parameter value is transfered from fo:block to Block. Parameter is inherited from Flow if not specified in Block. Parameter value is used in LayoutContext. Open issues: How and where do I transfer the parameter value from Block to LayoutContext?

Bug report for Fop [2008/11/30]

2008-12-01T07:08:11

+---------------------------------------------------------------------------+ | Bugzilla Bug ID | | +---------------------------------------------------------------------+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned | | | OPN=Reopened VER=Verified (Skipped Closed/Resolved) | | | +-----------------------------------------------------------------+ | | | Severity: BLK=Blocker CRI=Critical REG=Regression MAJ=Major | | | | MIN=Minor NOR=Normal ENH=Enhancement TRV=Trivial | | | | +-------------------------------------------------------------+ | | | | Date Posted | | | | | +--------------------------------------------------+ | | | | | Description | | | | | | | | 1063|Ne

DO NOT REPLY [Bug 46294] New: start-indent on list-item is not correctly handled

2008-11-25T16:46:02

https://issues.apache.org/bugzilla/show_bug.cgi?id=46294 Summary: start-indent on list-item is not correctly handled Product: Fop Version: 0.95 Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: pdf AssignedTo: fop-dev< at >xmlgraphics.apache.org ReportedBy: bowditch_chris< at >hotmail.com I stumbled across a bug in the PDF Renderer (may also affect other layout engine based renderers - I haven't checked, but doesn't affect RTFHandler) whilst testing a patch for bug 42437. I have attached the test FO to this bug. The problem is that the list-body within this FO use body-start() function to control indentation of body, but label is dependent on list-item indentation, since label start-indent is not set. The spec defines the body-start() function based on the indentation of list-block and doesn't take the indentation of list-item into account. Therefore the correct resul

DO NOT REPLY [Bug 46292] New: [PATCH] PS Renderer does not handle a string value for a key in a dictionary.

2008-11-25T14:19:27

https://issues.apache.org/bugzilla/show_bug.cgi?id=46292 Summary: [PATCH] PS Renderer does not handle a string value for a key in a dictionary. Product: Fop Version: all Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: ps AssignedTo: fop-dev< at >xmlgraphics.apache.org ReportedBy: kunhart< at >kadel.cz Created an attachment (id=22943) --> (https://issues.apache.org/bugzilla/attachment.cgi?id=22943) patch for class PSDictionary There is no possibility to assign a string value for a key in a dictionary. E.g.: It is needed for example if you want to choose a concrete output tray in the output PS file: /OutputType (FACE UP BIN) This patch should solve it.

DO NOT REPLY [Bug 46278] New: AFP Renderer doesn't handle fixed with spaces, e.g. thin space

2008-11-24T14:09:48

https://issues.apache.org/bugzilla/show_bug.cgi?id=46278 Summary: AFP Renderer doesn't handle fixed with spaces, e.g. thin space Product: Fop Version: 0.95 Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P4 Component: general AssignedTo: fop-dev< at >xmlgraphics.apache.org ReportedBy: bowditch_chris< at >hotmail.com Created an attachment (id=22925) --> (https://issues.apache.org/bugzilla/attachment.cgi?id=22925) AFP File This effect is illustrated by the FO in the layout engine test case block_white-space_4. I have attached the AFP File generated and the PDF for comparison.

[VOTE] Merge Temp_AFPGOCAResources branch into trunk

Adrian Cumiskey — 2008-11-24T14:08:23

Hi all, I would like to call for a merge of the AFP branch [1] back into trunk. This branch [1] contains a major rewrite of pretty much all the original AFP code. The majority of the AFP code is now homed in its own package separate from the renderer code in org.apache.fop.afp. The AFPRenderer itself is now only sone 800 or so lines long down from the previous 1800+ lines and now more properly extends the AbstractPathOrientedRenderer. There is also now much more shared code now betweeen the PDF and AFP renderers. Major new functionality in the branch includes :- * An AFPGraphics2D implementation which provides the ability to use Batik to drive the production of AFP Graphics (GOCA) output from SVG. * Resource group leveling, external streaming and de-duplication of images and graphics using IncludeObject and ResourceGroup. * Native image embedding support (e.g. JPEG, GIF, TIFF) using ObjectContainer and a MOD:CA Registry implementation. * More robust AFP font parsing, although this is still in need of

DO NOT REPLY [Bug 46277] New: RTF - Block elements with id but without other content shouldn't create a paragraph

2008-11-24T14:01:06

https://issues.apache.org/bugzilla/show_bug.cgi?id=46277 Summary: RTF - Block elements with id but without other content shouldn't create a paragraph Product: Fop Version: 0.95 Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: rtf AssignedTo: fop-dev< at >xmlgraphics.apache.org ReportedBy: maximilian.aster< at >boc-eu.com CC: maximilian.aster< at >boc-eu.com Created an attachment (id=22923) --> (https://issues.apache.org/bugzilla/attachment.cgi?id=22923) example fo Block elements which have only an id defined should not create a paragraph in RTF, because they are just used to reference somewhere, to the last page for example.

DO NOT REPLY [Bug 46276] New: Justified text rendered poorly in AFP Renderer

2008-11-24T13:58:00

https://issues.apache.org/bugzilla/show_bug.cgi?id=46276 Summary: Justified text rendered poorly in AFP Renderer Product: Fop Version: 0.95 Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: general AssignedTo: fop-dev< at >xmlgraphics.apache.org ReportedBy: bowditch_chris< at >hotmail.com Created an attachment (id=22922) --> (https://issues.apache.org/bugzilla/attachment.cgi?id=22922) sample AFP File This affect can be observed using the FO from the test case block_text-indent.xml in test\layoutengine\standard-testcases. I have attached a generated AFP file to illustrate. See the second paragraph where the lines don't end evenly against the right margin.

Bug report for Fop [2008/11/23]

2008-11-24T07:08:11

DO NOT REPLY [Bug 46272] New: printing the first page with full contents but page breaks in next pages itself

2008-11-24T04:58:00

https://issues.apache.org/bugzilla/show_bug.cgi?id=46272 Summary: printing the first page with full contents but page breaks in next pages itself Product: Fop Version: 0.94 Platform: Other OS/Version: Windows XP Status: NEW Keywords: XSLTBug Severity: major Priority: P1 Component: pdf AssignedTo: fop-dev< at >xmlgraphics.apache.org ReportedBy: nain_amitnain< at >yahoo.com After printing the first page with full contents upto the length specifed but in the next pages it breaks page and shifted to next page even though the this page have the space for the more contents. I am using the dynamic table creation with the conditional data. Please suggest some solution?

DO NOT REPLY [Bug 46253] New: break-after not honored

2008-11-21T08:12:44

https://issues.apache.org/bugzilla/show_bug.cgi?id=46253 Summary: break-after not honored Product: Fop Version: 0.95 Platform: PC OS/Version: Windows Server 2003 Status: NEW Severity: normal Priority: P2 Component: page-master/layout AssignedTo: fop-dev< at >xmlgraphics.apache.org ReportedBy: gd< at >geneon.de Created an attachment (id=22907) --> (https://issues.apache.org/bugzilla/attachment.cgi?id=22907) Testcase With break-after="odd-page" there should be one empty page and the second block should start on page 3. FOP 0.94 gets it wrong since it creates one empty page when break-after is set to even-page, and indeed two empty pages with odd-page, instead of respectively 0 and 1. FOP 0.95 doesn’t seem to honor the break at all.

DO NOT REPLY [Bug 46251] New: space-end on throws off formatting in pdf

2008-11-20T18:26:52

https://issues.apache.org/bugzilla/show_bug.cgi?id=46251 Summary: space-end on throws off formatting in pdf Product: Fop Version: 0.95 Platform: PC OS/Version: Windows XP Status: NEW Severity: minor Priority: P2 Component: pdf AssignedTo: fop-dev< at >xmlgraphics.apache.org ReportedBy: pilcme< at >yahoo.com When a block begins with an and the has a space-end attribute, the first line of the block is badly formatted in pdf. The first line is longer than it should be by the amount of the space-end. I have not tried any other output besides pdf. This also happened on 0.94. I have not tried it on any older version and I have not tried in on the current trunk. I am attaching an FO file. If you generate a pdf from this FO you should see the problem. Note that my block has text-align="justify". This makes the problem easier to see but the problem remains without the text-align.

DO NOT REPLY [Bug 46240] New: break-before breaks span?

2008-11-19T09:21:29

https://issues.apache.org/bugzilla/show_bug.cgi?id=46240 Summary: break-before breaks span? Product: Fop Version: 0.94 Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: page-master/layout AssignedTo: fop-dev< at >xmlgraphics.apache.org ReportedBy: gd< at >geneon.de Attached you will find a small fo-file containing one simple page master and two pages. Although the page master has a column-count=2, both pages should be single-column, therefore span=all is used. Both pages should start at an odd page, therefore break-before=odd-page is used. The unexpected result: The text on the first page uses both columns, the second page is empty, but the text on the third page uses only one column. When I remove the first page or break-before, the second text uses both columns.

Updating the FOP release plan

Jeremias Maerki — 2008-11-19T08:37:41

On a serious note (as opposed to my outburst on fop-users), I think we should really discuss the FOP release plan which we haven't updated in a while. I would hate to see FOP in 0.x mode after 10 years of existence. Let's assume 0.20.5 was actually FOP 1.0, and FOP 0.95 was actually FOP 2.0. How about calling the next version 2.009 (to be released in early 2009). Skip 1.0 entirely since that would only let the expectations rise into the sky. FOP had a major redesign which warrants at least a version jump of one major version. Not calling it 2.0 means it's not a first release from a fresh development branch. That will carry the message along that FOP is stable and usable in a productive environment. Hell, it's used in production by so many people for so many years. OhpointXitis is really bad. I know we still have about one item left on our pre-1.0 list: http://wiki.apache.org/xmlgraphics-fop/ReleasePlanning But that's still going to take a while. I want to revisit this list and see what today's view is. Fla

Table carry over to new page

JavaPenguin — 2008-11-19T08:11:34

I am generating tables in xsl-fo format and using fop to generate the pdf. A table is repeated n times. Some time the table is spread across two pages. How can I force the table to carry over to the next page if it does not fit onto the current page and not spread across two pages.

OutOfMemory Error When Building Website

Vincent Hennebert — 2008-11-18T11:40:11

Hi, I have the following error when building the website with Forrest: * [352/33] [0/0] 8.844s 0b compliance.pdf Exception in thread "main" java.lang.OutOfMemoryError: Java heap space at java.util.LinkedList.addAll(LinkedList.java:278) at java.util.LinkedList.addAll(LinkedList.java:247) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:361) at org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:116) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:294) at org.apache.fop.layoutmgr.list.ListItemLayoutManager.getNextKnuthElements(ListItemLayoutManager.java:234) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:294) at org.apache.fop.layoutmgr.list.ListBlockLayoutManager.getNextKnuthElements(ListBlockLayoutManager.java:119) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNex

Remove FAQ Entries Related to 0.20.5

Vincent Hennebert — 2008-11-18T11:14:41

Guys, What do you think of removing entries in the FAQ section that are specific to 0.20.5 and earlier versions? This would make it shorter, so less likely to scare people away, and in the same time easier for them to find the answer to their question. Plus it would stress the fact that we no longer support 0.20.5. Vincent

fo:inline screwing up rendering

Vincent Hennebert — 2008-11-17T11:36:09

Hi All, Does anybody know why FOP Trunk completely screws up the rendering of the attached file? It works fine when removing the fo:inline element, so I guess this has something to do with that element. FOP 0.95 renders the file correctly, both with and without the fo:inline. Thanks, Vincent

Bug report for Fop [2008/11/16]

2008-11-17T07:08:11

DO NOT REPLY [Bug 46211] New: Synchronization fault in FontCache

2008-11-14T13:12:05

https://issues.apache.org/bugzilla/show_bug.cgi?id=46211 Summary: Synchronization fault in FontCache Product: Fop Version: 0.95 Platform: PC OS/Version: Linux Status: NEW Severity: minor Priority: P2 Component: fonts AssignedTo: fop-dev< at >xmlgraphics.apache.org ReportedBy: rogov< at >devexperts.com I have an application which renders a lot of PDFs using several threads. We had an issue recently, concerning font loading. While investigating this stack trace: java.lang.NullPointerException at org.apache.fop.fonts.FontCache.isFailedFont(FontCache.java:294) at org.apache.fop.fonts.autodetect.FontInfoFinder.find(FontInfoFinder.java:179) at org.apache.fop.render.PrintRendererConfigurator.addFontInfoListFromFileList(PrintRendererConfigurator.java:233) at org.apache.fop.render.PrintRendererConfigurator.buildFontListFromConfiguration(PrintRendererConfigurator.java:140) at org.apache.fop.render.PrintRendererConfigu