LaTeX Coffee Stains (2021) [pdf]

2 days ago (ctan.math.illinois.edu)

I'm surprised nobody has yet mentioned how pleasant it is to create coffee stains using Typst, and if only LaTeX wasn't the de-facto standard in academia and stain-related journals, they would have already switched to it.

Of course, you can create coffee stains in HTML as well, but it's not something you can do in Markdown.

  • I've been rewriting all my papers in Rust. It's been a pleasant experience getting memory safe coffee stains on my papers.

  • Typst requires a signup? It's web? It says developed in the open, but the main page also offers a login. What can you about latex vs typst?

    • The compiler is open-source and can be run locally. You need an account if you want to use their web editor, which is nice (it shows error messages where they occur along with an explanation and link to docs, and also shows a real-time updated preview).

      As for Latex vs Typst, as a language Typst is much better, compiles very quickly, and has sane error messages. However, Typst still has a few rough edges, and can't do everything you can with Latex + packages (yet).

      I've been using Typst for most of my documents for a few months and I've been generally happy with it.

      1 reply →

    • I have never really used the web thing personally. I always use the command line version, and it works perfectly fine and it's FOSS.

      I find the syntax to Typst to be generally better than LaTeX. I don't like its equations as much, but Typst has one huge advantage that makes it easier to forgive its faults: it compiles several orders of magnitude faster than LaTeX. This might not sound like much but it honestly sort of changes how you even think about problems. I keep Neovim open on the left, run `typst watch` in the background, and Evince on the right, and my updates show up immediately upon saving.

      Also, adding plugins and libraries is trivial. All you have to do is declare it at the top of the file and it will automatically fetch it, which is considerably easier than LaTeX.

      I don't like the default font it ships with, but it's easy enough to add a Latin Modern font and get something that looks like LaTeX.

      Before Typst, I had typically been using Pandoc with Markdown to write my documents, and that served me well for quite awhile, but it had the disadvantage of being extremely slow to compile. A slide deck that I gave last year [1] would take a bit more than a minute to compile. This became an issue because I had to make a few small last-minute changes and having to wait an entire minute to view them actually made it so I was really pushing against the wire.

      If I had done my slides in Typst, they would have compiled in about 40 milliseconds, they wouldn't have looked any worse, and I'd have a syntax not dissimilar to Markdown. I'm pretty much a convert at this point.

      [1] https://git.sr.ht/~tombert/lambda_days_2025

    • No. Typst is an open source application.

      There is a very prominent web site that offers a hosted version without much clarity about the fact that you can run it yourself. The hosted version offers collaborative editing similar to what Overleaf provides which is incredibly useful.

      See https://github.com/typst/typst for the CLI version

      There is a page with pre-compiled binaries as well and on Macs, you can install using homebrew.

    • Typst is an application you can use on your local machine without any signup. The compiler is hosted on GitHub. The Typst web app (the online editor at typst.app) is closed source and offered as a paid with cloud storage, collaboration, autocomplete, etc...

    • You can start using typst by installing it using rust tooling (that's one way to install it): `cargo install typst-cli`

      Or install it using vscode's extensions, or install it for neovim using mason. That's a few commonly used distribution paths.

  • I came here to say this! I switched to Typst a couple of months ago and won't be going back.

Everybody knows that coffee stains are the only surefire way to tell whether a paper has been read or just printed out and ignored. A colleague in uni (way back in early 00s) would add these to her documents every once in a while to give them the "has been read" stamp of approval.

This looks nice, but it is just placing some pre-defined vector files. I wonder if it could be possible to procedurally generate realistic coffee stains.

Love this. My resume has been in LaTeX for over 20 years now.

Underappreciated IMHO. You can version control it, no dealing with wild Word shenanigans. Totally deterministic. Just find a style, insert your bullets and you have a nice sharable PDF.

Nowadays you can even have your preferred LLM do the conversion for you. LaTeX is finicky and I've had it fix warnings in mine that I couldn't be bothered to.

Good stuff, highly recommend a LaTeX resume, whether or not you drink coffee.

Not drinking coffee is the only reason I’ve ever felt truly excluded at a software company. Everyone loves their coffee!

  • I'm in the same boat; I can pretend with tea but it's not really the same experience.

    Diet soda sometimes works, but often isn't provided as easily.

  • You need to go all-in on tea and make your own mark. Get a fancy Chinese teapot with holes in the spout to use loose leaf tea, and start getting snobby about traditional vs modern techniques of Pu'er tea, and you'll get your own brand of respect!

This is wonderful to see. I was a student and then entered into the tech industry in the mid 90's and at that time the Internet had fun whimsical things like this almost weekly.

  • Obviously this was whimsical when it came out. However...we were creating synthetic data for training and testing OCR in multiple scripts. We would take a web page in some language with a non-Roman script, and reproduce it as multiple PDFs using different fonts. We also added various kinds of blurring, using ImageMagick and---of course---this very coffee stains program!

Half done job or just a starting point! We need also:

* tea strains

* bread crumbles (squashed among paper leaves)

* tomato sauce drops

* hair

> A lot of time can be saved by printing [extra stuff] directly on the page rather than adding them manually!

I'm happy this is public domain. In 2023 I used the stain images as the basis for a CTF challenge (for BSidesSF). The encoded flag given to participants was https://github.com/BSidesSF/ctf-2023-release/blob/main/alien...

Unfortunately the challenge was a bit too hard and went unsolved during the competition.

  • It's hard to imagine a reason for it being kept... proprietary?

    • A lot of people want to slap licenses on things without really thinking about what the license will do (or prevent), in practice.

      I like the author's note about the license: "As we do not believe in imaginary property, this package belongs to the public domain."

      I think it's much more common to see a Creative Commons license on this sort of thing.

      1 reply →

Coffee stains should look like water color paints. The fluid deposits pigment more at dry boundaries as evaporation and absorption approach equilibrium.

Reminds me of Windows 3.11 programs that would add random "coffee stains" to your "desktop" "wallpaper"

To save our children in the academia, we need a "Rewrite In Typst" movement, the equivalent of rewrite in rust!

  • If only they had stuck with latex maths syntax instead of inventing their own, I would have switched ages ago and encouraged others to do the same...

  • Nearly all academia uses MS-OFFICE instead of TeX insanity. Only hardcore phds use it really

  • There’s a bit of resistance sadly. My supervisor is “forcing” me to use LaTeX for my MSc thesis sadly.

I think it would be cool to see a version for epub 3.3, which is mostly html/xhtml with some limitations

"This page was intentionally left blank" is also an all time favorite of mine.

  • There’s an old story about that. Possibly apocryphal, but here goes:

    IBM mainframes used to come with documentation in ring binders. Some pages might indeed be marked “This page intentionally blank”. And they would from time to time send out update packages to their customers, with instructions to replace pages so-and-so with the included replacements. On the replacement pages, text that had been altered would be marked with a change bar in the margin.

    Lo and behold, one day an update package was received, replacing one completely blank page with one bearing the text “This page intentionally blank”. Complete with a change bar in the margin.