Posts tagged i18n
Sphinx Translation Tutorial: Localize Your Docs Like a Pro on Sep 01, 2025
Localizing documentation, manual, or help is a challenging task. But it’s also an area where Sphinx documentation generator really shines. Sphinx gives you strong tooling for the entire lifecycle from initial translation to keeping translation(s) up to date with constantly changing original. In this tutorial, I will guide you through the full translation workflow using a minimal yet realistic Sphinx documentation example.
Translating with gettext overview on Oct 15, 2021
Localization with gettext is streamlined process with responsibility distributed among original messages author, gettext tooling, and translator or translator tools. This post will help you understand extracting messages and starting new translation.
Getttext PO/POT format explained on Oct 15, 2021
Gettext is internationalization (i18n) mechanism and library used not only in many software products, programming languages but also for translating Sphinx documentations. Gettext extracts strings marked “to-be-localized” from a source code (or a document) to plain text file with .po or .pot file extension. Let’s look at its format.
