2020 ·English ·14 slides ·420 views

PrintCSS W3C workshop at XMLPrague 2020

1. Andreas Jung is a freelance consultant and developer who founded the print-css.rocks project in 2016 to provide vendor-neutral information about PrintCSS. 2. There are many incomplete and missing parts of the PrintCSS standard including issues with table splitting, floating, images, and support for JavaScript and multi-column layouts. 3. Key missing features from the standard include CSS exclusions, named page floating, hyphenation dictionaries, auto-sizing text to containers, consistent sidenote positioning, and tests to ensure consistent rendering behavior across tools.

Source PDF 1.4 MB Slide text

Slide 1 of 14 — PrintCSS W3C workshop at XMLPrague 2020

1/14 arrow keys or swipe · click image for fullscreen

Details

Uploaded: 13 February 2020
Updated: 19 November 2022
Language: English
Slides: 14
Image size: 2048x1448
Views: 420
SlideShare ID: 227858998
Uploaded format: PDF
Collected: 2026-09-27

The description above is SlideShare's automatically generated summary, not the author's own text.

Source & completeness

Content: original + reconstructed
Validation: passed
Slide text: available (14 slides)
Original files: yes

original.pdf PDF · 1.4 MB · 14 slides

Checksums (SHA-256)

original.pdf: 8f4586bef84a630395a04072538e2422ade96cb60f2c16c9f7aeb90815f363a9

Slide images come from SlideShare's public renderings (2048x1448 px, WebP). Any file marked as reconstructed is assembled from those images and is not the author's original source file.

Full text of every slide

Text extracted by SlideShare from the slide images — may contain OCR errors. 14 of 14 slides have text.

PrintCSS The missing parts. The bad parts. Andreas Jung (ZOPYX) info@zopyx.com www.print-css.rocks W3C PrintCSS Workshop @XMLPrague 2020 1 https:!//cutt.ly/jrIh5TI

ANDREAS JUNG ‣ background in electronic publishing since 1995 ‣ freelancer and independent consultant since 2004 ‣ large scale content management based on Plone CMS ‣ individual Python software development ‣ electronic publishing solutions ‣ founder of print-css.rocks project (2016?) 2

‣ vendor-neutral information about "PrintCSS" ‣ information about tools ‣ tested tools: ‣ PrinceXML ‣ Antennahouse ‣ PDFreactor ‣ WeasyPrint ‣ tutorial and lessons ‣ "PrintCSS" related resources 3

LESSONS 4

CONVERTER RESULTS 5

HTML INPUT 6

CSS INPUT 7

THE "STANDARD" (1/2) ‣ Draft: CSS Paged Media Module Level 3 (2018) ‣ Draft: CSS Generated Content for Paged Media Module (2014) ‣ various CSS Level 2-4 drafts and standards ‣ status of some drafts unclear (unmaintained, work-in-progress, discontinued?) ‣ many vendor speciﬁc extensions (development usually driven by customer needs) ‣ limited cross-platform compatibility and interoperability 8

THE "STANDARD" (2/2) ‣ conﬂicting implementations ‣ conﬂicting interpretations of the "standard" ‣ missing test suites ‣ adaptation of new CSS standards ‣ browsers: fast ‣ PrintCSS tool: slow 9

THE INCOMPLETE PARTS ‣ 🚫 table splits: repeated captions, page breaks within row spans. ‣ 🚫 deﬁciencies with page areas and running elements ‣ 🚫 ﬂoating of block elements is weak and incomplete (many vendor extensions) ‣ 🚫 image positioning, image ﬂoating and adaptive scaling (CSS Figures, Håkon Wium Lie) ‣ 🚫 Javascript support missing or only partly implemented ‣ 🚫 multi-column layouts (CSS Multi-column Layout Module Level 1) ‣ 🚫 consistent ﬂex box and grid support 10

THE MISSING PARTS ‣ 🚫 CSS 3 Exclusions ‣ 🚫 Floating of whole-page block elements to named pages ‣ 🚫 Standard for hyphenation dictionaries and exceptions ‣ 🚫 Auto-sizing of text (general: blocks) to ﬁt into container ‣ 🚫 Sidenotes are a huge mess (positioning, ﬂoating, multi column environments) ‣ 🚫 consistent rendering behavior ‣ 🚫 Tests, tests, tests 11

DEVELOPER EXPERIENCE WITH PRINTCSS ‣ 🚫 no professional development tools ‣ 🚫 rendering process is a blackbox process ‣ 🚫 no/few tracing/introspection options on the rendering process ‣ 🚫 lengthy trial-and-error development ‣ 🚫 no inﬂuence on the rendering process besides CSS 12

THE ECOSYSTEM ‣ CSS Paged Media tools: ‣ few commercial tools ‣ even fewer non-commercial, free tools ‣ limited options ‣ in-depth evaluation needed for advanced projects ‣ at one point you need to decide and pick one tool 13

#sigh 14