iText 7无法识别第三方PDF表单字段，Acrobat重存后恢复正常的技术问询

1. Tools to Analyze PDF Structure Differences #

Use these tools to pinpoint structural gaps between your original and Acrobat-re-saved PDFs:

• iText RUP: You already used this to confirm the empty Fields array in the original PDF. It lets you directly compare the AcroForm dictionary and page annotation structure across both files.
• PDFtk:
  • Run pdftk original.pdf dump_data_fields vs pdftk resaved.pdf dump_data_fields to see missing field metadata in the original.
  • Decompress both files with pdftk input.pdf output uncompressed.pdf uncompress, then use a text diff tool (VS Code's built-in diff, WinMerge, etc.) to compare the uncompressed content—this reveals exactly how Acrobat populates the central Fields array.
• qpdf: A command-line tool that converts PDFs to human-readable QDF format. Execute qpdf --qdf --object-streams=disable original.pdf original_qdf.pdf and repeat for the resaved file, then diff the QDF outputs to spot structural changes.
• Adobe Acrobat Preflight: Navigate to Tools > Print Production > Preflight and use "PDF Analysis" profiles to flag form structure issues like missing central Fields arrays.
• iText PDF Debugger: A GUI tool for browsing the PDF object tree. Inspect the AcroForm dictionary and page-level Widget annotations to see how fields are stored in both versions.

2. Fixing the Issue with iText 7 #

Your initial open/save code preserves the original broken structure—Acrobat fixes it by scanning page annotations and collecting fields into the central Fields array. You can replicate this behavior in iText 7 with the following code:

public void RepairPdfForm(string inputPath, string outputPath)
{
    using var pdf = new PdfDocument(new PdfReader(inputPath), new PdfWriter(outputPath));
    var form = PdfAcroForm.GetAcroForm(pdf, true); // Create AcroForm if it doesn't exist

    // Iterate through all pages to collect widget annotations
    foreach (var page in pdf.GetPages())
    {
        var annotations = page.GetAnnotations();
        foreach (var annotation in annotations)
        {
            // Check if the annotation is a form widget
            if (PdfName.Widget.Equals(annotation.GetSubtype()))
            {
                // Retrieve the form field linked to the widget
                var field = PdfFormField.GetFormFieldFromWidget(annotation);
                if (field != null)
                {
                    // Add the field to the central AcroForm Fields array
                    form.AddField(field);
                }
            }
        }
    }

    // Optional: Ensure field appearances render correctly
    form.SetNeedAppearances(true);
}

Why This Works: #

• The original PDF stores form fields only as page-level Widget annotations, not in the central Fields array of the AcroForm dictionary. iText relies on this central array to locate fields by default.
• This code scans each page for Widget annotations, extracts their associated form fields, and adds them to the AcroForm's Fields array—mimicking Adobe Acrobat's re-save behavior.
• After running this, your original test code will correctly detect fields: form.GetAllFormFields() will return the full collection, and form.GetField("FIELD_NAME") will work as expected.

Verify the Fix: #

Use pdftk repaired.pdf dump_data_fields to confirm fields are now detected, or run your original test code against the repaired PDF to validate field access.

内容的提问来源于stack exchange，提问作者Sam