Why browser translation is not enough
Automatic translation can help a visitor navigate, but religious vocabulary, names, kinship, poetic language, transliteration, and tradition labels require editorial judgment. A translated page should not be published merely because software produced fluent sentences.
What an editorial translation requires
- A translator with strong command of both languages and the subject.
- A terminology guide for Sanskrit and regional religious vocabulary.
- Editorial checks for doctrinal, regional, and cultural meaning—not only grammar.
- Translated navigation, metadata, structured data, images, alt text, and policy pages.
- A process for keeping corrections synchronized across editions.
Planned architecture
Future editions may use /hi/, /gu/, /ta/, /te/, and /bn/ directories. English remains at its existing URLs. Hreflang links will be added only when the corresponding editorial translation exists.
Current selector
The header identifies English as active and describes other languages as planned. It does not redirect by IP or browser language and does not claim that a translation is already published.