Skip to content

Track unresolved upstream Apache PDFBox 4.0 parity risks #650

Description

@erikbra

Purpose

Track unresolved Apache PDFBox issues that may affect PdfBox.Net parity, without implementing .NET-only fixes ahead of upstream Apache PDFBox.

This issue is an umbrella for grouped tracking issues. The intent is to keep the known risks visible, add fixtures where useful, and port/adapt upstream fixes once Apache PDFBox has accepted a direction.

Policy

  • Do not mirror every Apache JIRA issue as a PdfBox.Net issue.
  • Do not implement speculative fixes that get ahead of upstream unless the issue is clearly .NET/backend-specific.
  • Prefer parity fixtures and Java-vs-.NET comparisons for rendering/text/parser behavior.
  • When current Apache trunk already contains a fix, verify the exact upstream change before porting it.

Upstream groups

  • Parser and xref recovery: PDFBOX-5032, PDFBOX-6201.
  • Large-file and memory behavior: PDFBOX-6175, PDFBOX-5034, PDFBOX-4690.
  • Text extraction: PDFBOX-2138, PDFBOX-2532, PDFBOX-6188.
  • Rendering/forms/masks: PDFBOX-2359, PDFBOX-5953, PDFBOX-6024.
  • Fonts/glyphs/subsetting: PDFBOX-6175, PDFBOX-2578, PDFBOX-3759, PDFBOX-4951.
  • Signatures: PDFBOX-3699.
  • Structure/collection model: PDFBOX-4414, PDFBOX-5172.
  • COS object robustness: PDFBOX-5731, PDFBOX-6200.
  • Optional utilities: PDFBOX-2124.

Acceptance criteria

  • Each grouped issue links the relevant Apache JIRA tickets.
  • Each grouped issue states whether the next action is watch-upstream, add fixture, or port a confirmed upstream change.
  • Closed only when the grouped issues are resolved, intentionally deferred, or superseded by more specific parity work.

Metadata

Metadata

Assignees

No one assigned

    Labels

    parityupstream-parityTrack parity risks tied to upstream Apache PDFBox issues

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions