Translations

Welcome to the the OWASP Top Ten for LLM 2025 translation project!

The translation workflow

To ensure the quality and delivery of each OWASP Top Ten for LLM translation a process has been defined to ensure successful and accurate translation of the document. Each translation of the OWASP Top Ten for LLMs will go through a following steps before being published.

1. A translation branch is made on the main repo
2. A two letter ISO code for the language is created in the folder 2_0_vulns/translations
3. A copy of all that Markdown files are copied into the appropriate folder
4. Translators fork the repo on Github, switch to the appropriate branch and start translating all the Markdown files. During translations PRs can be made to the OWASP:translations/<language-code> branch if required for collaboration.
5. When 100% of the Markdown is translated, independent reviewers will review each Markdown file.
6. A PR is made to the main repo and the Localizations lead will do a final line by line review before merging
7. WIP PDFs will be generated and the Localizations lead will do a review of that for issues
8. Final PDFs will be be generated and all markdown and PDFs will be merged into the main branch.
9. Promotion of new translation

Actual details on how to kick off a translation are documented below.

For each language a few team members will be needed

1. Translators familiar with the Markdown format and working on Github (the more the better)
2. Reviewers that will review the translations for errors independently once translation of a Markdown file is complete
3. (Optional) A per language translator lead that helps coordinate translators for that specific language
4. Localization lead to coordinate final steps

Step by step translation process

1. Look up your preferred language in the Translation Progress document.

• All languages that are being translated are currently listed on a public spreadsheet. Take a look there, the language you may be thinking about may actually already be in progress and a team has already formed and translating that you can contribute to. More hands make less work so don't be shy to get involved if you see an effort already undergoing.
• If your preferred language is already being translated, then that language will have a dedicated channel on the OWASP Slack. You will find the channel name on the spreadsheet, its link and the handle of the language lead who you can message when you join.
• The best strategy would be to join the channel, introduce yourself and check in with the translation lead. They will help letting you know which part of the OWASP Top Ten for LLMs translation you can help contribute with next.

2. Starting a new translation

If there is no ongoing translation for you preferred language, then it's a simple process for getting started on. The localizations team and lead will help every step of the way. Here are your next steps.

1. Join the OWASP Slack server
2. Once on the server join the #team-llm-translations channel
3. Post a comment tagging Talesh who is the localizations lead mentioning that you'd like to get a new translation for the OWASP Top Ten.
4. Talesh will create a new channel for that translation, the branch on main and the appropriate folder for you.
5. Next you can get started working on the translation via the markdown files.
6. Talesh will work with the community and start sourcing additional translators to help and a team to review the translation while coordinating to ensure that the PDF generator supports the character set of the new translation.