Am 05.04.2013 07:45, schrieb Andreas Lehmkuehler:
Hi,
Hi,
Am 04.04.2013 20:53, schrieb Thomas Chojecki:
Hi all,
I have patched the COSWriter and I would ask you to test it please. I
attached
the patch.
Thanks for jumping in. Looks good to me, it restores the old
behaviour. I'll run
some
Hi,
Thomas Chojecki i...@rayman2200.de hat am 5. April 2013 um 10:31 geschrieben:
Am 05.04.2013 07:45, schrieb Andreas Lehmkuehler:
Hi,
Hi,
Am 04.04.2013 20:53, schrieb Thomas Chojecki:
Hi all,
I have patched the COSWriter and I would ask you to test it please. I
attached
the
Hi,
Am 05.04.2013 um 11:10 schrieb Andreas Lehmkühler andr...@lehmi.de:
Hi,
Thomas Chojecki i...@rayman2200.de hat am 5. April 2013 um 10:31
geschrieben:
Am 05.04.2013 07:45, schrieb Andreas Lehmkuehler:
Hi,
Hi,
Am 04.04.2013 20:53, schrieb Thomas Chojecki:
Hi all,
I have patched
Hi,
Am 04.04.2013 16:41, schrieb Maruan Sahyoun:
Hi Andreas,
it's related to PDFBOX-1551 as you already guessed. In addition PDF-1556 is
related to PDFBOX-1551. I linked them in Jira.
Thanks.
I ran a quick test. As suggested I simply load and save a pdf and got 2
different results:
-
Hi Andreas,
I'm currently on a trip but could it be the test in line 595 of COSWriter? I
have some more time tomorrow
Kind regards
Maruan Sahyoun
Am 04.04.2013 um 18:45 schrieb Andreas Lehmkuehler andr...@lehmi.de:
Hi,
Am 04.04.2013 16:41, schrieb Maruan Sahyoun:
Hi Andreas,
it's
Hi,
Am 04.04.2013 18:58, schrieb Maruan Sahyoun:
Hi Andreas,
I'm currently on a trip but could it be the test in line 595 of COSWriter? I
have some more time tomorrow
No, it seems to be in line 1142. In the case of a XRef stream the trailer isn't
written right after the xref table, which is
But the testfiles show that the xref is written as text and not as stream so I
think the fact that there is a stream in the doc ommits writing a trailer at all
Maruan Sahyoun
Am 04.04.2013 um 19:26 schrieb Andreas Lehmkuehler andr...@lehmi.de:
Hi,
Am 04.04.2013 18:58, schrieb Maruan
Zitat von Andreas Lehmkuehler andr...@lehmi.de:
Hi,
Hi Andreas,
Am 04.04.2013 16:41, schrieb Maruan Sahyoun:
Hi Andreas,
it's related to PDFBOX-1551 as you already guessed. In addition
PDF-1556 is related to PDFBOX-1551. I linked them in Jira.
Thanks.
I ran a quick test. As suggested
Hi all,
I have patched the COSWriter and I would ask you to test it please. I
attached the patch.
Due to temp. lacking access to my apache webspace, I uploaded the
patched jar on my private server.
http://media-nation.de/~rayman2200/pdfbox-1.9.0-SNAPSHOT.jar
Best regards
Thomas
If no
Hi Thomas,
I've tested with the files provided during recent complaints on the users
mailing list as well as PDFBOX-1556.
The files are accessible now using the jar you provided so the fix seems to
solve the issue. As I'm on travel I can't do a full test though.
Maruan Sahyoun
Am 04.04.2013
Hi,
Am 04.04.2013 20:53, schrieb Thomas Chojecki:
Hi all,
I have patched the COSWriter and I would ask you to test it please. I attached
the patch.
Thanks for jumping in. Looks good to me, it restores the old behaviour. I'll run
some additional tests at the weekend. BTW the written trailer
Hi,
Am 02.04.2013 17:22, schrieb Maruan Sahyoun:
Hi,
there might be a regression in pdfbox-1.8.1 compared to pdfbox-1.7.1.
The samples under the us...@pdfbox.apache.org email list for 'Error when
opening multi-page PDF generated by PDFBox' work fine in 1.7.1 but are
corrupt as is
12 matches
Mail list logo