Hello Luis,thanks for taking the time to test the patch. From a quick look I
had, it seems this is a legit issue (the reading order is wrong -- I can not
reproduce the long pause between lines).
Date: Sun, 15 Feb 2015 23:44:37 +0000
Subject: Re: [VOTE] Merge Temp_MergeTaggedPDF to trunk
Thank you. That worked.
What happens when a document with the first limitation is used? I
assume the output is not correct, but in what way?
I performed a simple search for "tagged pdf example". One of the
first hits is this link:
The sample there does not work very well with this patch. The
content is read in a different order. And there are long pauses
between lines, something that does not happen with the original (I
only tested with Adobe Reader in Windows 8.1). Is this sample an
example that this patch does not support? Or is the problem with
On 2/15/15 7:47 PM, Simon Steiner wrote:
If you use
pdfplugin, delete fontbox 1.8 jar in fop and copy pdfbox and
fontbox pdfplugin jars to fop.
From: Luis Bernardo
Sent: 15 February 2015 19:16
Subject: Re: [VOTE] Merge Temp_MergeTaggedPDF to
Given the fact that fop-pdf-images (including this branch)
uses pdfbox 2.0 snapshots while fop trunk uses 1.8.5 (the
fontbox jar) I think we need some information on how to test
this. I thought that using the recent pdfbox 1.8.8 jars
would work but it doesn't seem to be the case. What version
of pdfbox jars should we use with fop?
Also, I would like to suggest that if we run two votes in
parallel then 5 working days for both votes may not be
On 2/10/15 11:04 AM, Simon Steiner wrote:
Thanasis Giannimaras provided patch to
merge Tagged PDF for pdf plugin and small patch for fop.
Known Limitations :
- Only PDF with marked-content sequences
in the page content stream are supported. Marked-content
sequences in content stream other than the content stream of
the page are not supported.
- Repeated headers and footers are not
completely supported. Example: 2-page pdf including table
that spans both pages with repeated header. If you merge the
second page, the table header will be visible in the pdf but
the reader will ignore it (same principle applies for
In order to use this feature,
accessibility must be enabled in the configuration file and
the source pdf must be accessible (tagged).
The vote will last 5 working days, ending
Here is my vote: +1