Translation and Cultural Review Policy

Every interpretation, guide, and calculator explanation is written and edited in English first. Historical claims are checked at the English layer, so a correction made there flows to every language on the next translation pass. No content originates in another language and no meaning is invented during translation.

This also means the English version is the authoritative one: if a translated passage ever seems to say something stronger or stranger than the English, the English text is what we stand behind, and the translation is the bug.

Translations are generated by machine translation models, protected by a curated glossary of terms that must stay consistent (the names of core numbers, for example) and checked by automated audits that catch missing passages, untranslated text, and formatting damage before an update ships.

Machine translation has real limits, and we treat it accordingly: it is how a small team can serve many languages at all, not a claim that every sentence reads like a native wrote it.

When a passage has no translation yet in your language, the site shows the English original rather than a blank space or a broken key. We think a visible fallback is more honest than pretending coverage that doesn't exist — you can always tell what has and hasn't been translated.

Our language statistics work the same way: a language's completion is measured against the real English content, and we only present a language to search engines as fully supported once it passes a completeness threshold.

Before a language is promoted to fully-supported status, a human review of sample pages precedes the switch — checking register, consistent address forms, and terms that machine translation commonly gets wrong. Languages wait in the visible-but-not-promoted state until they pass.

Cultural review matters most on the tradition articles, where a translation error can misrepresent someone's heritage. Reviewers are credited by name on the articles they review; we do not claim reviews that have not happened.

If you find a translation mistake, tell us through the contact page — a screenshot or the page address is enough. Human corrections are stored in a way that protects them from being overwritten by later automated translation runs, so a fix stays fixed.

Corrections that change meaning, not just phrasing, are treated like content corrections and noted accordingly.