Add German (de) translation of OWASP Top 10:2025 - #964
Open
RicoKomenda wants to merge 1 commit into
Open
Conversation
Full German translation of all 16 documents (Introduction, About OWASP, What are Application Security Risks, Establishing a Modern Application Security Program, A01–A10, Next Steps, and index) plus X02/X03 sections of Next Steps. Wires the de locale into 2025/mkdocs.yml's i18n plugin config and uncomments the existing de entry in extra.alternate, both additive changes alongside the existing cs/es/it/ja/ko/fa/pt-BR/zh-Hant locales.
RicoKomenda
force-pushed
the
translation/german-2025
branch
from
September 8, 2026 21:16
45ca8ad to
d2d3412
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
delocale in2025/mkdocs.yml's i18n plugin config and uncomments the existingdeentry underextra.alternate, following the CONTRIBUTING.md steps for translators. Both changes are additive — the existing cs/es/it/ja/ko/fa/pt-BR/zh-Hant locale configs are untouched.:in/:innen) and terminology (e.g. scenario numbering, "Schwachstelle" vs "Sicherheitslücke", "Zugangsdaten" vs "Anmeldeinformationen") consistently across all files.