[PR #4758] [CLOSED] docs(i18n): add Telugu README translation #6393

Closed
opened 2026-10-31 01:14:08 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4758
Author: @sathish123m
Created: 10/17/2026
Status: ❌ Closed

Base: main ← Head: docs/telugu-readme


📝 Commits (1)

  • 1ffbcba docs(i18n): add Telugu README translation

📊 Changes

63 files changed (+53725 additions, -39941 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_pl.md (+1 -1)
📝 docs/readme/README_pt-BR.md (+1 -1)
📝 docs/readme/README_ru.md (+1 -1)
➕ docs/readme/README_te.md (+402 -0)
📝 docs/readme/README_th.md (+1 -1)
📝 docs/readme/README_tr.md (+1 -1)
📝 docs/readme/README_uk.md (+1 -1)
📝 docs/readme/README_vi.md (+1 -1)
📝 docs/readme/README_zh-TW.md (+1 -1)

...and 43 more files

📄 Description

Summary

Add a Telugu (te) README edition so Telugu readers can follow the onboarding
guide in their language, matching the existing editions under docs/readme/.

The translation tracks the current English README. Telugu is registered in the
README language selectors and the website language inventory, and the generated
website catalog, sitemap behavior and shared page markup stay consistent.

No issue is linked: there is no open Telugu request. If maintainers prefer an
issue-first flow for new languages, I can move the discussion there.

Problem and expected behavior

The onboarding documentation has editions for 19 languages, but none for
Telugu, so Telugu readers land on the English README. Expected behavior:
docs/readme/README_te.md renders the same product facts, commands and links
as README.md, every language selector links it, and website tooling treats
te like the other editions — pages that are not translated yet show the
labeled English fallback with noindex.

Change and scope

  • New docs/readme/README_te.md, translated from the current English README,
    including the Linux procps prerequisite, the Go and SQLite rows and the Bun
    1.2.17 rea update wording. Commands, paths, URLs, code blocks and Evidence
    terminology are unchanged.
  • Telugu appended last in every README language selector (README.md and all
    19 existing editions) and registered in website/locales/languages.json.
  • python3 scripts/website.py translations extract generated
    website/locales/te/messages.po and refreshed catalog source references for
    the pages whose shared markup changed; the synced shared regions are
    committed.
  • website/locales/README.md documents that the Telugu website catalog has no
    reviewed messages yet, so its pages use the labeled English fallback.
  • Intentionally not included: reviewed Telugu website messages (a separate
    follow-up), and unrelated changes.

Contribution scope: documentation-only translation; no target execution,
injection, mutation or protection recovery. Maintainer scope decision:
not applicable.

Contract and boundary impact

  • Semantic owner and earliest changed stage: not applicable (documentation).
  • Contribution scope fit and linked maintainer decision: docs-only; not applicable.
  • CLI and MCP/tool-catalog contract: none.
  • Provider, bridge, target-format, or platform compatibility: none.
  • Evidence, artifact, provenance, or reconstruction contract: none.
  • Target selection, authority, upstream behavior, and cleanup details: none.
  • Generated metadata: website/locales/*.po and messages.pot were regenerated
    with the documented translations extract step; no product catalog, package
    or installation change.

Expected effects (documentation-only on its own):

  • Documentation or usability only; no target interaction.

Evidence and regression coverage

  • Tests added or updated: none; existing checks cover this change.
  • Base reproduction or other evidence: readmeConsistency discovers the new
    edition, requires its bash examples to equal the English ones, and compares
    languages.json entries with the README files on disk;
    documentationFactIssues compares every resolved README link target against
    the English canonical set.
  • Remaining proof gaps: the Telugu text is machine-assisted and needs native
    review, which the human owner (a Telugu speaker) provides during PR
    readiness. The Telugu website catalog is registered but untranslated, so its
    pages show the labeled English fallback until a follow-up translates them.

Validation performed

  • npm run test:local -- tests/conformance/readmeConsistency.test.ts — 5 tests passed.
  • npx vitest run tests/boundary/filesystem/documentationFacts.test.ts — 1 test passed (after generating the ignored docs/public/product-catalog.json).
  • node scripts/check-doc-facts.mjs — exit 0.
  • python3 scripts/website.py check — exit 0 (prepared 399 reading pages in 21 languages; verified 401 HTML pages and 27,790 local references; 380 indexable sitemap pages with the 19 Telugu fallback pages marked noindex).
  • npx oxfmt --check README.md docs/readme website/locales — clean.

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable (documentation).
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: none.

Author readiness

Human owner: @sathish123m

  • 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.

Before merge

  • This PR addresses a concrete problem or an agreed enhancement.
  • Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
  • The PR has one focused outcome and the title follows type(scope): outcome.
  • Related issue is linked, or the reason for not linking one is stated above.
  • Tests cover changed observable behavior and meaningful failure paths.
  • Owning docs, contracts, and generated metadata are updated where needed.
  • User-visible CLI/MCP changes include representative output.
  • I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

🔄 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/4758 **Author:** [@sathish123m](https://github.com/sathish123m) **Created:** 10/17/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `docs/telugu-readme` --- ### 📝 Commits (1) - [`1ffbcba`](https://github.com/morluto/rea/commit/1ffbcbad1e35d14998915040d78096a7f480db07) docs(i18n): add Telugu README translation ### 📊 Changes **63 files changed** (+53725 additions, -39941 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_pl.md` (+1 -1) 📝 `docs/readme/README_pt-BR.md` (+1 -1) 📝 `docs/readme/README_ru.md` (+1 -1) ➕ `docs/readme/README_te.md` (+402 -0) 📝 `docs/readme/README_th.md` (+1 -1) 📝 `docs/readme/README_tr.md` (+1 -1) 📝 `docs/readme/README_uk.md` (+1 -1) 📝 `docs/readme/README_vi.md` (+1 -1) 📝 `docs/readme/README_zh-TW.md` (+1 -1) _...and 43 more files_ </details> ### 📄 Description ## Summary Add a Telugu (`te`) README edition so Telugu readers can follow the onboarding guide in their language, matching the existing editions under `docs/readme/`. The translation tracks the current English README. Telugu is registered in the README language selectors and the website language inventory, and the generated website catalog, sitemap behavior and shared page markup stay consistent. No issue is linked: there is no open Telugu request. If maintainers prefer an issue-first flow for new languages, I can move the discussion there. ## Problem and expected behavior The onboarding documentation has editions for 19 languages, but none for Telugu, so Telugu readers land on the English README. Expected behavior: `docs/readme/README_te.md` renders the same product facts, commands and links as `README.md`, every language selector links it, and website tooling treats `te` like the other editions — pages that are not translated yet show the labeled English fallback with `noindex`. ## Change and scope - New `docs/readme/README_te.md`, translated from the current English README, including the Linux `procps` prerequisite, the Go and SQLite rows and the Bun 1.2.17 `rea update` wording. Commands, paths, URLs, code blocks and Evidence terminology are unchanged. - Telugu appended last in every README language selector (`README.md` and all 19 existing editions) and registered in `website/locales/languages.json`. - `python3 scripts/website.py translations extract` generated `website/locales/te/messages.po` and refreshed catalog source references for the pages whose shared markup changed; the synced shared regions are committed. - `website/locales/README.md` documents that the Telugu website catalog has no reviewed messages yet, so its pages use the labeled English fallback. - Intentionally not included: reviewed Telugu website messages (a separate follow-up), and unrelated changes. Contribution scope: documentation-only translation; no target execution, injection, mutation or protection recovery. Maintainer scope decision: not applicable. ## Contract and boundary impact - Semantic owner and earliest changed stage: not applicable (documentation). - Contribution scope fit and linked maintainer decision: docs-only; not applicable. - CLI and MCP/tool-catalog contract: none. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: none. - Target selection, authority, upstream behavior, and cleanup details: none. - Generated metadata: `website/locales/*.po` and `messages.pot` were regenerated with the documented `translations extract` step; no product catalog, package or installation change. Expected effects (documentation-only on its own): - [x] Documentation or usability only; no target interaction. ## Evidence and regression coverage - Tests added or updated: none; existing checks cover this change. - Base reproduction or other evidence: `readmeConsistency` discovers the new edition, requires its bash examples to equal the English ones, and compares `languages.json` entries with the README files on disk; `documentationFactIssues` compares every resolved README link target against the English canonical set. - Remaining proof gaps: the Telugu text is machine-assisted and needs native review, which the human owner (a Telugu speaker) provides during PR readiness. The Telugu website catalog is registered but untranslated, so its pages show the labeled English fallback until a follow-up translates them. ## Validation performed - `npm run test:local -- tests/conformance/readmeConsistency.test.ts` — 5 tests passed. - `npx vitest run tests/boundary/filesystem/documentationFacts.test.ts` — 1 test passed (after generating the ignored `docs/public/product-catalog.json`). - `node scripts/check-doc-facts.mjs` — exit 0. - `python3 scripts/website.py check` — exit 0 (prepared 399 reading pages in 21 languages; verified 401 HTML pages and 27,790 local references; 380 indexable sitemap pages with the 19 Telugu fallback pages marked `noindex`). - `npx oxfmt --check README.md docs/readme website/locales` — clean. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: not applicable (documentation). - Package or release metadata impact: none. - Security, privacy, process, or containment review: none. ## Author readiness Human owner: @sathish123m - [ ] 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. ## Before merge - [ ] This PR addresses a concrete problem or an agreed enhancement. - [ ] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [ ] The PR has one focused outcome and the title follows `type(scope): outcome`. - [ ] Related issue is linked, or the reason for not linking one is stated above. - [ ] Tests cover changed observable behavior and meaningful failure paths. - [ ] Owning docs, contracts, and generated metadata are updated where needed. - [ ] User-visible CLI/MCP changes include representative output. - [ ] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 01:14:08 +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#6393
No description provided.