Our biggest problem now is that we haven't been able to detect when the
issue occours before our customer does. I guess a possible (but not
optimal) work around for us would be to check the PDF files if they got
this issue (getAllPages.size() is not the same as getNumPages()), and then
raise an exception so we can contact the senders manually.


Aleksander

On Tue, Jul 8, 2014 at 11:05 AM, Maruan Sahyoun <sahy...@fileaffairs.de>
wrote:

> of course it’s possible to put in a workaround - might it be in PDFBox
> itself or in the merging application. Even better might be to check why
> this - at least misleading information - might have been created. Would you
> think you could influence that?
>
> BR
> Maruan
>
> Am 08.07.2014 um 11:01 schrieb Aleksander Blomskøld <aleks...@gmail.com>:
>
> > Yes, it's the same issue. The files attached actually comes from the
> > company I'm working for.
> >
> >
> > On Mon, Jul 7, 2014 at 11:05 PM, Maruan Sahyoun <sahy...@fileaffairs.de>
> > wrote:
> >
> >> the issue is because part1.pdf in PDFBOX-1533 references the same 2
> pages
> >> 3 times within the document catalog (/Kids [3 0 R, 3 0 R, 3 0 R]). Could
> >> you attach a sample pdf to PDFBOX-1533 to verify that your issue has the
> >> same cause or verify it for yourself?
> >>
> >> We are using PDFBox for merging documents ourselves successfully.
> >> Obviously this file would need some special treatment.
> >>
> >> BR
> >> Maruan
> >>
> >> Am 07.07.2014 um 11:31 schrieb Aleksander Blomskøld <aleks...@gmail.com
> >:
> >>
> >>> Hi,
> >>>
> >>> We're using PDFBox for PDF validation and PDF merging in a backend
> >>> invoicing system. It's working pretty well for most of the time, but
> >> right
> >>> now we're having some unhappy customers because of
> >>> https://issues.apache.org/jira/browse/PDFBOX-1533.
> >>>
> >>> As it's important for us to have this fixed pretty soon, we're
> wondering
> >> if
> >>> anyone of you would be willing to fix this issue for pay. If so, please
> >>> contact me so we can work out the details.
> >>>
> >>>
> >>> Regards,
> >>>
> >>> Aleksander Blomskøld
> >>
> >>
>
>

Reply via email to