dompdf renderer
Purpose
Documents are rendered with Chromium in the core. This add-on package provides dompdf as a second engine — for environments where Chromium cannot be run. It is deliberately a separate package and not part of the main delivery.
Scope
- HTML→PDF through dompdf, registered as an engine through the core document interface.
- No loading from the network and no PHP inside the HTML — the engine sees only what it is
handed.
- Access limited to the temp directory.
- DejaVu Sans as the font so umlauts and the euro sign are correct; A4 portrait.
Interplay
The engine is selected through document output of the commerce core. Once installed and selected, documents are produced with it instead of Chromium; everything else about the document — template, number range, delivery route — stays unchanged.
Limits
- Why it is a separate package at all: dompdf is licensed under LGPL-2.1. The main product
ships no dependency of the GPL family. Anyone who needs this engine installs it deliberately and pulls in the licence just as deliberately; the main package stays free of it.
- dompdf can do less than Chromium. Modern layout features are only partly supported; complex
templates look different.
- Without this package and without Chromium no document is produced — one of the two engines has
to be present.