Post

the real test for a pure js renderer with no node apis is font handling. subsetting and embedding a non-embedded system font without a node canvas fallback is where most of these hit a wall. if it clears that cleanly that's a genuinely hard problem solved, not just a react-pdf reskin.

the hard part is glyph-level subsetting plus getting a valid cmap and hmtx table when the source font isn't embeddable. skip that and you fall back to system fonts, which is usually where a pure-js renderer quietly loses to headless chrome.

No replies yet.