Why one PDF is often not enough
A PDF built for fast online reading should not behave exactly like a print-ready file. A lightweight PDF helps users access content quickly, while a print-focused PDF must preserve higher asset quality and stricter production expectations.
What XML JATS enables
- Web PDF: lighter, faster and optimized for digital consultation.
- Print PDF: stronger for professional output, archive needs or institutional delivery.
- Coherence: both outputs derive from the same structured source.
Why this is better than manual duplication
Without a structured source, each PDF variant tends to become its own file history. That creates drift, duplicated corrections and uncertainty about which version is definitive. XML JATS turns PDF into a controlled derivative, not the place where editorial logic gets trapped.
Output strategy
Different publication contexts deserve different PDF behavior
It is not about making more files for the sake of it. It is about generating the right output for each real publishing use case from a single editorial base.
What editorial teams notice
- Fewer PDF-related compromises during issue closure.
- Better control over file weight and visual fidelity.
- More consistent correspondence between web and PDF versions.
- Less repeated correction work.
Conclusion
XML JATS helps journals stop forcing one PDF to do everything. By deriving web and print variants from the same structure, publication becomes cleaner, faster and more dependable.