I guess I could have been more open about the problem I'm facing. I use OpenOffice to edit the .odt files for the Apache pdf forms for various documents and then export them as .pdf and store them on the apache.org <http://apache.org/> site as editable forms.
Many pdf form editors are then used by community members to fill, sign, and send the forms to [email protected] <mailto:[email protected]>. Once they arrive, they are processed by an application that displays the pdf form, reads the form fields, and fills fields in the web application. What I'm looking for is advice on how to define the form fields so they are able to be filled by the user and later processed by the application, in a consistent manner regardless of which pdf form filler is used. Any advice, including tutorial links to creating form field, is appreciated. > On Sep 24, 2025, at 17:19, Craig Russell <[email protected]> wrote: > > With the new oak leaf logo, I will undertake to update the forms to remove > the feather and replace it with the leaf. > > There are a few things that don't work reliably that I'd like to fix while I > have the forms open. > > Mostly I use Mac Safari to open the forms. The behavior is sometimes > different with Chrome or Firefox. I use the whimsy application to open and > view the pdf filled forms. > > The main problem is that the ICLA behaves differently, perhaps because of the > different form fill pdf applications. > > Sometimes the saved form that is sent to secretary has fields that when > clicked, open a field a few rows below the row where the field is on the form. > > Sometimes the font displayed is not what was originally intended. I'd like > the form itself to specify which font is to be used when the user enters data > into fields. > > Sometimes the fields appear to be entered twice, with the second field > slightly offset, making it difficult to read. This seems to occur mostly with > Safari, less so with Chrome. > > Any suggestions or references to user manuals will be appreciated. > > Warm regards, > Craig > > Craig L Russell > [email protected] > Craig L Russell [email protected]
