Arabic translation of ASVS v5.0.0

Aperta
  • Qualcosa non va?
#3,405 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
25/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
markdown
Ambito
documentation, localization

Direzione di ricerca

Usa il branch v5.0.0 come richiesto da CONTRIBUTING.md e traduci i 27 file in 5.0/en in una nuova cartella 5.0/ar. Esegui 5.0/tools/translation_validation/validate_translation.py --translated-folder ar e markdownlint con .markdownlint.jsonc; il lavoro è completato quando tutti i 27 file superano i controlli strutturali e dei requisiti, con ID e livelli invariati.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

I would like to contribute an Arabic (ar) translation of ASVS 5.0.0.

I searched first: the only previous Arabic work is #1172 / #1174 against v4.0.3
in 2022, and there is no in-progress Arabic effort listed in CONTRIBUTING.md.

Status: complete. All 27 files in 5.0/en are translated, based on the
v5.0.0 branch as CONTRIBUTING.md requires, in a new 5.0/ar folder.

Checks:

  • 5.0/tools/translation_validation/validate_translation.py --translated-folder ar
    reports Overall: PASS, 27/27 files, 0 requirement failures, 0 structural failures
  • markdownlint clean against .markdownlint.jsonc
  • All 345 requirement IDs and levels are byte-identical to the English
  • The PR touches only 5.0/ar/ (28 files, insertions only)

Conventions used, following the merged translations rather than inventing new ones:

  • Chapter/section headings keep the V<n> prefix and translate the name, as in tr/ru/id/ko/pt/fr
  • Table headers translated (| # | الوصف | المستوى |)
  • Glossary keeps the English term as the bolded lookup key with an Arabic gloss,
    following the Russian pattern - it keeps the A-Z ordering meaningful and stays
    searchable for practitioners who know the English terms
  • Terminology inherited from the official 4.0.3 Arabic translation where it exists
    (37 of the 87 glossary terms), except for a handful of entries in 4.0/ar that
    are defective - PSTN and PII carry the wrong term, PBKDF2's definition is
    circular, and "Hibernate" was translated as "hibernation". Those were written fresh
  • Protocol names and acronyms stay in Latin script (TLS, JWT, OAuth, SAML, WebRTC ...)
  • Appendix C's algorithm tables are preserved verbatim - only headings, prose and
    table headers are translated. A transposed digit in an Argon2 parameter would be
    worse than leaving a row in English

One deliberate deviation from the English source: ≥ (U+2265) is written as >=
in Appendix C. Amiri has no glyph for U+2265, so it is silently dropped from the
PDF, turning m ≥ 47104 into m 47104 - a minimum reading as an exact value in a
password-hashing parameter table. See the separate issue on RTL PDF generation.

Happy to adjust any of the above - particularly terminology - if the working group
has preferences.

Lingua principale
HTML
Stelle
3.8k
Fork
855
Merge medio
1g 9h
PR unite (30g)
8

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di OWASP/ASVS

Tutte le issue di OWASP/ASVS

Issue simili

Altre issue su Documentation

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.