This presentation is a technical journey into the architecture of map engine typography, contrasting industry-standard methods with Navara’s custom approach.

The talk is structured in three parts:

• The Problem (Why Map Text is Hard): A quick look at the unique constraints of GIS typography, why map text is uniquely difficult compared to standard UI text
• The PBF Paradigm & Its Pitfalls: We will break down how standard vector engines serve fonts via the SDF/PBF pipeline. I will explain why this "pre-baking" method was historically necessary, but also why it falls short today—specifically regarding network bloat for large character sets and the inability to properly handle Complex Text Layouts (CTL) dynamically.
• The Navara Solution: We will pop the hood on Navara's rendering engine to show how we bypassed the PBF bottleneck entirely. I will detail our alternative architecture for loading fonts, executing client-side text shaping, and sending text to the GPU on the fly, sharing the performance trade-offs and lessons we learned along the way.