morluto/rea

Fork 0

mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00

[PR #2847] [CLOSED] docs: add Hindi (हिन्दी) translation of README #5434

New issue

Closed

opened 2026-10-31 01:06:35 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 01:06:35 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/2847
Author: @rollroyces
Created: 10/13/2026
Status: ❌ Closed

Base: main ← Head: docs/add-hindi-readme

📝 Commits (1)

c4f6048 docs: add Hindi (हिन्दी) translation of README

📊 Changes

1 file changed (+309 additions, -0 deletions)

View changed files

➕ README_hi.md (+309 -0)

📄 Description

Summary

Adds README_hi.md, a Hindi (हिन्दी) translation of the English README.md, mirroring the conventions of the existing 20 sibling translations.

Background

REA ships READMEs in ~20 languages (zh, zh-TW, ja, ko, tr, ru, vi, th, de, es, fr, uk, pl, pt-BR, ar, fa, id, it and the source English). Hindi was missing despite being one of the most-spoken languages in the world.

Change

New file: README_hi.md (38,225 bytes; 309 lines), Devanagari throughout the prose.
Preserves all code blocks (8), commands, badges (5 shields), anchor links, <a id> markers, and the language-switcher header bar.
Placed **हिन्दी** between ไทย and Deutsch in the header.
Mirrors README_de.md formatting (≈19 kB siblings; size difference is the Devanagari UTF-8 byte cost, similar to README_ja.md at 24 kB).
Kept the **You must legally obtain...** paragraph verbatim in English, matching how German and Japanese siblings leave it untranslated.
Translated "Quick start" → त्वरित शुरुआत, "Showcases" → उदाहरण. Other navigation anchors translated to Devanagari slugs that should auto-generate correctly in GitHub.

Out of scope

No source code change.
No CLI/MCP contract change.
No docs generation change (the docs:generate pipeline does not touch the root README*.md files; this is a language header entry under the project's existing translation convention).
No additional languages — keeping the PR focused on Hindi.

Validation

Confirmed all badge URLs, anchor targets, and docs/ links preserved.
Manual review: 21 anchored navigation links (mix of explicit + GitHub-auto-generated) match the corresponding translated headings.
Translation quality: aimed for natural-sounding technical Hindi rather than English calques; technical identifiers (MCP, Hopper, Ghidra, IDA, JEB, JADX, Binwalk, ASAR, etc.) kept verbatim per sibling convention.
Note: I cannot run the docs:check lint locally (no npm install in this environment); parent CI is expected to be the final source of truth for any generated metadata links.

Open questions

Header entry position: I placed **हिन्दी** between ไทย and Deutsch. If the project keeps translations in chronological-add order and prefers a different slot, that's a one-line reorder.
GitHub anchor slugification for Devanagari: should work (consistent with how German umlauts resolve), but only github.com rendering can confirm.

Happy to renumber or reposition the header entry on maintainer request.

_{🔄 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/2847 **Author:** [@rollroyces](https://github.com/rollroyces) **Created:** 10/13/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `docs/add-hindi-readme` --- ### 📝 Commits (1) - [`c4f6048`](https://github.com/morluto/rea/commit/c4f604860686571d0edef07eb50bb4aea23f9038) docs: add Hindi (हिन्दी) translation of README ### 📊 Changes **1 file changed** (+309 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `README_hi.md` (+309 -0) </details> ### 📄 Description ## Summary Adds `README_hi.md`, a Hindi (हिन्दी) translation of the English `README.md`, mirroring the conventions of the existing 20 sibling translations. ## Background REA ships READMEs in ~20 languages (zh, zh-TW, ja, ko, tr, ru, vi, th, de, es, fr, uk, pl, pt-BR, ar, fa, id, it and the source English). Hindi was missing despite being one of the most-spoken languages in the world. ## Change - New file: **`README_hi.md`** (38,225 bytes; 309 lines), Devanagari throughout the prose. - Preserves all code blocks (8), commands, badges (5 shields), anchor links, `<a id>` markers, and the language-switcher header bar. - Placed `**हिन्दी**` between `ไทย` and `Deutsch` in the header. - Mirrors `README_de.md` formatting (≈19 kB siblings; size difference is the Devanagari UTF-8 byte cost, similar to `README_ja.md` at 24 kB). - Kept the `**You must legally obtain...**` paragraph verbatim in English, matching how German and Japanese siblings leave it untranslated. - Translated "Quick start" → `त्वरित शुरुआत`, "Showcases" → `उदाहरण`. Other navigation anchors translated to Devanagari slugs that should auto-generate correctly in GitHub. ## Out of scope - No source code change. - No CLI/MCP contract change. - No docs generation change (the docs:generate pipeline does not touch the root `README*.md` files; this is a language header entry under the project's existing translation convention). - No additional languages — keeping the PR focused on Hindi. ## Validation - Confirmed all badge URLs, anchor targets, and `docs/` links preserved. - Manual review: 21 anchored navigation links (mix of explicit + GitHub-auto-generated) match the corresponding translated headings. - Translation quality: aimed for natural-sounding technical Hindi rather than English calques; technical identifiers (MCP, Hopper, Ghidra, IDA, JEB, JADX, Binwalk, ASAR, etc.) kept verbatim per sibling convention. - Note: I cannot run the docs:check lint locally (no npm install in this environment); parent CI is expected to be the final source of truth for any generated metadata links. ## Open questions - Header entry position: I placed `**हिन्दी**` between `ไทย` and `Deutsch`. If the project keeps translations in chronological-add order and prefers a different slot, that's a one-line reorder. - GitHub anchor slugification for Devanagari: should work (consistent with how German umlauts resolve), but only github.com rendering can confirm. Happy to renumber or reposition the header entry on maintainer request. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-31 01:06:35 +00:00

closed this issue
added the
pull-request
label

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#5434

No description provided.

Rows
Columns