> Copying the fields from the template doc to the doc with the > content is VERY simple and logical - there shouldn't be any problems.
I'm sure it is...but when new ways are added and old ways are not being depricated, case in point PRAcroForm.FieldInformation and AcroField.Item, well I'm sitting here programming with iText wondering why I have 2 data structures for what I would logically expect to be the same information, and nothing provided saying use blah because it's how we do stuff now. So finding this simple and logical way of copying information from a reader to a writer is made all the more complex. I've got a ref to the (/AcroForm) dictionary. Does that contain all the widgets for the fields as well? In the writer, can I just putAll the items from that (/AcroForm) dictionary to the new pdf document? How does one associate an (/Annot) dictionary with a particular page? What are indirect references used for? Is it just a way to identify data so you don't need the actual object reference? I see them used in a lot of places and I wasn't clear what they were being used for. You guys ever given much thought to ditching the current learn by example stuff and starting an iText wiki? Thanks, -Nick _______________________________________________ iText-questions mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/itext-questions
