Translation

Every page is written to live in four languages. English sits at the root; Spanish, Catalan and Tagalog mirror it, each under its own prefix. This page is the policy that keeps them in step.

Four locales

English is served at the root with no prefix. Spanish, Catalan and Tagalog each live under their own prefix. Dates and month names format per region — British English, European Spanish, Catalan and Filipino.

Locale Path Language
en (root) English
es /es/ Español
ca /ca/ Català
tl /tl/ Tagalog

What translates, and what does not

Prose, headings, alt text, interface strings and diagram labels are translated. Everything a reader would copy and run is kept exactly: code, terminal commands, file paths, URLs, code identifiers, and brand and product names. A translated post reads in its own language while its git commands and API names stay byte-for-byte the English.

Translated

  • Prose and headings
  • Image alt text
  • Diagram (Mermaid) labels
  • Interface strings

Kept verbatim

  • Code blocks
  • Terminal commands
  • File paths and URLs
  • Code identifiers
  • Brand and product names

Not every post exists in all four languages. Where a translation is missing, that language’s feed shows the English post rather than hiding it, and a first-time visitor to the site root is sent to their browser’s language.

Voice across languages

A translation here is not a word-for-word rendering. Each language is written the way a senior engineer would write it natively: the same structure and the same facts, in its own natural phrasing.

Borrowed words stay

Spanish and Catalan keep the technical English that developers actually use: runtime, bundle, host, remote, build, deploy. Some of these are anglicisms no dictionary would bless, and they stay anyway. Translating runtime as “tiempo de ejecución” is dictionary-correct and reads like a textbook; the goal is to read like a colleague.

Tagalog is Taglish

The Tagalog posts are idiomatic Taglish: Filipino sentence flow with the technical vocabulary left in English, the way Filipino developers talk shop. A fully translated technical Tagalog would be harder to read, not easier.

The same bans travel

The writing rules cross the language barrier, and one gets stricter: the spaced em-dash aside that English prose allows is dropped entirely in translation; Spanish, Catalan and Tagalog reach for a comma, a colon or parentheses instead. Each language also bans its own marketing filler, the local cousins of the English list: in Catalan, for instance, d’avantguarda, sense fissures, holístic and disruptiu are out.

Spotted something wrong on this page? Email me