{"slug": "tectonic", "name": "Tectonic", "category": "other", "category_name": "Other software", "description": "", "recommenders": 4, "commenters": 4, "warners": 0, "score": 3.58, "rising": -1.31, "first": "2026-03-03", "latest": "2026-06-12", "why": "that's what I use personally for local PDF generation", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 4, "neutral": 0, "compare": 0, "warn": 0}, "spark": [0, 0, 0, 0, 1, 0, 1, 2, 0, 0, 0, 0], "listed": true, "loved": [], "caveat": "", "short_quote": "that's what I use personally for local PDF generation", "icon": true, "domain": null, "github_repo": "github.com/tectonic-typesetting/tectonic", "official_url": "https://tectonic-typesetting.github.io", "pricing": "", "aliases": ["Tectonic"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 776216786, "item_id": 48513549, "url": "https://news.ycombinator.com/item?id=48513549", "by": "xvilka", "date": "2026-06-12", "stance": "recommend", "quote": "Projects like Tectonic would solve this for TeX", "excerpt": "I have been using TeX/LaTeX for ages and today same issues hinder the user experience like multiple decades ago - cryptic error messages, complex pipeline, lack of the proper Unicode symbols support out of the box, and so on. Nowadays, with Typst existing, it's vital for TeX ecosystem to solve these issues, since none of them are present in Typst. Projects like Tectonic would solve this for TeX, but they lack enough ", "context": "", "use_case": "TeX engine", "switched_from": "", "story": "Tectonic: A modernized, complete, self-contained TeX/LaTeX engine"}, {"id": 775491312, "item_id": 48468207, "url": "https://news.ycombinator.com/item?id=48468207", "by": "maxloh", "date": "2026-06-09", "stance": "recommend", "quote": "Tectonic is forked from the XeTeX TeX engine.", "excerpt": "Background of the project: Tectonic is forked from the XeTeX TeX engine. However, the build process for XeTeX (and all other mainstream TeX engines) is extremely baroque: 1. The original Knuth sources are written in a language called WEB (which is basically used by nobody else) 2. Those sources are then patched with a series of \u201cchange files\u201d due to restrictions on distributing modified sources 3. These patched files", "context": "", "use_case": "TeX/LaTeX typesetting", "switched_from": "", "story": "Tectonic: A modernized, complete, self-contained TeX/LaTeX engine"}, {"id": 768839600, "item_id": 48052475, "url": "https://news.ycombinator.com/item?id=48052475", "by": "nixpulvis", "date": "2026-05-07", "stance": "recommend", "quote": "that's what I use personally for local PDF generation", "excerpt": "I'm not sure how much overlap there is between this project and Tectonic [1], but that's what I use personally for local PDF generation, and it's also using a good bit of Rust. Just thought I'd mention since it's related and I really like the project. [1] https://github.com/tectonic-typesetting/tectonic", "context": "", "use_case": "local PDF generation", "switched_from": "", "story": "RaTeX: KaTeX-compatible LaTeX rendering engine in pure Rust"}, {"id": 755843232, "item_id": 47240202, "url": "https://news.ycombinator.com/item?id=47240202", "by": "Johnny_Bonk", "date": "2026-03-03", "stance": "recommend", "quote": "I have a claude skill using tectonic I believe and it works pretty well", "excerpt": "When you say consistently render what do you mean? Like without any sort of formatting issue? If thats the case I would lower your expectations a bit almost always as with any bit of copy editing regardless of using ai or not theres going to be issues to review. I have a claude skill using tectonic I believe and it works pretty well, and then I wrote hooks to make sure if certain things are going to be written it doe", "context": "", "use_case": "compiling LaTeX via Claude skill", "switched_from": "", "story": "Ask HN: What prompt do you use to get Claude to consistently render LaTeX?"}]}], "caveats": [], "who": [], "tags": [], "use_cases": ["tex engine", "tex/latex typesetting", "local pdf generation", "compiling latex via claude skill"], "compared": [], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=48467697", "title": "Tectonic: A modernized, complete, self-contained TeX/LaTeX engine", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=48010729", "title": "RaTeX: KaTeX-compatible LaTeX rendering engine in pure Rust", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47238785", "title": "Ask HN: What prompt do you use to get Claude to consistently render LaTeX?", "mentions": 1}], "sentiment_by_month": {"2025-11": {}, "2025-12": {}, "2026-01": {}, "2026-02": {}, "2026-03": {"recommend": 1}, "2026-04": {}, "2026-05": {"recommend": 1}, "2026-06": {"recommend": 2}, "2026-07": {}, "2026-08": {}, "2026-09": {}, "2026-10": {}}, "quotes": [{"id": 776216786, "item_id": 48513549, "url": "https://news.ycombinator.com/item?id=48513549", "by": "xvilka", "date": "2026-06-12", "stance": "recommend", "quote": "Projects like Tectonic would solve this for TeX", "excerpt": "I have been using TeX/LaTeX for ages and today same issues hinder the user experience like multiple decades ago - cryptic error messages, complex pipeline, lack of the proper Unicode symbols support out of the box, and so on. Nowadays, with Typst existing, it's vital for TeX ecosystem to solve these issues, since none of them are present in Typst. Projects like Tectonic would solve this for TeX, but they lack enough ", "context": "", "use_case": "TeX engine", "switched_from": "", "story": "Tectonic: A modernized, complete, self-contained TeX/LaTeX engine"}, {"id": 775491312, "item_id": 48468207, "url": "https://news.ycombinator.com/item?id=48468207", "by": "maxloh", "date": "2026-06-09", "stance": "recommend", "quote": "Tectonic is forked from the XeTeX TeX engine.", "excerpt": "Background of the project: Tectonic is forked from the XeTeX TeX engine. However, the build process for XeTeX (and all other mainstream TeX engines) is extremely baroque: 1. The original Knuth sources are written in a language called WEB (which is basically used by nobody else) 2. Those sources are then patched with a series of \u201cchange files\u201d due to restrictions on distributing modified sources 3. These patched files", "context": "", "use_case": "TeX/LaTeX typesetting", "switched_from": "", "story": "Tectonic: A modernized, complete, self-contained TeX/LaTeX engine"}, {"id": 768839600, "item_id": 48052475, "url": "https://news.ycombinator.com/item?id=48052475", "by": "nixpulvis", "date": "2026-05-07", "stance": "recommend", "quote": "that's what I use personally for local PDF generation", "excerpt": "I'm not sure how much overlap there is between this project and Tectonic [1], but that's what I use personally for local PDF generation, and it's also using a good bit of Rust. Just thought I'd mention since it's related and I really like the project. [1] https://github.com/tectonic-typesetting/tectonic", "context": "", "use_case": "local PDF generation", "switched_from": "", "story": "RaTeX: KaTeX-compatible LaTeX rendering engine in pure Rust"}, {"id": 755843232, "item_id": 47240202, "url": "https://news.ycombinator.com/item?id=47240202", "by": "Johnny_Bonk", "date": "2026-03-03", "stance": "recommend", "quote": "I have a claude skill using tectonic I believe and it works pretty well", "excerpt": "When you say consistently render what do you mean? Like without any sort of formatting issue? If thats the case I would lower your expectations a bit almost always as with any bit of copy editing regardless of using ai or not theres going to be issues to review. I have a claude skill using tectonic I believe and it works pretty well, and then I wrote hooks to make sure if certain things are going to be written it doe", "context": "", "use_case": "compiling LaTeX via Claude skill", "switched_from": "", "story": "Ask HN: What prompt do you use to get Claude to consistently render LaTeX?"}]}