Hi Adam,
PdfReader.GetPageN() does exist in iTextSharp but isn't a static function,
you need to call it from an instance of the PdfReader object, i.e.:
PdfReader reader = new PdfReader(myDoc.PDF);
reader.GetPageN(1).Put(PdfName.CROPBOX, new PdfRectangle(...));
Cheers,
Brian
Brian Chappell
While I'm not able to offer a solution here I can talk about the principle
which may help crystallise your dilemma.
When a document is digitally signed, the entire document is encrypted and
the result of that encryption is stored with the document. This allows
someone with the appropriate key to
Which version of the AGPL is going to be used?
--
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your
Was the intent to change the license for the 4.1.6/4.2.0 as well? I notice
that the source on sourceforge now includes the AGPL license rather than the
LGPL/MPL as before. Was that deliberate or accidental? Should we read that
previous versions of iTextSharp are now no longer compatible with those
Thanks for that clarification Paulo, it does leave me a little confused
however.
If you pull the 106 revision (or in fact any revision after 98) the
AssemblyInfo still states a version of 4.1.6 but the license in each file is
AGPL as is the License indicated in the Develop tab of whole the
Sorry Paulo, but what do you mean you don't see where there's doubt? You
have the potential of multiple DLLs all reporting 4.1.6 as their version and
no way of telling if it's a LGPL/MPL or and AGPL licensed release unless you
are working from the source. That's confusion to me. The announcement
I can see I'm wasting my time here.
-Original Message-
From: Paulo Soares [mailto:psoa...@glintt.com]
Sent: 08 December 2009 8:43 AM
To: Post all your questions about iText here
Subject: Re: [iText-questions] Silent license change?
You are talking about code that's still in the SVN,
