Hello,
Regarding this discussion on the relationship between xfa and pdf,
http://www.mail-archive.com/itext-questions@lists.sourceforge.net/msg36570.h
tml
the final solution Leonard provided was to use iText to extract xfa from the
pdf,
then modify and inject it into the shell pdf.
After a few days of being frustrated this is exactly what Im looking for!
Thank you so much! Now I just need to
find out how to go about extracting xfa from a pdf which I *know* does
contain xfa
any pointers, advice welcome, thank you.
Dilligently reading up on iTextSharp,
DorothyB
>>Leonard Rosenthol
>Fri, 07 Mar 2008 07:21:41 -0800
>On Mar 7, 2008, at 3:04 AM, Sérgio Oliveira wrote:
>> Are you saying that when we open a Livecycle designer pdf file (xfa
>> based pdf) in Acrobat Reader, the Reader will not "parse" the PDf
>> but it will parse the xfa inside the pdf? So the pdf file could be
>> a "dummy" empty pdf with only the real xfa structure?
>>
>
> That is EXACTLY what I am saying!!
>
> You only need enough PDF structure to enable Reader to get to the /
>Catalog/AcroForm/XFA key - where it will find your XFA and then
>ignore all the rest. You can see such "shell PDFs" by using
>LiveCycle Designer 8.x (the version that comes with Acrobat 8) and
>creating a dynamic form - it will create file just like that.
>
>
>> If this is the point you were talking about, then it means that if
>> one extrats the xfa from a dummy PDF file (empty without any
>> object, only with a xfa structure) using iText; then change the xfa
>> structure and finally inject the modified structure into the dummy
>> pdf file again, then Reader will render it and show a new pdf file?
>> (with the new modifications).
>
> BINGO!! You now understand what I am saying...
>
>
>> If this is true, then I don´t understand why Adobe didn´t abolished
>> the PDF from the process at all.
>
> Because PDF documents are something that users know about. They
>know what one is and how to use it. In addition, all the software
>(OS, web browsers, servers, etc.) all know what a PDF is. If we
>introduced a new file type (let's call it .xfa for example) - this
>would be a new thing that wouldn't get handled correctly. There is
>no reason for the average user to have to learn about XFA.
>
>
>Leonard
>
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
iText-questions mailing list
iText-questions@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/itext-questions
Do you like iText?
Buy the iText book: http://www.1t3xt.com/docs/book.php
Or leave a tip: https://tipit.to/itexttipjar
