Arabic translation of ASVS v5.0.0

Abierto
  • ¿Algo no está bien?
#3,405 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
markdown
Área
documentation, localization

Línea de trabajo

Usa la rama v5.0.0 como exige CONTRIBUTING.md y traduce los 27 archivos de 5.0/en a una nueva carpeta 5.0/ar. Ejecuta 5.0/tools/translation_validation/validate_translation.py --translated-folder ar y markdownlint con .markdownlint.jsonc; se considera terminado cuando los 27 archivos superan las comprobaciones estructurales y de requisitos, con los IDs y niveles sin cambios.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
HTML
Estrellas
3.8k
Forks
855
Merge medio
1 d 9 h
PR fusionados (30 d)
8

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de OWASP/ASVS

Todos los issues de OWASP/ASVS

Issues similares

Más issues de Documentation

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.