LaTeX uses 1/72.27 inch per point (Knuth’s TeX definition); Inkscape uses 1/72 inch (PostScript/CSS/SVG standard), causing a 0.4% mismatch that breaks precise grid alignment.
Key Takeaways
The typographic point has no single historical origin: US, German, French, and Japanese standards all differ, with the US settling near 0.013837 inches via NIST.
Knuth intentionally redefined the TeX point to make 72.27 pt = 1 inch exactly, a cleaner ratio than the NIST value, at a cost of ~1 part in 10^8.
PostScript defined its unit as 1/72 inch and called it a “point”; Apple’s LaserWriter shipped it, making 72 pt/in the de facto digital standard for CSS, SVG, and Inkscape.
Frink, a units-aware programming language, labels 1/72 inch as computerpoint/postscriptpoint and 0.013837 inch as point, but its texscaledpoint definition is off by ~50 attometers (~3% of a proton width).
draw.io is an outlier SVG editor that uses 1/100 inch as its point size, further fragmenting the landscape.
Hacker News Comment Review
No substantive HN discussion yet; one commenter flagged Frink as worth revisiting for unit-handling tooling, and another made an off-topic joke about units of concern.
Notable Comments
@WillAdams: Recommends just using PostScript (Big) Points as the practical default; flagged Frink as previously unknown and potentially useful for unit-aware tooling.
