@embedpdf/default-stamps
The standard rubber-stamp library — Approved, Draft, Confidential, Sign Here, … — as one PDF per locale, in Acrobat's own stamp-library dialect:
/Titleis the library name (Standaard stempels)./Names /Pagesregisters every page asidentifier=label(Approved=Goedgekeurd): the identifier becomes a placed stamp's/Name, the label its/Subjand the picker text.- Every page is one vector stamp;
/PieceInfocarries the library id (embedpdf-standard), the locale, and each stamp's kind.
The v3 importer reads everything from the PDF. The same file drops into
Acrobat's Stamps folder and shows up as a library there.
| Locale | File | Name |
|---|---|---|
en | en/stamps.pdf | Standard Stamps |
de | de/stamps.pdf | Standardstempel |
nl | nl/stamps.pdf | Standaard stempels |
fr | fr/stamps.pdf | Tampons standards |
es | es/stamps.pdf | Sellos estándar |
zh-CN | zh-CN/stamps.pdf | 标准印章 |
sv | sv/stamps.pdf | Standardstämplar |
ja | ja/stamps.pdf | 標準スタンプ |
Every locale registers the same 17 identifiers in the same page order; only the labels differ. Import two locales side by side and the plugin keeps them as two libraries with one identity.
Use
import { StampToken } from '@embedpdf/plugin-stamp';
import { loadDefaultLibrary } from '@embedpdf/default-stamps/library';
const stamp = registry.capability(StampToken);
await stamp.importLibrary(await loadDefaultLibrary('nl')); // title, identifiers, labels come from the file
As part of your build
@embedpdf/default-stamps/library delivers each locale through the module
graph — a generated ES module per locale, loaded with a literal dynamic
import — so the library ships as a lazy chunk of your own build. Nothing to
copy, no asset pipeline to configure, no CDN:
import { LOCALES, loadDefaultLibrary } from '@embedpdf/default-stamps/library';
const bytes = await loadDefaultLibrary('nl'); // the PDF; unknown codes fall back to `en`
await stamp.importLibrary(bytes);
The PDFs themselves stay in the package (<locale>/stamps.pdf) for
self-hosting and for Acrobat.
V2 compatibility
Keep each <locale>/manifest.json in every release, including the stable
release. Already deployed v2 viewers request these files from the unversioned
jsDelivr URL for this package, so a major version bump does not isolate them.
The manifests retain v2's library id, categories, stamp ids, localized labels,
and page indexes. Their relative pdf: "stamps.pdf" points to the same PDF
that v3 uses; the new catalog metadata does not change the artwork or page
order that v2 reads.
These manifests are compatibility files for v2, not an input to the v3 loader.
Do not remove or rename them, or reorder PDF pages without preserving the
legacy page-index mapping. The release consume gate runs the stamp-library
tests against the packed npm artifact to verify all eight manifests and their
PDF page mappings before publishing to either next or latest.
Provenance
The artwork is Acrobat's standard stamp set, carried over unchanged from the previous major of this package; only the catalog was added (title, registry, PieceInfo). The stamp plugin's test suite re-imports every shipped file and checks its title, identifiers, and labels.