Beyond the Code Editor: Understanding TeX, LaTeX, and Their Many Flavours

• Introduction (relate to developer audience)
• History/context
• The various "flavors" explained simply
• Why this matters for developers
• Practical guidance

When you're building software, the last thing you want is another layer of complexity. Yet somewhere between your Git repository and that beautifully formatted PDF you're generating, there's a decades-old typesetting system that refuses to fade into obscurity—TeX.

You might encounter it when writing API documentation, contributing to academic papers, or setting up automated build pipelines for technical content. Whatever the context, understanding the TeX family tree can save you hours of frustration and help you make smarter choices about your documentation workflow.

The Origin Story: How It All Began

In the late 1970s, computer science legend Donald Knuth received the galley proofs for Volume 2 of his seminal work, The Art of Computer Programming. The typographic quality was so disappointing that he decided to solve the problem himself. That single moment of dissatisfaction birthed a typesetting system that would define technical publishing for the next four decades—and counting.

Knuth wasn't just building software; he was crafting algorithms for automatic line breaking, hyphenation, and mathematical typesetting that remain remarkably sophisticated by modern standards. He even developed his own font technology called MetaFont to accompany his creation.

Why TeX Still Matters in 2024

Here's the thing that surprises many developers: TeX isn't a relic. It's actively maintained, widely used in academic publishing, and increasingly relevant for anyone producing high-quality technical documentation.

The original TeX engine, often called "Plain TeX," gives you low-level control over every aspect of document formatting. But let's be honest—writing raw TeX is like writing assembly when you could be using a modern language. That's where the derivatives come in.

The Family Flavours, Explained

Think of TeX as an engine, and LaTeX (and the other variants) as different vehicles built around that engine. Here's your cheat sheet:

LaTeX is the most popular TeX derivative—a document preparation system that abstracts away the complexity of raw TeX. Instead of manually controlling every formatting decision, you write structured markup that LaTeX translates into beautifully typeset output. This is what the vast majority of users actually interact with.

pdfLaTeX extends the original TeX engine to produce PDF output directly. For years, this was the standard choice for most use cases, supporting Unicode input and modern font embedding.

XeLaTeX arrived to solve some limitations of pdfLaTeX, particularly around internationalization. It natively supports OpenType fonts and Unicode text, making it far easier to work with multilingual documents or non-Latin scripts. If you're typesetting content with complex character requirements, this is often your best bet.

LuaLaTeX represents the most modern approach, embedding the Lua scripting language directly into the TeX engine. This gives you incredible flexibility for custom document processing, automated workflows, and complex typographic requirements. It's where most new development is happening.

What This Means for Your Stack

At NameOcean, we see developers wrestling with these choices when setting up documentation pipelines, particularly for projects that need to generate consistent PDFs across different platforms and build environments.

A few practical considerations:

For most general-purpose technical documentation, XeLaTeX strikes an excellent balance between modern font support and compatibility with existing LaTeX packages. If you're building multilingual documentation or working with non-Western character sets, the Unicode advantages become essential.

If you need deep customization or are building tooling around your documentation pipeline, LuaLaTeX offers programmatic extensibility that the other engines can't match. The ability to embed Lua scripts directly into your document processing opens up possibilities for dynamic content generation.

pdfLaTeX remains relevant for projects where package compatibility is critical—some specialized academic packages haven't been updated for XeLaTeX or LuaLaTeX. Legacy is a real consideration in the TeX world.

The Bottom Line

You don't need to master every TeX variant to be effective. Understanding the basics—knowing that LaTeX is the layer you'll most often interact with, and that your choice of compiler affects font handling, Unicode support, and PDF generation—is enough to make informed decisions.

The next time you're configuring your documentation build system or collaborating with authors who speak in terms like "XeLaTeX compiler," you'll know exactly what they're referring to. And that's worth more than a PhD in typography.

At NameOcean, we help developers and technical teams build reliable infrastructure for their projects—including the documentation pipelines that keep the world informed. Explore our hosting solutions built for developers, by developers.