In my efforts to evaluate iText as a PDF API, I'm finding that going from a creative design (like from an Art Director) to Java code, and making it look even remotely close, is an arduous process.
It can indeed.
This is usually better solved by having the creative person do their work in a GUI editor of some fashion (Illustrator, CorelDraw, etc.) and then having that exported in a form that you can work with (SVG, EPS, PDF, etc.) to convert to PDF (with necessary substitutions). Or starting with a PDF template that you then amend as necessary.
So far, through experimentation, I have been able to come roughly close to what the art director wants to see, but not near close enough to get any sort of signoff.
Perhaps you need to give us more information about what they want and what you are having problems delivering...Example PDF's would be helpful.
LDR -- --------------------------------------------------------------------------- Leonard Rosenthol <mailto:[EMAIL PROTECTED]> Chief Technical Officer <http://www.pdfsages.com> PDF Sages, Inc. 215-629-3700 (voice) 215-629-0789 (fax)
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
iText-questions mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/itext-questions
