I am completely not an expert on the pdf specifications, but I'm wondering
whether this PDF I have is doing anything "wrong", and if so, whether it
would be worth itext[sharp] handling it anyway?
Context is, I was given a bug to fix that, for a particular PDF we were
sent to look at, which contain
look into a bug that's still
easily reproduceable? (At least I hope it is; otherwise I'm going crazy...)
On Tue, Dec 4, 2012 at 11:13 PM, 1T3XT BVBA wrote:
> Wasn't this fixed a long time ago?
> Which version are you using?
>
>
> On 5/12/2012 0:31, Adam Field wrote:
>
Ooh, I know this one. Oddly enough, yes I -have- used iTextSharp from MFC.
I don't believe iTextSharp itself provides a COM interface, but it's easy
enough to make a wrapper dll in C# that does provide a COM interface (
http://msdn.microsoft.com/en-us/library/c3fd4a20.aspx), and import said
interfa
On Tue, Mar 29, 2011 at 2:45 PM, Adam Field wrote:
> On Mon, Mar 28, 2011 at 12:44 PM, Mark Storer wrote:
>> Ah. You have an XFA based form, and are using AcroForm tech to address it.
>> Don't do that.
>
> Alright, I suppose that's good to know (I do see tha
On Mon, Mar 28, 2011 at 12:44 PM, Mark Storer wrote:
> Ah. You have an XFA based form, and are using AcroForm tech to address it.
> Don't do that.
Alright, I suppose that's good to know (I do see that now, and also
see it documented that using the high-level AcroForms API *usually*
works, but
