svn's dif command should be useful for this. If you are using an IDE like
Eclipse, you can just check out both versions, then do a Compare With Each
Other operation. This is starting to move far afield from a discussion
about itext - probably best to ask google about how to use svn dif.
--
View
Bah - you've got the change log entry where the fix was made, just do a tree
wide compare of that version of the entire repo to the previous version.
You'll find all the modified files, and what was changed in them. There's
no need to do file-by-bile comparison (which I agree *would* require a so
Thanks guys. I'm looking at the SVN blog site in order to get help from it.
And you're right, this is a large project, but this one aspect is messing
up.
--
View this message in context:
http://itext-general.2136553.n4.nabble.com/Fixing-EOFException-In-Version-2-0-8-tp3736353p3739572.html
Sent fr
Changes made by Kevin Day
Fix bug that caused end of file errors when parsing an object at very
end of an object stream.
And I did what you said and created the small app that read the bytes in and
wrote it to another file. Sadly the %%EOF was there in the newly created
text file. So going to
On 12/08/2011 15:34, 1T3XT BVBA wrote:
Sure, but not that obvious for a large project, unless you already know
where to look.
This could help understanding the structure of svn
http://www.redlab.be/blog/2011/developer-guide/
(however it has changed a bit since 'wayback long time ago prehistoric
On 12/08/2011 15:24, Kevin Day wrote:
> Not to point out the obvious or anything, but why don't you do a diff of the
> two versions of code and see what the differences were between the unfixed
> and fixed version? That is what svn is for, after all... You can look at
> the commit history to find
Not to point out the obvious or anything, but why don't you do a diff of the
two versions of code and see what the differences were between the unfixed
and fixed version? That is what svn is for, after all... You can look at
the commit history to find the commit that fixed this issue you think mi
On 12/08/2011 13:44, NerdManJr wrote:
> which is where I think the problem was fixed
Before you start that effort, check if the problem is caused by the %%EOF.
If that's the case, writing a small app that preprocesses the PDFs could
do the trick.
If that's not the case, we don't know what fixed th
> Thank you tons for the heads up. I noticed in the logs that you
> guys had fixed the problem in one of the releases, I was trying to actually
> find a way of doing it myself based on the 2.0.8 version, but didn't know
> what exactly you guys had changed from the 2.0.8 to the 2.6.1 versions.
I gue
On 12/08/2011 13:44, NerdManJr wrote:
Hello there. Thank you tons for the heads up. I noticed in the logs that you
guys had fixed the problem in one of the releases, I was trying to actually
find a way of doing it myself based on the 2.0.8 version, but didn't know
what exactly you guys had change
Hello there. Thank you tons for the heads up. I noticed in the logs that you
guys had fixed the problem in one of the releases, I was trying to actually
find a way of doing it myself based on the 2.0.8 version, but didn't know
what exactly you guys had changed from the 2.0.8 to the 2.6.1 versions.
On 11/08/2011 22:08, NerdManJr wrote:
> Here is the code I am using. I know the software is outdated, that is why I
> continued to say I'm forced to use the 2.0.8 version.
Check the PDF that causes the EOFException.
Does it end with %%EOF?
If not, remove all the bytes that follow the last occurence
I would, but I'm closing with the PdfStamper and don't know how to do that
with it. How would I?
--
View this message in context:
http://itext-general.2136553.n4.nabble.com/Fixing-EOFException-In-Version-2-0-8-tp3736353p3737092.html
Sent from the iText - General mailing list archive at Nabble.com
Here is the code I am using. I know the software is outdated, that is why I
continued to say I'm forced to use the 2.0.8 version.
public static void addWatermark(ArrayList files, String country){
BaseFont bf = null;
String originalAttachmentName = null;
String newAttachmentName = null;
PdfConte
Try calling flush before close if it’s available.
From: Alexis Pigeon [mailto:pigeon.ale...@gmail.com]
Sent: Thursday, August 11, 2011 3:30 PM
To: Post all your questions about iText here
Subject: Re: [iText-questions] Fixing EOFException In Version 2.0.8
Hi NerdManJr
On 11 August 2011
Hi NerdManJr
On 11 August 2011 18:26, NerdManJr wrote:
> Hey guys. I'm forced to use iText version 2.0.8 and currently getting an
> error when trying to watermark a certain PDF. I can't include the PDF, but
> wanted to know a fix I could do other than upgrading to the newest version
> of iText.
Hey guys. I'm forced to use iText version 2.0.8 and currently getting an
error when trying to watermark a certain PDF. I can't include the PDF, but
wanted to know a fix I could do other than upgrading to the newest version
of iText. I know the bug was fixed already (I think it was fixed in version
17 matches
Mail list logo
