# latex Published articles for latex. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Typst 0.15 adds variable fonts, MathML, and multiple bibliographies DevFeed: [Typst 0.15 adds variable fonts, MathML, and multiple bibliographies]() Original publisher: [Read original article]() Author: jake Published: 2026-09-09T15:37:55Z Content type: news Language: en Sources: [LWN.net]() Topics: [Typst](), [pdf](), [SVG](), [Variable Fonts](), [LaTeX](), [Rust]() Tags: [apache](), [features](), [fonts](), [latex](), [new-features](), [open-source](), [pdf](), [rust](), [variable-fonts]() ### AI overview Typst 0.15 adds support for variable fonts, MathML, multiple bibliographies, and other features. The article examines variable-font support and demonstrates it with Roboto Flex and Zycon. ### Source excerpt Typst is a system for typesetting documents into various formats: PDF, SVG, PNG, and, in progress, HTML. It is adept at handling technical material, and is often considered to be an eventual LaTeX replacement. We last looked in on Typst a year ago, when it had reached version 0.13. A new version, 0.15, was released in June with lots of new features, including support for variable fonts, MathML, multiple bibliographies, and more. Typst is free, Apache-2.0-licensed software, programmed in Rust. ## Logic for Programmers is Done DevFeed: [Logic for Programmers is Done]() Original publisher: [Read original article]() Author: Hillel Wayne Published: 2026-07-29T15:43:52Z Content type: release Language: en Sources: [Newsletter feed for Hillel Wayne's Newsletter]() Topics: [Publishing](), [LaTeX]() Tags: [announcement](), [blog](), [book](), [free](), [latex](), [typography]() ### AI overview Logic for Programmers has reached version 1.0 and is available in print. Early ebook buyers can download the completed edition for free through Leanpub. ### Source excerpt It's done. Logic for Programmers is now 1.0 and available in print. Full announcement here, official website here, direct Amazon link here. If you got an early version of the ebook, you can go back to leanpub to download the 1.0 for free. This marks the completion of a project that took five years of work, six bookwriting professionals, fourteen domain experts, and fifteen public alphas. This has been, without a doubt, the biggest and most exhausting project I've ever done. The examples in the discarded drafts alone could make a second book. The cursed knowledge I've gained on LaTeX and typography could fill a third (or at least a couple of entertaining blog posts). Self-publishing was simultaneously the worst and best decision I made. Now excuse me I am going to sleep for a month. ## Points are a weird and inconsistent unit of measure DevFeed: [Points are a weird and inconsistent unit of measure]() Original publisher: [Read original article]() Author: Hillel Wayne Published: 2026-05-13T15:56:37Z Content type: opinion Language: en Sources: [Newsletter feed for Hillel Wayne's Newsletter]() Topics: [LaTeX](), [TeX]() Tags: [articles](), [latex](), [technology]() ### AI overview The author investigates why a 10.8pt x 7.2pt grid differs between LaTeX and Inkscape. The article explains that point definitions varied historically and that TeX uses a slightly different point size from the official printer's point. ### Source excerpt I'm in the middle of redoing the Logic for Programmers diagrams and this has surfaced a really annoying problem. The book is formatted in LaTeX using a pseudo-grid of 10.8pt x 7.2pt. The diagrams are done in Inkscape using a 10.8pt x 7.2pt. Last week I found out that these are not the same points. Latex defines a point as 1/72.27 inches (0.3515 millimeters). Inkscape instead uses 1/72 inches (0.3528 mm). It's only a difference of 0.4% but it still floors me that two widespread digital technologies would be different! So, uh, what happened? A few hours of reading articles later, this is what I found, caveat that I didn't spend all that much time researching this and this is only initial impressions. what even is a point A point is a typographic measure, coming from 1517, that is supposedly the smallest interesting size for a printer. This was notably not a standardized measure- different companies in times used different point sizes depending on their equipment. Over time it was standardized, but each country picked a different standard: the German and Japanese point is 0.250 mm, the French point is allegedly 0.399 mm, etc. But early computer history is super Americentric so that's what technology uses. In the US, they standardized the point around the end of the 19th century. To what? I dunno. This source from 1900 gives the length of a point as 35/996 cm (72.281 points/in) and then says there are exactly 867.4699 "ems per foot" (72.289 points/in). This source from 1916 says the standard pica (12 points) is 0.16604 inches and that there are 72.272 "pica ems per foot". Which conveniently enough gives us 72.272 points/in (a pica being 12 points). Then on the very next page they say no a pica is actually 0.166044 inches and a point is exactly 0.013837 inches. I found other sources with other definitions, too. I'm going to chalk the differences up to a mix of "the definitions of 'meter' and 'foot' changed over time" and "these are less than a micron apart so who gives a ## MDN 2024 content projects DevFeed: [MDN 2024 content projects]() Original publisher: [Read original article]() Author: vadim-makeev Published: 2025-01-08T00:00:00Z Content type: article Language: en Sources: [MDN Blog]() Topics: [Documentation](), [Web platform](), [HTTP](), [XML](), [Accessibility](), [LaTeX](), [math](), [HTML](), [Markdown]() Tags: [2025](), [accessibility](), [docs](), [html](), [http](), [latex](), [markdown](), [math](), [web-platform]() ### AI overview MDN Web Docs reviews its 2024 content projects, describing audits and updates to popular but outdated or incomplete material. The work focused on HTTP, MathML, and web Manifests, with particular detail on improved MathML documentation, examples, LaTeX annotations, browser compatibility data, and accessibility information. ### Source excerpt Let's have a look at MDN Web Docs content projects in 2024, with highlights of our top picks and recommended reading, and at what's next on MDN for 2025. ## Product Update - August 2023 DevFeed: [Product Update - August 2023]() Original publisher: [Read original article]() Author: Joshua Kim Published: 2023-08-31T00:00:00Z Content type: release Language: en Sources: [Mintlify Blog]() Topics: [Command-line interface](), [Documentation](), [LaTeX]() Tags: [announcements](), [cli](), [documentation](), [icons](), [improvements](), [latex](), [mobile](), [product](), [update]() ### AI overview Mintlify's August 2023 product update introduced CLI v4 with local preview capabilities and faster page loads, along with documentation feedback configuration, LaTeX support, mobile header copying, and expanded icon integration. ### Source excerpt In August, we brought a range of improvements and expansions to our platform, including our CLI v4, documentation feedback, LateX support, copying headers from mobile, and icon add-ins. ## Computations that differentiate, debug, and document themselves DevFeed: [Computations that differentiate, debug, and document themselves]() Original publisher: [Read original article]() Author: Aditya Srinivasan Published: 2022-11-17T00:00:00Z Content type: article Language: en Sources: [Jane Street]() Topics: [Optimization](), [debugging](), [OCaml](), [LaTeX](), [Programming]() Tags: [debug](), [latex](), [ocaml](), [optimization](), [programming]() ### AI overview Jane Street describes a library for numerical computations that can evaluate values, automatically differentiate variables, inspect intermediate results for debugging, and generate LaTeX documentation. The library was designed for computations expressed naturally in OCaml and for the needs of Jane Street's production systems. ### Source excerpt One of the problems we wrestle with at Jane Street is how to understand and manage the costs associated with the positions we hold: things like margin, financing costs, market risk, regulatory capital requirements, and so on. To that end, we've built systems that estimate these costs and propose ways to reduce them. Essentially, this is a numerical optimization problem. ## A Working Mathematician's Guide to Parsing DevFeed: [A Working Mathematician's Guide to Parsing]() Original publisher: [Read original article]() Published: 2019-04-20T17:51:51Z Content type: tutorial Language: en Sources: [Jeremy Kun]() Topics: [Parsing](), [LaTeX](), [Programming](), [Code](), [syntax]() Tags: [code](), [guide](), [latex](), [parsing](), [programming](), [regular-expressions](), [syntax]() ### AI overview This tutorial explains how to convert LaTeX math delimiters for a blog platform when simple find-and-replace is insufficient. It introduces text manipulation approaches, including regular expressions and a program built from scratch, using basic Python or Perl tools. ### Source excerpt Our hero, a mathematician, is writing notes in LaTeX and needs to convert it to a format that her blog platform accepts. She's used to using dollar sign delimiters for math mode, but her blog requires \( \) and \[ \]. Find-and-replace fails because it doesn't know about which dollar sign is the start and which is the end. She knows there's some computer stuff out there that could help, but she doesn't have the damn time to sort through it all. ## An Overview of the TeX and LaTeX Ecosystem DevFeed: [An Overview of the TeX and LaTeX Ecosystem]() Original publisher: [Read original article]() Author: Joway Published: 2018-05-13T00:00:00Z Content type: tutorial Language: zh Sources: [Random Thoughts]() Topics: [LaTeX](), [TeX](), [Programming]() Tags: [latex](), [programming](), [tech]() ### AI overview An overview of the TeX typesetting system and the roles of TeX engines, LaTeX macro collections, packages, and Chinese-language support. ### Source excerpt 最近在使用 LaTeX 写作，发现虽然这个「软件」使用简单，设计简约，但使用起来却并不是非常的容易，加上其生态非常芜杂，各种宏包和发行版层出不穷，中文世界鲜有文章系统地去讲他们之间的关系。这篇文章不会去介绍其基本用法，而是以一个更为宏观的角度，旨在厘清 TeX 排版系统的来龙去脉，以及其生态圈中各个项目的作用与关系。或有纰漏，还望雅正。 ## From boiling lead and black art: An essay on the history of mathematical typography DevFeed: [From boiling lead and black art: An essay on the history of mathematical typography]() Original publisher: [Read original article]() Author: Eddie Smith Published: 2017-10-13T00:00:00Z Content type: opinion Language: en Sources: [Eddie Smith]() Topics: [Mathematics](), [Data visualization](), [LaTeX](), [Microsoft]() Tags: [data-visualization](), [essay](), [history](), [latex](), [microsoft](), [typography]() ### AI overview An essay on the history and craft of mathematical typography, explaining why mathematical typesetting is more difficult than ordinary text and reflecting on the advantages and limitations of modern tools such as Microsoft Word and LaTeX. ### Source excerpt Math fonts from six different type systems, courtesy Chalkdust I've always felt like constructing printed math was much more of an art form than regular typesetting. Someone typesetting mathematics is less a "typist" and more an artist attempting to render abstract data on a two-dimensional surface. Mathematical symbols are themselves a language, but they are fundamentally a visual representation of human-conceived knowledge--knowledge that would be too inefficient to convey through verbal explanations. This brings the typesetting of mathematics closer to a form of data visualization than regular printed text. No matter how hard it's ever been to create printed text, creating printed math has always been even harder. In pre-digital times, equation-laden texts were known as "penalty copy" because of the significant additional time and expense it took to set math notation for printing presses. Even when modern word processors like Microsoft Word include equation editors, they tend to be difficult to use and often produce unpleasing results. While LaTeX and similar variants produce the highest quality digital math type, these frameworks also have much more of a learning barrier than general word processing. But these modern quibbles are much more the fault of hedonic adaption than any of the tools available to us today. We have it vastly easier than any previous stage of civilization, and I think it's critically important for those of us that write math to have at least a basic awareness of the history of mathematical typesetting. For me, knowing this history has had several practical benefits. It's made me more grateful for the writing tools I have today--tools that I can use to simplify and improve the presentation of quantitative concepts to other actuaries. It's also motivated me to continue to strive for elegance in the presentation of math--something I feel like my profession has largely neglected in the Microsoft Office era of the last twenty years. Most importantl ## Foobar, Blossoms, and Isomorphism DevFeed: [Foobar, Blossoms, and Isomorphism]() Original publisher: [Read original article]() Author: yifanlu Published: 2017-09-13T07:00:00Z Content type: tutorial Language: en Sources: [Yifan Lu]() Topics: [Programming](), [Code](), [Google]() Tags: [algorithm](), [computer-science](), [foobar](), [google](), [guards](), [latex](), [math](), [number-theory](), [programming](), [technical]() ### AI overview A detailed solution to Google Foobar's "Distract the Guards" problem. The article models when two guards enter an infinite loop and explains how maximum matching can pair the greatest possible number of guards into such loops. ### Source excerpt A friend recently invited me to participate in Foobar, Google's recruiting tool that lets you solve interesting (and sometimes not-so-interesting) programming problems. This particular problem, titled "Distract the Guards" was very fun to solve but I found no good write-ups about it online! Solutions exist but it is rather hard to understand how the author came upon the solution. I thought I might take a shot and go into detail into how I approached it-as well as give proofs of correctness as needed. ## Choosing Checklist Tools for Different Tasks DevFeed: [Choosing Checklist Tools for Different Tasks]() Original publisher: [Read original article]() Author: Eddie Smith Published: 2017-07-25T00:00:00Z Content type: opinion Language: en Sources: [Eddie Smith]() Topics: [App](), [Tool](), [file](), [LaTeX]() Tags: [apple](), [application](), [apps](), [file](), [files](), [latex](), [mac](), [tasks](), [templates](), [tools]() ### AI overview The article argues that no single checklist tool is best for everyone. The appropriate format depends on the task and whether users need to track both unfinished and completed items. It discusses spreadsheets, OmniOutliner, Apple Notes, Drafts, and file-organization methods for different uses. ### Source excerpt Gabe whipped up a great list of checklist tools. My favorite aspect of his post is that there's no clear winner. There shouldn't be. Checklists can come in all forms, and the ideal format depends entirely on the application. For me, checklists make sense when I need to see not only what needs to be done, but also what I've already done. Apps that automatically "vanish" completed tasks fail to do the latter. For me, sometimes there's just no substitute for a spreadsheet for large checklists, especially if each item can have multiple statuses or dimensions. Sometimes adding more columns is way more efficient than adding more tasks (rows). For packing lists, I've tried so many apps, but OmniOutliner is the best for me. It's simple checkbox feature is perfect, and I have several templates I use for different types of trips. Sometimes an Apple Note will suffice, and sometimes I just "x" lines in Drafts for a quick and dirty grocery list. When I'm working with large numbers of LaTeX files on my Mac, I use file colors, prefix schemes, and even moving files from one folder to another to keep what I've processed and what I haven't. Checklists are as old as civilization and are one of the most fundamental ways to augment the human mind, which needs help seeing where it's been and where it needs to go. Everyone can benefit from checklists. Just check out The Checklist Manifesto. ## A couple of Jekyll updates DevFeed: [A couple of Jekyll updates]() Original publisher: [Read original article]() Author: Eddie Smith Published: 2017-07-02T00:00:00Z Content type: tutorial Language: en Sources: [Eddie Smith]() Topics: [Jekyll](), [Markdown](), [CSS](), [YAML](), [HTML](), [LaTeX]() Tags: [css](), [html-elements](), [jekyll](), [latex](), [markdown](), [yaml]() ### AI overview A personal update on a Jekyll site that adds image captions with CSS and Markdown, and integrates MathJax selectively through YAML front matter while retaining the kramdown converter. ### Source excerpt Since moving to Jekyll last year, I've done relatively little to tweak the inner workings of this site. After all, one of the most appealing things about having a static site is that it doesn't need to have a lot of moving parts. It just works. But today I finally got around to a couple of housekeeping items that have been on my list: image captions and MathJax. Image captions For image captions, I settled on a beautifully simple solution posted by Andrew Wei on Stack Overflow: *image_caption* This takes advantage of the fact that you can create CSS for combinations of HTML elements. In this case, I can use img + em { display: block; text-align: center;} to target the *image_caption* text only and center it under images, which are also centered on this site by default. It works perfectly, and this isn't even Jekyll-specific. Anyone publishing in Markdown could do this. Agreed. Jekyll + MathJax Adding MathJax took a little more time, but not much. It was worth it just to remind me of the brilliance of Jekyll's architecture. Even though the Jekyll site mentions MathJax, it doesn't say enough to be of immediate use. It basically points to a blog post that entails switching from the default kramdown Markdown converter to redcarpet. Given that I'm happy with kramdown and not in the mood to backtest a bunch of blog posts with a different converter, I wanted to stick with kramdown. A series of subsequent web searches lead me to a Github issue thread for a Jekyll theme that I'm not even using, but I found a really efficient implementation of MathJax there by user "mmistakes," who suggested adding a mathjax variable in each page's YAML front matter that could be set to true on a post by post basis. The elegance of this solution is that the MathJax script will only be written into the HTML of posts that actually have MathJax in them. This seemed super appealing to me because it meant that I didn't have to worry about MathJax being triggered by some accident