Translation
On this page
Contributors may use their preferred language. English is the initial reference version for shared guides.
Languages#
Website drafts cover Simplified Chinese (zh-Hans), Korean (ko), Spanish (es), French (fr), and Arabic (ar). Translators, fluent reviewers, and maintainers are wanted. Other languages are welcome.
Find available pages and review status in the translation directory.
Start with READMEs, the getting-started guide, contribution rules, resource requests, and the project template. Then translate other guides and project summaries as needed.
Prepare a translation#
- For the website, edit the UTF-8 JSON catalog in
translations/catalogs/<language-tag>.json. English phrases are keys; translated phrases are values. The translation directory explains how to export one page for review. Separate repository documents may use UTF-8 Markdown intranslations/<language-tag>/<source-path>. - Record the source path, source commit, language tag, translator, reviewer, and review date.
- Preserve scientific meaning, uncertainty, values, units, identifiers, code, and file paths.
- Use natural technical language. Simplified Technical English (STE) guides English writing; other languages have their own conventions.
- Translate captions, link descriptions, and alt text. Check fonts, line wrapping, and right-to-left text.
- Show language names in their own languages. Use text links rather than flags.
Keep OSRI and Agentic-Powered-Research unchanged. Add a local explanation where needed.
Review and update#
Agents may draft translations. A fluent person must compare the translation with its source. Rules, methods, and scientific claims also need relevant subject expertise.
Label each page draft, reviewed, or needs-update. Mark affected translations when the source changes. If versions conflict, ask a maintainer to resolve the passage against the reference source.
Keep attribution and license notices. Ask for help in Q&A.