DO NOT REPLY [Bug 39443] Long tables stop spanning in multiple columns after first page

2011-05-26 Thread bugzilla 
https://issues.apache.org/bugzilla/show_bug.cgi?id=39443

Harsha harsh...@gmail.com changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 CC||harsh...@gmail.com
Version|0.95|all
 Resolution|FIXED   |

--- Comment #8 from Harsha harsh...@gmail.com 2011-05-26 13:09:17 UTC ---
This has come back in apache fop version 6.X

-- 
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 51270] New: [PATCH] PDFOutline: 'endobj' should be preceded by an EOL

2011-05-26 Thread bugzilla 
https://issues.apache.org/bugzilla/show_bug.cgi?id=51270

 Bug #: 51270
   Summary: [PATCH] PDFOutline: 'endobj' should be preceded by an
EOL
   Product: Fop
   Version: all
  Platform: All
OS/Version: All
Status: NEW
  Severity: normal
  Priority: P2
 Component: pdf
AssignedTo: fop-dev@xmlgraphics.apache.org
ReportedBy: matthias.bauer@infineon.com
Classification: Unclassified


Created attachment 27071
  -- https://issues.apache.org/bugzilla/attachment.cgi?id=27071
patch

org.apache.fop.pdf.PDFOutline.toPDF() outputs  endobj\n. 

According to PDF/A spec (or at least according to the validators I've used)
there has to be a \n in front of the endobj tag. (And at every other position
in the code we're already outputting a \n.)

The patch changes the output to \nendobj\n.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

Fop Memory Leak

2011-05-26 Thread Eric Douglas 
I could use some help tracking this down.  I created a Print Preview
program but it just runs out of memory after a dozen or two pages.
I started with a program which generates XML data, transforms it into FO
data, then transforms that.
There are 2 transforms in it, one to create a PDF and one for Print
Preview.
When I tried to create a large FO and generate a PDF of 1000+ pages it
crashed, out of memory.
I changed it to break the output.  It now stores an array of FO files
for no more than 10 pages each, using XSL's intiial-page-number to store
a starting point for each document fragment.
To create a PDF I call the transformer to get the PDF from the Fop
output stream in byte format for each FO.  Then I load them into PDF
objects using the pfdbox project, create a new PDF with it and copy in
the pages to merge them.
This works great for PDF.  I was able to generate a report this way of
over 1800 pages.
Now I try it for print preview, generating 10 pages at a time, calling
the render process again when a new size or a page from a different
block is requested.
The memory use never drops on these calls but in 2 places I see it
jumping up, whenever it calls Transformer.transform with a PNGRenderer,
and whenever I try to create a new image for a page even though I'm only
generating 10 pages and on each render I replace the previous array of
images.
If I do something as simple as this the memory jumps up sometimes on the
create.
myBufferedImage = myImageArray.get(pageNum);
myBufferedImage.flush();
myBufferedImage = new
BufferedImage(sameWidthAsOldImage,sameHeightAsOldImage);
It does this if I call PNGRenderer.getPageImage(pageNum) (from
Java2DRenderer), so I tried creating the BufferedImage (or VolatileImage
same issue) myself and using the Java2DRenderer.print method to draw the
page on it.  Memory use keeps increasing on the image create and on the
transform.
The transform is all done in one method, with only the FopFactory and
TransformerFactory remaining (created static final to the class) after
the method so a second call shouldn't use any more than the first.

Re: Want to contribute

2011-05-26 Thread darshan 

Hi Andreas,

I was doing a stupid thing by putting the test file into a wrong 
directory. Sorry for the unnecessary confusion. I have made the attached 
testcase again for the same bug and the test is working with the svn 
copy I have. Could you please check it out for me?


Thank you,
Drashan

On 25/05/11 04:08, Andreas L. Delmelle wrote:

On 24 May 2011, at 03:35, darshan wrote:

Hi Darshan


snip /

5. I found out the xpath values using the firefox extention XPather and then 
filled in the checks accordingly.

OK, that works too and looks comprehensive.
There is an easier way, though. If you have FOP set up in an IDE (Eclipse, IntelliJ 
IDEA...), then, as mentioned on the Wiki, you can just set up a JUnit Launch 
configuration, which will allow you to run the test from within your IDE. That's 
where those variables come into play. If you do not set them, the entire test suite will 
be run. Specifying '-Dfop.layoutengine.starts-with=...' as a VM parameter would only run 
those tests whose name starts with the specified string, etc.

In that case, you have the benefit of the standard output we normally get when 
running the test suite (see the output I posted earlier). If the test passes, 
you should also get a clear indication that none of the checks failed and the 
test finished successfully.


I have attached the .at files as well.

Also does follow-up attachment mean that I attached the file to the bugreport 
https://issues.apache.org/bugzilla/show_bug.cgi?id=50196 and close it?

Indeed. If we confirmed it on our end, we will then add the test to our suite, 
and everything remains available in Bugzilla for future reference. If we cannot 
verify that it has been fixed, we will reopen and will ask you to re-examine.

Thanks!

Regards

Andreas
---


?xml version=1.0 encoding=UTF-8?
!--
  Licensed to the Apache Software Foundation (ASF) under one or more
  contributor license agreements.  See the NOTICE file distributed with
  this work for additional information regarding copyright ownership.
  The ASF licenses this file to You under the Apache License, Version 2.0
  (the License); you may not use this file except in compliance with
  the License.  You may obtain a copy of the License at

   http://www.apache.org/licenses/LICENSE-2.0

  Unless required by applicable law or agreed to in writing, software
  distributed under the License is distributed on an AS IS BASIS,
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  See the License for the specific language governing permissions and
  limitations under the License.
--
!-- $Id: table-header_table-footer_padding.xml  2011-05-27 18:22:06Z darshan $ --
testcase
  info
p
  This test checks headers and footers left inline padding after a page break.
/p
  /info
  fo
fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; xmlns:svg=http://www.w3.org/2000/svg;
  fo:layout-master-set
fo:simple-page-master master-name=normal page-width=5in page-height=5in
  fo:region-body/
/fo:simple-page-master
  /fo:layout-master-set
  fo:page-sequence master-reference=normal white-space-collapse=true
fo:flow flow-name=xsl-region-body
  fo:table table-layout=fixed width=100%
fo:table-column number-columns-repeated=2 column-width=proportional-column-width(1)/
fo:table-header
  fo:table-row background-color=yellow
fo:table-cell
  fo:blockfo:inline padding-left=20header/fo:inline/fo:block
/fo:table-cell
fo:table-cell
  fo:blockfo:inline padding-left=20start of page/fo:inlinefo:page-number//fo:block
/fo:table-cell
  /fo:table-row
/fo:table-header
fo:table-footer
  fo:table-row background-color=orange
fo:table-cell
  fo:blockfo:inline padding-left=20footer/fo:inline/fo:block
/fo:table-cell
fo:table-cell
  fo:blockfo:inline padding-left=20end of page/fo:inlinefo:page-number//fo:block
/fo:table-cell
  /fo:table-row
/fo:table-footer
fo:table-body
  fo:table-row height=100pt
fo:table-cell
  fo:blockcell1/fo:block
/fo:table-cell
fo:table-cell background-color=lightgray
  fo:blockcell2/fo:block
/fo:table-cell
  /fo:table-row
  fo:table-row height=100pt
fo:table-cell background-color=lightgray
  fo:blockcell3/fo:block
/fo:table-cell
fo:table-cell
  fo:blockcell4/fo:block
/fo:table-cell
  /fo:table-row
  fo:table-row height=100pt
fo:table-cell
  fo:blockcell5/fo:block
/fo:table-cell