I'm sure this isn't a great place to ask for a resolution to my itextsharp issues, but you seem to be the only person I've stumbled across who might know the answer (I'm sure you're well-aware that there is a serious dearth of documentation and information available about itextsharp otherwise).
We are doing much the same as your post suggests (using itextsharp to fill fields in a pre-defined PDF and send it down to the user user) and we have just about given up on being able to use itextsharp to fill a PDF form textbox with rich-text-encoded text and I was wondering if you might have any suggestions for us.
Acrobat makes it trivial to setup a textbox field in a PDF form to accept RTF content (just set the props on the field to 'use RTF text' in the forms designer) but when we use itextsharp to fill this field with RFT-encoded content, the RTF syntax is reproduced in its entirety with in the textbox in the PDF (e.g., we get '{\rtf\01\hello\etc....}' instead of the text with the formatting applied).
Have you (or anyone else who might view this blog post) ever tried this and come across the same issue? Other than this, we find itextsharp to be a quite useful tool for systems that need to collect data in one format (e.g., via a web form, a winform, whatever) and then display that back to the user in any pre-conceived format in an organizational-specific paper-form equivalent).
Happy coding to all~!
-Steve B.