[PR #6499] [MERGED] docs(readme): add Roman Urdu edition #7371

Closed
opened 2026-11-01 21:47:23 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/6499
Author: @hifzabuildsai
Created: 10/23/2026
Status: ✅ Merged
Merged: 10/23/2026
Merged by: @morluto

Base: main ← Head: docs/roman-urdu-readme


📝 Commits (2)

  • dfaba57 docs(readme): add Roman Urdu edition
  • d5d0d16 test(website): cover completed script-tag page metadata

📊 Changes

48 files changed (+15417 additions, -1927 deletions)

View changed files

📝 README.md (+1 -1)
📝 docs/readme/README_ar.md (+1 -1)
📝 docs/readme/README_de.md (+1 -1)
📝 docs/readme/README_el.md (+1 -1)
📝 docs/readme/README_es.md (+1 -1)
📝 docs/readme/README_fa.md (+1 -1)
📝 docs/readme/README_fr.md (+1 -1)
📝 docs/readme/README_id.md (+1 -1)
📝 docs/readme/README_it.md (+1 -1)
📝 docs/readme/README_ja.md (+1 -1)
📝 docs/readme/README_ko.md (+1 -1)
📝 docs/readme/README_ml.md (+1 -1)
📝 docs/readme/README_pl.md (+1 -1)
📝 docs/readme/README_pt-BR.md (+1 -1)
📝 docs/readme/README_ru.md (+1 -1)
📝 docs/readme/README_th.md (+1 -1)
📝 docs/readme/README_tr.md (+1 -1)
📝 docs/readme/README_uk.md (+1 -1)
➕ docs/readme/README_ur-Latn.md (+435 -0)
📝 docs/readme/README_vi.md (+1 -1)

...and 28 more files

📄 Description

Summary

Add a Roman Urdu README for readers who use Urdu in Latin script with English technical terms. Register it as ur-Latn with left-to-right direction, link it from every README language menu, and keep its untranslated website pages as labeled, nonindexable English fallbacks.

Change and scope

  • Translate the current English README, including setup, supported targets, examples, FAQ, limitations, responsible-use guidance and licensing. Preserve executable examples, product names, requirements and recorded case-study values.
  • Register the edition in the shared language inventory and generate its pending gettext catalog and shared website navigation. Existing translated catalog contents are unchanged.
  • Accept canonical script subtags through the same language-code helper in inventory admission and search-metadata validation. Add inventory coverage for script identity, region ordering and invalid casing, plus completed ur-Latn and ur-Latn-PK page fixtures through check_search_metadata().

This is distinct from the standard Urdu-script translations in #4491 and #5276.

Shared dependency: the language-code helper and its verifier use follow maintainer @morluto's existing change in #2043, commit c46f606c899e27b2e51c16500493413daf57ddad. That PR remains open. These two small source changes are carried here because main rejects ur-Latn; they are not claimed as a new independent parser fix. Rebase away the overlap when the shared script-tag support lands. No Hinglish translation or catalog is copied.

Contract and boundary impact

Documentation and website language identity only. CLI/MCP contracts, providers, target authority, installed-package behavior and package metadata are unchanged. No separate capability-scope decision applies.

  • Documentation or usability only; no target interaction.

Evidence and validation

Base: 5d813633919825030623cf9b3ef640833ef4de14. Linux, Node.js 24.18.0, npm 11.16.0, Python 3.12, repository-pinned website dependencies.

  • Before the script-tag change, the new inventory regression rejected ur-Latn, ur-Latn-PK and hi-Latn. It passes after the shared parser is used.
  • Review follow-up: completed, indexable ur-Latn and ur-Latn-PK fixtures pass search-metadata, hreflang and sitemap validation. Running the new test with the verifier's old language/region-only predicate produces the expected needs lang=en failures for both routes. The inventory test alone did not exercise this consumer.
  • npm run check — passed, including typecheck, formatting, lint, metadata and architecture checks.
  • npm run docs:check — passed, including all 9 README consistency checks.
  • .venv/bin/python scripts/website.py check — passed: 25 maintenance tests, 420 HTML pages, 29,531 local references, and search/sitemap checks. The new edition has 19 English fallback pages; the existing 380 indexable pages are preserved.
  • All 7 bash examples match the English README byte for byte. A separate local Markdown check resolves all 93 relative links and fragments in the new README.
  • git diff --cached --check — passed.

External-link availability, browser visual review, and independent human language review were not checked. Real-provider verification does not apply to this documentation/site-inventory change. The website itself is not translated into Roman Urdu.

Author readiness

Human owner: @hifzabuildsai

  • I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
  • I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
  • I declare this PR ready for initial maintainer review.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/6499 **Author:** [@hifzabuildsai](https://github.com/hifzabuildsai) **Created:** 10/23/2026 **Status:** ✅ Merged **Merged:** 10/23/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `docs/roman-urdu-readme` --- ### 📝 Commits (2) - [`dfaba57`](https://github.com/morluto/rea/commit/dfaba57013fccf815e1579762dfdd4d54322fb97) docs(readme): add Roman Urdu edition - [`d5d0d16`](https://github.com/morluto/rea/commit/d5d0d1627585cc9d09ebe1c2aaea1a46c38e08ae) test(website): cover completed script-tag page metadata ### 📊 Changes **48 files changed** (+15417 additions, -1927 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -1) 📝 `docs/readme/README_ar.md` (+1 -1) 📝 `docs/readme/README_de.md` (+1 -1) 📝 `docs/readme/README_el.md` (+1 -1) 📝 `docs/readme/README_es.md` (+1 -1) 📝 `docs/readme/README_fa.md` (+1 -1) 📝 `docs/readme/README_fr.md` (+1 -1) 📝 `docs/readme/README_id.md` (+1 -1) 📝 `docs/readme/README_it.md` (+1 -1) 📝 `docs/readme/README_ja.md` (+1 -1) 📝 `docs/readme/README_ko.md` (+1 -1) 📝 `docs/readme/README_ml.md` (+1 -1) 📝 `docs/readme/README_pl.md` (+1 -1) 📝 `docs/readme/README_pt-BR.md` (+1 -1) 📝 `docs/readme/README_ru.md` (+1 -1) 📝 `docs/readme/README_th.md` (+1 -1) 📝 `docs/readme/README_tr.md` (+1 -1) 📝 `docs/readme/README_uk.md` (+1 -1) ➕ `docs/readme/README_ur-Latn.md` (+435 -0) 📝 `docs/readme/README_vi.md` (+1 -1) _...and 28 more files_ </details> ### 📄 Description ## Summary Add a Roman Urdu README for readers who use Urdu in Latin script with English technical terms. Register it as `ur-Latn` with left-to-right direction, link it from every README language menu, and keep its untranslated website pages as labeled, nonindexable English fallbacks. ## Change and scope - Translate the current English README, including setup, supported targets, examples, FAQ, limitations, responsible-use guidance and licensing. Preserve executable examples, product names, requirements and recorded case-study values. - Register the edition in the shared language inventory and generate its pending gettext catalog and shared website navigation. Existing translated catalog contents are unchanged. - Accept canonical script subtags through the same language-code helper in inventory admission and search-metadata validation. Add inventory coverage for script identity, region ordering and invalid casing, plus completed `ur-Latn` and `ur-Latn-PK` page fixtures through `check_search_metadata()`. This is distinct from the standard Urdu-script translations in #4491 and #5276. **Shared dependency:** the language-code helper and its verifier use follow maintainer @morluto's existing change in #2043, commit `c46f606c899e27b2e51c16500493413daf57ddad`. That PR remains open. These two small source changes are carried here because main rejects `ur-Latn`; they are not claimed as a new independent parser fix. Rebase away the overlap when the shared script-tag support lands. No Hinglish translation or catalog is copied. ## Contract and boundary impact Documentation and website language identity only. CLI/MCP contracts, providers, target authority, installed-package behavior and package metadata are unchanged. No separate capability-scope decision applies. - [x] Documentation or usability only; no target interaction. ## Evidence and validation Base: `5d813633919825030623cf9b3ef640833ef4de14`. Linux, Node.js 24.18.0, npm 11.16.0, Python 3.12, repository-pinned website dependencies. - Before the script-tag change, the new inventory regression rejected `ur-Latn`, `ur-Latn-PK` and `hi-Latn`. It passes after the shared parser is used. - Review follow-up: completed, indexable `ur-Latn` and `ur-Latn-PK` fixtures pass search-metadata, hreflang and sitemap validation. Running the new test with the verifier's old language/region-only predicate produces the expected `needs lang=en` failures for both routes. The inventory test alone did not exercise this consumer. - `npm run check` — passed, including typecheck, formatting, lint, metadata and architecture checks. - `npm run docs:check` — passed, including all 9 README consistency checks. - `.venv/bin/python scripts/website.py check` — passed: 25 maintenance tests, 420 HTML pages, 29,531 local references, and search/sitemap checks. The new edition has 19 English fallback pages; the existing 380 indexable pages are preserved. - All 7 bash examples match the English README byte for byte. A separate local Markdown check resolves all 93 relative links and fragments in the new README. - `git diff --cached --check` — passed. External-link availability, browser visual review, and independent human language review were not checked. Real-provider verification does not apply to this documentation/site-inventory change. The website itself is not translated into Roman Urdu. ## Author readiness Human owner: @hifzabuildsai - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-01 21:47:23 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#7371
No description provided.