Crates.io | pdf-writer |
lib.rs | pdf-writer |
version | 0.12.0 |
source | src |
created_at | 2021-05-22 12:17:32.40139 |
updated_at | 2024-09-30 13:43:08.124295 |
description | A step-by-step PDF writer. |
homepage | |
repository | https://github.com/typst/pdf-writer |
max_upload_size | |
id | 400800 |
size | 2,475,204 |
A step-by-step PDF writer.
[dependencies]
pdf-writer = "0.12"
The entry point into the API is the main Pdf
, which constructs the document
into one big internal buffer. The top-level writer has many methods to create
specialized writers for specific PDF objects. These all follow the same general
pattern: They borrow the main buffer mutably, expose a builder pattern for
writing individual fields in a strongly typed fashion and finish up the object
when dropped.
There are a few more top-level structs with internal buffers, like the builder
for Content
streams, but wherever possible buffers are borrowed from parent
writers to minimize allocations.
The following example creates a PDF with a single, empty A4 page.
use pdf_writer::{Pdf, Rect, Ref};
// Define some indirect reference ids we'll use.
let catalog_id = Ref::new(1);
let page_tree_id = Ref::new(2);
let page_id = Ref::new(3);
// Write a document catalog and a page tree with one A4 page that uses no resources.
let mut pdf = Pdf::new();
pdf.catalog(catalog_id).pages(page_tree_id);
pdf.pages(page_tree_id).kids([page_id]).count(1);
pdf.page(page_id)
.parent(page_tree_id)
.media_box(Rect::new(0.0, 0.0, 595.0, 842.0))
.resources();
// Finish with cross-reference table and trailer and write to file.
std::fs::write("target/empty.pdf", pdf.finish())?;
For more examples, check out the examples folder in the repository.
This crate forbids unsafe code, but it depends on a few popular crates that use unsafe internally.
This crate is dual-licensed under the MIT and Apache 2.0 licenses.