#pdflite

flowchart LR
  Bytes[PDF bytes] --> Reader[pdf_read_document_from_bytes]
  Reader --> Document[PdfDocument]
  Document --> Pages[page tree and resources]
  Document --> Objects[object table]
  Pages --> Content[content operators]
  Objects --> Writer[pdf_write_document]
  Content --> Writer
  Writer --> BytesOut[PDF bytes]

#Native CLI

moon run --target native cmd/pdflite -- info fixtures/camlpdf/logo.pdf
moon run --target native cmd/pdflite -- info --json fixtures/camlpdf/logo.pdf
moon run --target native cmd/pdflite -- validate fixtures/camlpdf/logo.pdf
moon run --target native cmd/pdflite -- rewrite fixtures/camlpdf/logo.pdf _build/logo-roundtrip.pdf
moon run --target native cmd/pdflite -- merge _build/combined.pdf cover.pdf chapter-1.pdf appendix.pdf

moon run --target native --release --build-only cmd/pdflite
PDFLITE_CLI="$PWD/_build/native/release/build/moonbitlang/pdflite/cmd/pdflite/pdflite.exe" \
PDFLITE_LOGO_PDF="$PWD/fixtures/camlpdf/logo.pdf" \
moon cram test --shell /bin/bash --timeout-seconds 120 tests/cram

#Release checks

moon check pdflite
moon test --target native pdflite
moon test --target wasm pdflite

#What This Package Owns

• The public PdfDocument representation and its object table.
• PDF syntax objects such as arrays, dictionaries, streams, names, strings, numbers, booleans, nulls, and indirect references.
• Readers for headers, trailers, classic xref tables, xref streams, object streams, damaged-startxref reconstruction, revisions, and encrypted inputs.
• Writers for classic xref tables, xref streams, compressed xref streams, generated trailer IDs, incremental updates, and encrypted outputs.
• Page-tree construction, page queries, resource renumbering, merge/extract helpers, bookmarks, destinations, annotations, optional content groups, and content stream operators.
• Text/font/image helpers that need the full document graph.

#Pedantic Boundaries

• PDF byte data stays byte-oriented. @core.PdfBytes is Bytes; @core.PdfName and PdfString store raw bytes until an explicit text-decoding API is used.
• Object numbers are one-based in normal document allocation. Missing or deferred objects are represented explicitly instead of being guessed.
• Public parsing and writing APIs raise @core.PdfError for typed failure classes. Tests should assert concrete errors where the input class is stable.
• Methods that mutate a document mutate the in-memory object table directly. Functional wrapper APIs, when present, copy before mutation.
• Encryption APIs distinguish authentication, object crypt filters, saved encryption state, denied permissions, and recryption paths.

#Checked Examples

///|
test "minimum document round trip" {
  let document = try! @pdflite.pdf_minimum_valid_pdf()
  let bytes = try! @pdflite.pdf_write_document(document)
  let version = try! @reader.pdf_read_header_from_bytes(bytes)
  if version.major != 1 || version.minor != 0 {
    fail("expected a PDF 1.0 header")
  }
  let parsed = try! @pdflite.pdf_read_document_from_bytes(bytes)
  inspect(try! parsed.endpage(), content="1")
}

///|
test "name writer escapes delimiter bytes" {
  let name = @core.pdf_name_of_bytes(
    try! @core.pdf_bytes_of_int_array([47, 65, 32, 66]),
  )
  @test.assert_eq(@core.pdf_int_array_of_bytes(@pdflite.pdf_write_name(name)), [
    47, 65, 35, 50, 48, 66,
  ])
}

#Package Notes

• PdfDocument owns the object table, root catalog pointer, trailer dictionary, encryption state, and revision metadata.
• @syntax.PdfObject values preserve PDF syntax-level objects, including byte strings, names, dictionaries, streams, and indirect references.
• Read APIs raise @core.PdfError for malformed input rather than silently repairing data. Reconstruction helpers are explicit APIs.
• Writer APIs can emit classic xref tables, xref streams, compressed xref streams, generated trailer IDs, incremental updates, and encrypted output.

#Verification Notes

• README.mbt.md blocks are blackbox tests for the root package.
• Most root tests should run on all MoonBit targets. Native-only random or file behavior belongs in targeted test files or the async_io package.
• For public API changes, run moon info and review pkg.generated.mbti.
• For behavior changes, run moon test; for native reader/writer coverage, also run native-target tests.