Reach · Clarity · Care

Languages

The Book of 42 is written and published in English first. That is the authoritative voice of the archive, the films, and the chronicle.

Right now

Your browser can translate the site for personal reading. Chrome, Edge, Safari, and many mobile browsers offer Translate page for the whole document.

That is machine translation. Beautiful for access. Not a substitute for a human or carefully reviewed edition of the Book’s voice.

Google Translate vs built-in translation

  • Browser / Google Translate · Instant. Works on most text pages. Does not change the underlying site. Quotes, poems, and mythopoetic lines can blur. Canvas games and images with baked-in English stay English.
  • Built-in (our translation) · We choose languages, review Eros and Logos together, keep curly quotes and seals true, and ship real routes (for example /es, /pt). Best for scale and trust. Takes deliberate work.

What scaling needs

  1. String inventory · Move visible English into message files (nav, footers, game status, archive ledes). Leave primary-source quotes attributed in original English with optional translated gloss.
  2. Locale routes · /es/…, /pt/…, later more. html lang per locale.
  3. Priority languages · Spanish and Portuguese first (Americas + global reach), then others you choose with readers in mind.
  4. What not to auto-translate · Elon’s lines, Isaacson short holds, gematria seals, film voiceover scripts, share-card art with English type.
  5. Privacy · A full Google Translate widget sends page content to Google. We prefer browser-side translate or our own locale files so the portal stays quiet by default. See Privacy.
  6. Games & canvas · Labels and HUD strings become locale messages. Physics and art stay universal.

Until locale editions ship: use your browser’s translate for access. The living English chronicle remains the source of truth.