Hello,

I have to correct, what I have said:
Manipulation only the XFA-part of my form works with Adobe Reader,
but not with alternative readers like foxit. This is really a pity.


        -----Ursprüngliche Nachricht-----
        Von: Leonard Rosenthol mailto:[EMAIL PROTECTED]
        Gesendet: 07.03.2008 16:21:47
        An: Post all your questions about iText here 
mailto:itext-questions@lists.sourceforge.net
        Betreff: Re: [iText-questions] XFA-Forms with a PDF couterpart inside
        
        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: Microsoft
        Defy all challenges. Microsoft(R) Visual Studio 2008.
        http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
        _______________________________________________
        iText-questions mailing list
        iText-questions@lists.sourceforge.net
        https://lists.sourceforge.net/lists/listinfo/itext-questions
        Buy the iText book: http://itext.ugent.be/itext-in-action/
        



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
iText-questions mailing list
iText-questions@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/itext-questions
Buy the iText book: http://itext.ugent.be/itext-in-action/

Reply via email to