trans: Initialize Panjabi (pa-IN) translation structure for ASVS 5.0#3254
Draft
GeeksikhSecurity wants to merge 20 commits into
Draft
trans: Initialize Panjabi (pa-IN) translation structure for ASVS 5.0#3254GeeksikhSecurity wants to merge 20 commits into
GeeksikhSecurity wants to merge 20 commits into
Conversation
- Created pa-IN directory following ISO 639-1 standard - Added initial README.md with bilingual content - Added TRANSLATION-NOTES.md for tracking progress - Added 0x01-Frontispiece.md template from English - Using 'Panjabi' spelling per Sikhri.org convention Related to upcoming issue for Panjabi translation
Collaborator
|
Converted to draft, as the translation is in progress. |
Author
|
Thank you @elarlang for converting this to draft status! 🙏 Current Status Update✅ Completed Infrastructure
🚧 Translation Progress (3/25 files - 12%)
🎯 Next Steps
📊 Quality Metrics
🌍 Community ImpactThis translation will serve 100+ million Panjabi speakers globally, enabling cybersecurity education in underserved linguistic communities and establishing methodology for future OWASP multilingual projects. I'll continue updating this PR as translation progresses. Ready to address any feedback or requirements from the maintainer team! Estimated completion: 4-6 weeks for full translation |
…anded glossary - Translate 0x01-Frontispiece.md from English-only to full bilingual format - Add 0x02-Preface.md bilingual translation (399 words) - Expand README.md glossary from 5 terms to 100+ categorized security terms with Gurmukhi translations, romanization, and T/L/R/H classification - Enhance TRANSLATION-NOTES.md with word counts (38,372 total across 27 files), phased progress tracking, terminology decision log, and QA checklist - Add GIT-CHEATSHEET.md for PR workflow reference - All files validated: Gurmukhi Unicode clean, no Devanagari, markdown intact Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…, 0x05 For Users of 4.0 Phase B progress — these two chapters are self-marked Translation Status: Complete in their headers and have full bilingual body content. Following the format established by Phase A (0x01-Frontispiece, 0x02-Preface): English heading + Panjabi heading mirror; English paragraph immediately followed by its Panjabi equivalent. * 0x04 Assessment_and_Certification.md (10.9 KB) * 0x05 For-Users-Of-4.0.md (18.0 KB) Translation rules per 5.0/pa-IN/CLAUDE.md: - Gurmat-aligned vocabulary; no yoga/Hindu/Sanskrit terms outside Gurbani - Dictionary lookup order: Guru Granth Sahib Dictionary → GGS reference → Punjabi University Patiala (ISBN 81-7380-095-2) - T/L/R/H classification consistent with the 68-term glossary - Gurmukhi numerals for version refs (੫.੦); IAST canonical romanization - "Panjabi" spelling per Sikhri.org / Panjab Digital Library standard Reviewer landing pages live at: https://securityleader.ai/blog/asvs-panjabi-review-hub https://securityleader.ai/blog/asvs-panjabi-review-frontispiece https://securityleader.ai/blog/asvs-panjabi-review-preface https://securityleader.ai/blog/asvs-panjabi-review-glossary Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…tication, 0x17 V8 Authorization Phase B in-flight chapters. Headers self-mark Translation Status: In Progress; committing now to keep PR OWASP#3254 reflective of current state so the OWASP maintainers and community reviewers see active progress. * 0x03 What-is-the-ASVS.md (21.7 KB) — bilingual headings + prose translation currently being completed * 0x15 V6-Authentication.md (23.1 KB) — Control Objective fully bilingual; V6.1 onward in active translation * 0x17 V8-Authorization.md ( 6.1 KB) — headings translated; section descriptions and per-requirement tables in active translation These chapters will receive follow-up commits that finalize the per-section prose + per-requirement table translations. Header status will transition "In Progress" → "Complete" per chapter as bodies are completed. Strategy: commit progress visibly rather than batching for a single large push, so reviewers can comment on terminology choices in flight (especially for V6 Authentication, where security-term drift is the highest risk). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…Week 1) Finished V8 Authorization from In Progress to Complete. Added bilingual mirrors throughout: every English heading has a Gurmukhi mirror line below, every English paragraph has a parallel Panjabi paragraph, and each English requirements table is followed by a matching Panjabi table (ਵੇਰਵਾ/ਪੱਧਰ headers, Gurmukhi numerals for L1/L2/L3). File grew from 60 to 107 lines and Translation Status header moved to Complete. Sections translated: Control Objective, V8.1 Authorization Documentation, V8.2 General Authorization Design, V8.3 Operation Level Authorization, V8.4 Other Authorization Considerations, References. Four tables translated. New glossary terms introduced (proposed, pending reviewer confirmation): - multi-tenant -> ਬਹੁ-ਕਿਰਾਏਦਾਰ (bahu-kirāedār, T) - cross-tenant -> ਅੰਤਰ-ਕਿਰਾਏਦਾਰ (aṅtar-kirāedār, T) - endpoint -> ਅੰਤ-ਬਿੰਦੂ (aṅt-bindū, T) - entitlements -> ਹੱਕ (haqq, T) - self-contained token -> ਸਵੈ-ਨਿਰਭਰ ਟੋਕਨ (svai-nirbhar ṭokan, H) - tier (architecture layer) -> ਪੱਧਰ (paddhar, T) - intermediary -> ਵਿਚੋਲਾ (vichola, T) - adaptive -> ਅਨੁਕੂਲਿਤ (anukūlit, T) - environmental and contextual -> ਵਾਤਾਵਰਣੀ ਅਤੇ ਸੰਦਰਭੀ (T) - step-up authentication -> ਸਟੈਪ-ਅੱਪ ਪ੍ਰਮਾਣੀਕਰਨ (H) - object -> ਆਬਜੈਕਟ (ābjaikṭ, L) - device security posture -> ਡਿਵਾਈਸ ਸੁਰੱਖਿਆ ਮੁਦਰਾ (H) Reused locked glossary entries verbatim: adhikārīkaraṇ, pramāṇīkaraṇ, pahuṅch niyaṅtraṇ, khapatkār, sarot, ijāzat, faṅkshan-paddhar, khetar-paddhar, dastāvezīkaraṇ. Open questions for reviewer: - multi-tenant: confirm bahu-kirāedār vs transliteration ਮਲਟੀ-ਟੇਨੈਂਟ - IDOR/BOLA/BOPLA: kept in Latin in the PA table; confirm house style - entitlements: ਹੱਕ vs ਅਧਿਕਾਰ (latter risks collision with adhikārīkaraṇ) - step-up: Gurmukhi-script transliteration vs fully native rendering - posture: ਮੁਦਰਾ vs ਸਥਿਤੀ in security context Policy compliance: Gurmat-aligned (no yoga/Hindu/Sanskrit drift), zero Devanagari contamination, R21/R22/R23 satisfied. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
… B Week 1) Created the pa-IN file for V9 Self-contained Tokens from scratch following the Phase A bilingual pattern (English block immediately followed by Panjabi block; English requirement table immediately followed by parallel Panjabi rendering). 72 lines, 2.0x the EN chapter — within the expected ~1.7x envelope given table mirroring. Sections translated: V9 heading, Control Objective, V9.1 Token source and integrity (intro + 3-row table), V9.2 Token content (intro + 4-row table), References. Two tables translated. Key terminology decisions: - self-contained token -> ਸਵੈ-ਨਿਰਭਰ ਟੋਕਨ (svai-nirbhar ṭokan, H), English in parens on first use - token -> ਟੋਕਨ (ṭokan, L) per existing TRANSLATION-NOTES entry - JWT/JWS/SAML/OAuth/OIDC retained as acronyms (R) - audience: kept as English inline rather than proposed ਸਰੋਤਾ (sarotā/listener) which does not capture the JWT semantics of "intended recipient service" — flagged for reviewer - stateless: not needed in this chapter, choice deferred - signature -> ਡਿਜੀਟਲ ਦਸਤਖ਼ਤ (ḍijīṭal dastakhat, H) - verification -> ਤਸਦੀਕ (tasdīq, T) - validate / validation -> ਪ੍ਰਮਾਣਿਤ / ਪ੍ਰਮਾਣਿਕਤਾ (T) - issuer -> ਜਾਰੀਕਰਤਾ (jārīkartā, T) - integrity -> ਅਖੰਡਤਾ (akhaṇḍatā, T) - tampering -> ਛੇੜਛਾੜ (chheṛchhāṛ, T) - claim -> ਦਾਅਵਾ (dāʼvā, T) - identifier -> ਪਛਾਣਕਰਤਾ (pachhāṇkartā, T) - context -> ਸੰਦਰਭ (sandarbh, T) - validity period -> ਜਾਇਜ਼ਤਾ ਮਿਆਦ (jāʼizatā miyād, T) Open questions for reviewer: - self-contained: confirm ਸਵੈ-ਨਿਰਭਰ vs ਸਵੈ-ਪੂਰਨ / ਸਵੈ-ਸੰਪੰਨ - audience: confirm English retention vs Panjabi calque - stateless (future chapters): propose ਸਟੇਟਲੈੱਸ (sṭeṭalais, L) - allowlist: kept English inline; reviewer may consider ਪ੍ਰਵਾਨ-ਸੂਚੀ - key material: kept English inline; reviewer may consider ਕੁੰਜੀ-ਸਮੱਗਰੀ Policy compliance: Gurmat-aligned (no yoga/Hindu/Sanskrit drift), zero Devanagari contamination, R21 (no ਠੱਗੀ misuse — none needed), R22 (no ਭਾਈਚਾਰਾ needed — no community references), R23 (IAST canonical romanization). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…y posture" Self-flagged during the V8 Authorization translation workflow w9f91d645: the previously-shipped commit 09838a3 rendered "device security posture assessment" as "ਡਿਵਾਈਸ ਸੁਰੱਖਿਆ ਮੁਦਰਾ ਮੁਲਾਂਕਣ" (line 8.4.2). The word ਮੁਦਰਾ (mudrā) carries strong Hindu/yoga ritual connotations (mudrā = ritual hand gesture in classical Indian iconography and Hatha Yoga practice). Per 5.0/pa-IN/CLAUDE.md "Gurmat Language Constraints (MANDATORY)": ❌ Yoga terminology (chakras, kundalini, pranayama, third eye) ❌ Sanskrit mantras or terms outside of Gurbani context ❌ Any term with yoga/Hindu connotation when a Gurmat or neutral Panjabi equivalent exists ਸਥਿਤੀ (sthitī = state/posture/condition) is the neutral Panjabi equivalent with no Gurmat-constraint conflict. Used widely in modern Panjabi technical and political prose ("ਆਰਥਿਕ ਸਥਿਤੀ" = economic situation). Single occurrence, single-line patch. No other chapter affected. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
New bilingual chapter mirroring the Phase A pattern (EN heading → PA heading; EN paragraph → PA paragraph; EN requirement table → parallel PA table). 102 lines, 17,417 bytes. Translation Status: Complete. Sections translated: - Control Objective (denial of service, unauthorized access, storage exhaustion) - V5.1 File Handling Documentation (1 requirement, L2) - V5.2 File Upload and Content (6 requirements, L1-L3) - V5.3 File Storage (3 requirements, L1-L3) - V5.4 File Download (3 requirements, L2) - References (OWASP File Upload Cheat Sheet, magic bytes, symlinks CVE) Terminology decisions: - File / Upload / Download / Extension — Gurmukhi-script loan (L) - Path traversal / LFI / RFI / SSRF / zip slip — Latin retained (R) - Allowlist — Latin retained (R) — consistent with 0x18 V9 precedent - Magic bytes — Latin retained (R) — well-established crypto/file-format term - HTTP / Content-Disposition / RFC 6266 / JSON / JSONP / URL — Latin (R) - File Handling → ਫ਼ਾਈਲ ਪ੍ਰਬੰਧਨ (H) — hybrid - Storage → ਭੰਡਾਰਨ (T) — Gurmat-neutral, common in Punjabi - Server-side → ਸਰਵਰ-ਪਾਸੇ (H) - Compressed file → ਸੰਕੁਚਿਤ ਫ਼ਾਈਲ (T+L) - Untrusted → ਅਣਭਰੋਸੇਯੋਗ (T) - Denial of service — ਸੇਵਾ-ਇਨਕਾਰ (T) with English in parens on first use - Sanitization → ਸੈਨੀਟਾਈਜ਼ੇਸ਼ਨ (L) — per existing glossary - Symlinks — ਸਿਮਲਿੰਕ (L) with English in parens on first use Policy compliance: - R21 (ਠੱਗੀ-only): no ਫ਼ਰਾਡ standalone (not applicable to file handling) - R22 (ਭਾਈਚਾਰਾ for community): not relevant — no community references - R23 (IAST canonical): tasdīq (not tasdeeq) used throughout for "verify" - Gurmat (CLAUDE.md): no yoga/Hindu/Sanskrit terms; ਮੁਦਰਾ count = 0 - Devanagari purity: 0 leaks (danda U+0964 retained as allowed shared punctuation) Open question for community review: zip-slip, LFI, RFI, SSRF kept as Latin acronyms in the PA table — confirm house-style preference vs Gurmukhi gloss. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…iewer adjudication Reviewer-facing companion to the bilingual translations. Lists every terminology decision made during Phase B that the translator deferred for community review, with current pick + alternatives + reasoning per entry. Questions sourced from workflow w9f91d645 + the 0x14 V5 commit (145ad26): Open (10): * Q1 multi-tenant (V8 Authz) — ਬਹੁ-ਕਿਰਾਏਦਾਰ vs transliteration * Q2 IDOR/BOLA/BOPLA (V8 Authz) — Latin vs Gurmukhi gloss * Q3 entitlements (V8 Authz) — ਹੱਕ vs ਅਧਿਕਾਰ (collision risk) * Q4 step-up authentication (V8) — transliteration vs native * Q6 Self-contained token (V9) — svai-nirbhar vs alternatives * Q7 Audience JWT claim (V9) — English retained (sarotā wrong semantics) * Q8 Stateless (deferred) — loan vs native — early signal welcome * Q9 Allowlist (V9 + V5) — English retained; precedent set across 2 chapters * Q10 Key material (V9) — English retained vs ਕੁੰਜੀ-ਸਮੱਗਰੀ calque * Q11 LFI/RFI/SSRF/zip-slip (V5) — Latin retained, matches Q2 pattern Resolved (1): * Q5 posture (V8 Authz) — ਮੁਦਰਾ → ਸਥਿਤੀ (Gurmat policy fix, commit 9e1e96b) Each entry has: EN term, current pick, T/L/R/H type, alternatives, reasoning, and a "Reviewer notes" field for adjudicators to fill via email (gurvinder@securityleader.ai with subject "ASVS Panjabi Review — Q<number>") or inline PR comment. Also includes a "Policy locks" reference section noting which decisions are already final (R21/R22/R23, Gurmat, Devanagari purity) and not open for review — challenges to policy locks should be separate GitHub issues rather than inline PR comments. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Author
Status update — 2026-06-01 (still Draft, posting for visibility)This PR has been actively progressing. Posting a status summary for maintainers and any reviewers who want to look at the Panjabi translation while it's still in Draft state. Not yet flipping to Ready for review — the in-progress chapters (0x03, 0x15) still need full body translations. What's in this PR right nowCommitted and Complete (8 files under
In Progress (committed as drafts so maintainers can see direction)
Supporting documents
Pending chapters (not yet started)V1 Encoding/Sanitization, V2 Validation, V3 Web Frontend, V4 API/Web Service, V7 Session Management, V10 OAuth/OIDC, V11 Cryptography, V12 Secure Communication, V13 Configuration, V14 Data Protection, V15 Secure Coding, V16 Logging, V17 WebRTC, plus 5 appendices and 0x00 header. Cadence target: 2–3 chapters per week with small-first sequencing, heavy chapters (>15 KB EN) getting solo weeks. Policy locks applied corpus-wide
How reviewers can help right now (Draft is fine)
Companion public review surfaceFor sangat reviewers who don't use GitHub:
Branch is now current with Will flip Draft → Ready for review after 0x03 and 0x15 bodies land and at least 2–3 pre-submission reviewer passes have happened on the terminology questions. |
… (।) for Panjabi sentence-end Proper Panjabi (Gurmukhi-script) prose uses the Indic danda ੦U+0964 ੦ as the sentence terminator, not the Western period. This corpus had drift across Phase A and Phase B chapters where Western periods landed in Panjabi sentence-final positions, including end-of-paragraph and inside requirement-table cells where the sentence ends with a parenthetical. The substitution covers two patterns, applied only on lines that contain Gurmukhi characters (so English paragraphs in bilingual files are untouched): 1. ੦Gurmukhi letter੦ + ੦.੦ + ੦(space|EOL)੦ → ੦Gurmukhi letter੦ + ੦।੦ + ੦(space|EOL)੦ 2. ੦)੦ + ੦.੦ + ੦(space|EOL)੦ on Panjabi lines → ੦)੦ + ੦।੦ + ੦(space|EOL)੦ (catches sentences that end with a parenthetical, e.g. "(ਜਿਵੇਂ, RFC 6266 ਦੇ ਅਨੁਸਾਰ).") Excluded by design: - Periods preceded by ASCII digits (version numbers like 5.0, requirement IDs like 5.2.1, decimal counts) - Periods inside English paragraphs, URLs, file extensions, and English abbreviations on lines that contain no Gurmukhi - Periods preceded by Gurmukhi digits (U+0A66-U+0A6F) — same logic Files corrected (with substitution count): * 5.0/pa-IN/0x01-Frontispiece.md — 11 * 5.0/pa-IN/0x02-Preface.md — 21 * 5.0/pa-IN/0x14-V5-File-Handling.md — 24 * 5.0/pa-IN/0x17-V8-Authorization.md — 26 * 5.0/pa-IN/0x18-V9-Self-contained-Tokens.md — 25 * 5.0/pa-IN/README.md — 18 * 5.0/pa-IN/REVIEW-PLAN.md — 1 * 5.0/pa-IN/TRANSLATION-NOTES.md — 1 Already correct (no changes): 0x03, 0x04, 0x05, 0x15, CLAUDE.md, OPEN-QUESTIONS.md — these files either use danda already (the workflow- translated Complete chapters 0x04 and 0x05) or contain no Panjabi sentences to terminate. Policy alignment: - R4 (Devanagari contamination check) already carved out U+0964 ੦ and U+0965 ੨ as shared Indic punctuation explicitly allowed in Gurmukhi. Devanagari purity check still reports 0 leaks across all 13 files. - Going forward, all new Panjabi prose must use ੨ for sentence-final punctuation. Will land as content-rigor.md R24 in a follow-up doc commit. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…danda (।) Locks the orthographic policy applied corpus-wide in commit bdda180. New section "Sentence-ending punctuation (MANDATORY)" documents: - The rule: every Panjabi sentence ends with । (U+0964), not Western period - Parenthetical-ending sentences: ).→)। (not the other way around) - Exceptions kept on Western .: ASCII digits, version numbers, URLs, English abbreviations, decimals, English-only lines - R4 codepoint allowlist: U+0964 and U+0965 explicitly excluded from Devanagari contamination check - Reference to the corpus-wide application commit bdda180 Future translations honor this from creation; existing chapters already patched. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
… B Week 2) New bilingual chapter following the Phase A pattern. Translation Status: Complete. Honors the danda (।) sentence-end rule locked in commit 7479894. Sections translated: - Control Objective (data in transit, end-user→backend, internal services) - V12.1 General TLS Security Guidance (5 requirements, L1-L3) - V12.2 HTTPS Communication with External Facing Services (2 requirements, L1) - V12.3 General Service to Service Communication Security (5 requirements, L2-L3) - References (OWASP TLS Cheat Sheet, Mozilla SSL config, O-Saft) Terminology decisions: - Secure Communication → ਸੁਰੱਖਿਅਤ ਸੰਚਾਰ (T) - Data in transit → ਪ੍ਰਸਾਰਣ ਦੌਰਾਨ ਡਾਟਾ (T) with English in parens on first use - TLS / mTLS / OCSP / ECH / SNI / PKI / HTTP / HTTPS / SSH / API / CA — Latin (R) - TLS 1.2 / TLS 1.3 — preserved verbatim - Encrypted / Encryption — ਏਨਕ੍ਰਿਪਟ ਕੀਤੇ / ਏਨਕ੍ਰਿਪਸ਼ਨ (L) - Cipher / Cipher suite → ਸਾਈਫ਼ਰ / ਸਾਈਫ਼ਰ ਸੂਟ (L) - Forward secrecy → ਅੱਗੇ ਦੀ ਗੁਪਤਤਾ (T) with English in parens - Wildcard → ਵਾਈਲਡਕਾਰਡ (L) - Self-signed certificate → ਸਵੈ-ਦਸਤਖ਼ਤੀ ਸਰਟੀਫ਼ਿਕੇਟ (H) - Posture → ਸਥਿਤੀ (T) — locked from 0x17 Gurmat fix (9e1e96b) - Replay attack → ਰੀਪਲੇ ਹਮਲਾ (L+T) - Endpoint → ਅੰਤ-ਬਿੰਦੂ (T) — locked from 0x17 - Microservice → ਮਾਈਕਰੋਸਰਵਿਸ (L) - Service mesh → ਸੇਵਾ ਮੈਸ਼ (T+L) with English in parens - Backend → ਬੈਕਐਂਡ (L) - Production / Staging / Development / Test — loanword (L) per industry standard - Handshake → ਹੈਂਡਸ਼ੇਕ (L) Policy compliance: - R21 (ਠੱਗੀ-only standalone fraud): not applicable to TLS chapter - R22 (ਭਾਈਚਾਰਾ for community): not relevant - R23 (IAST canonical romanization): pramāṇīkaraṇ, adhikārīkaraṇ, sthitī, anta-bindū - Gurmat (CLAUDE.md): no yoga/Hindu/Sanskrit terms; ਮੁਦਰਾ count = 0 - Devanagari purity: 0 leaks (danda U+0964 retained as allowed shared punctuation) - Sentence-end orthography: all Panjabi sentences end with ।, no Western . after Gurmukhi Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…h REVIEW-PLAN status Prepares the corpus for community/professional review. REVIEWER-NOTES.md (NEW) — self-contained shareable briefing: - "You don't need to be both" (Panjabi reader OR security practitioner) - 8 Complete chapters with shortest-to-start recommendations - What to look for (accuracy, terminology, script, readability, Gurmat fit) - Policy locks reviewers should NOT re-litigate inline (separate issue instead) - How to send feedback (email / GitHub PR / public review pages) - QA-already-run summary (Opus 4.8 mechanical scan, 0 violations) OPEN-QUESTIONS.md — added Q12 (highest priority, CORPUS-WIDE): - Documents the two coexisting bilingual structures found in the Opus 4.8 QA scan: Pattern A (dual-block, English-first + Panjabi mirror, used in 0x01/0x02/0x14/0x17/0x18/0x21) vs Pattern B (code-switched single-block, used in 0x04/0x05). - The choice is genuinely unmade — the two patterns are an artifact of different drafting passes, not a deliberate decision. Deferred to community review per project-owner decision. - Translator recommendation: Pattern A everywhere (matches the public rationale's stated bilingual-readability promise); 0x04/0x05 would be re-translated if community agrees. REVIEW-PLAN.md — refreshed the stale Feb-23 header: - Co-author Opus 4.6 → 4.8 - Added current-status table (8 Complete / 2 In Progress / pending list) - Pointer to REVIEWER-NOTES.md as the recommended starting point - Note that 12 open questions exist, Q12 highest priority QA context: Opus 4.8 adversarial scan (2026-06-02) found the corpus mechanically flawless (0 Devanagari leaks, 0 fraud-term/Gurmat/romanization/ Western-period violations across 13 files). The only finding was the Q12 structural inconsistency, now documented for review rather than silently fixed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Consolidated translation rules for the Panjabi (pa-IN) ASVS translation, accepting all recommendations from the Punjabi University usage review: Gurmukhi-only/NFC, danda, Western numerals (incl. version numbers), the apostrophe-clitic 'ਤੇ accepted (not an error), IAST romanization, T/L/R/H terminology anchored in Punjabi University lexicography, locked decisions (ਠੱਗੀ/ਭਾਈਚਾਰਾ/house glossary), Gurmat safety, bilingual dual-block, verb precision, requirement-ID preservation, and the Sangat certification gate. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…l rules) SAY-318 Section A, applied corpus-wide: - Convert Gurmukhi numerals -> Western digits in content chapters + README (version numbers, years, ASVS level column); requirement IDs already Western. - Flip stale "use Gurmukhi numerals" guidance in CLAUDE.md, REVIEW-PLAN.md, and TRANSLATION-NOTES.md to the accepted Western-numeral rule. - Name TRANSLATION-RULES.md as the canonical rule set in CLAUDE.md. - NFC: corpus already normalized (verified no-op). Apostrophe-clitic 'ਤੇ preserved (already declared acceptable in TRANSLATION-RULES.md). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
2 participants
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.
Pull Request: Panjabi Translation of ASVS v5.0
Summary
This PR introduces the first Panjabi (ਪੰਜਾਬੀ) translation of OWASP ASVS v5.0, reaching 130+ million Panjabi speakers worldwide. Every section is bilingual — English first, Panjabi (Gurmukhi script) immediately below — so developers can cross-reference for technical precision.
Changes Made
5.0/pa-IN/directory structureTranslation Details
Files Added
Terminology Approach
Each security term is classified as:
Community Impact
How to Review
5.0/pa-IN/Checklist
Related Issues
Maintainer
GeeksikhSecurity — Committed to ongoing maintenance and community engagement