On Apr 30, 2007, at 1:44 PM, William Alexander Segraves wrote:
> Leonard, he scenario I had in mind was this:
>
> 1. Client-side browser "submits" to "localhost" server.
> 2. Localhost server parses submitted data, converting same into FDF/
> XFDF.
> 3. Localhost server returns FDF/XFDF in 2 above to client browser.
> 4. User saves the FDF/XFDF to a file.
> 5. User executes a command line process, e.g., Pdftk or an iText
> class, that
> merges the FDF/XFDF with a fillable PDF.
>
> 5(alt). User merges the FDF/XFDF with a fillable PDF with Acrobat.
>
> I do not believe the process described in steps 1 - 5 above is in
> violation
> of any Reader EULA, although it fits the description in the above
> statement:
>
You are correct - what you are describing above is PERFECTLY FINE!
The violation would have been if for 3, it returns a filled in PDF
instead of an FDF/XFDF.
> IMO, the problem we are having with the Adobe Reader EULA (v. 7 &
> up?) is
> that a legitimate use of other software on a localhost server,
> e.g., Pdftk,
> iText, to merge FDF/XFDF with a PDF, serving same to the client
> browser, is
> deemed by Adobe to be the same as enabling Reader to Save/SaveAs.
>
Exactly!
Leonard
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
iText-questions mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/itext-questions
Buy the iText book: http://itext.ugent.be/itext-in-action/
