pdftk/Makefile.Base | 2 1 + 1 - 0 !
pdftk/Makefile.Debian | 10 5 + 5 - 0 !
2 files changed, 6 insertions(+), 6 deletions(-)

 change compiler parameters for debian

pdftk/pdftk.cc | 17 15 + 2 - 0 !
1 file changed, 15 insertions(+), 2 deletions(-)

 support prompt for user_pw and owner_pw simultaneously
 The check if user_pw is not equal to owner_pw should be after prompting for them.

pdftk/pdftk.cc | 20 12 + 8 - 0 !
1 file changed, 12 insertions(+), 8 deletions(-)

 warn instead of fail if no owner password is given.

java/com/lowagie/text/pdf/PdfReader.java | 20 10 + 10 - 0 !
1 file changed, 10 insertions(+), 10 deletions(-)

 this patch fixes an infinite loop caused by cr instead of crlf
 line endings in non-standard-conform pdf files.

java/com/lowagie/text/pdf/PdfWriter.java | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 avoid nullpointerexception
 at com.lowagie.text.pdf.PRIndirectReference.toPdf

pdftk/pdftk.cc | 5 5 + 0 - 0 !
1 file changed, 5 insertions(+)

 set additionally lc_messages=c and lc_all=c to
 circumvent libgcj10 exception with locale de_AT.UTF-8.
 This patch is a workaround to an ArrayIndexOutOfBoundsException evoked in
 java.text.SimpleDateFormat.formatWithAttribute (libgcj10, Version 4.4.2-4).
 The exception occures only between April and December and with the de_AT-UTF.8 locale.

java/com/lowagie/text/pdf/PdfWriter.java | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 fix wrong entries in xref table.
 This fixes a off-by-one error in the included itext-paulo library which makes
 at least the burst command to produce non-standard-conform PDF documents
 whose free entries in the xref table are wrongly marked as used.

java/com/lowagie/text/pdf/PRTokeniser.java | 6 6 + 0 - 0 !
1 file changed, 6 insertions(+)

 do not fail if an objstm ends with a number
 Without this fix, pdftk fails for example on particular PDF version 1.5
 documents generated by newer pdflatex versions.

 The actual bug is in the method PRTokeniser#nextValidToken. This method has
 the feature that it treats an indirect object reference (such as 24 0 R) as a
 single token. Therefore when it sees a number, it has to look ahead to see if
 the number is actually the start of an indirect object reference.  If, however,
 the object stream ends during this lookahead then it would wrongly fail. So it
 will go wrong whenever the last object in an object stream is a number.