[PR #4971] docs(i18n): add Azerbaijani README and sync Turkish edition #6704

Open
opened 2026-11-01 21:42:25 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4971
Author: @abdullaabdullazade
Created: 10/18/2026
Status: 🔄 Open

Base: main ← Head: docs/az-tr-readme


📝 Commits (2)

  • 12e5d90 docs(i18n): sync Turkish README with the English edition
  • 49f9f1d docs(i18n): add Azerbaijani README edition

📊 Changes

65 files changed (+55037 additions, -41638 deletions)

View changed files

📝 README.md (+1 -1)
📝 docs/readme/README_ar.md (+1 -1)
➕ docs/readme/README_az.md (+401 -0)
📝 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 (+32 -12)
📝 docs/readme/README_uk.md (+1 -1)
📝 docs/readme/README_vi.md (+1 -1)

...and 45 more files

📄 Description

Summary

Adds an Azerbaijani (az) README edition and brings the Turkish README back in line with the current English README, section for section.

Problem and expected behavior

  • There was no Azerbaijani README.
  • docs/readme/README_tr.md had fallen behind README.md. It was missing the Linux procps ps prerequisite, the rea --update alias and updater output-limit paragraphs, the GNU objdump/Rizin paragraph, the JavaScript-row ps requirement and the Hopper first-run session guidance. It also had wording drift in the .NET row and the bug-report FAQ, and the disclaimer paragraphs were in a different order.

Expected: every README edition follows the English structure, links and commands.

Change and scope

  • docs/readme/README_az.md: a full translation of README.md. Commands, code blocks, paths, product names and link targets are unchanged. Website links point to the English site, the same as the Malayalam edition, because there is no Azerbaijani website translation.
  • docs/readme/README_tr.md: adds the missing sections and corrects the drift listed above. The objdump/Rizin link moves from the section navigation into the body, where the English README has it.
  • An Azərbaycanca link is added to the language navigation of README.md and all translated editions.
  • website/locales/languages.json now registers az, which keeps the README/website inventory contract intact. This follows the same pattern as b27e1a74c (Malayalam): website.py sync and translations extract regenerated the shared navigation, messages.pot and the PO source references. website/locales/az/messages.po is untranslated, so its pages use the labeled, nonindexable English fallback. A short note was added to website/locales/README.md.

Not included: translating the Azerbaijani website catalog.

Contract and boundary impact

  • Semantic owner and earliest changed stage: README editions and the website language inventory

  • Contribution scope fit and linked maintainer decision: not applicable (documentation/translation)

  • 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 (if applicable): not applicable

  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: none; no build outputs committed

  • Documentation or usability only; no target interaction.

Evidence and regression coverage

  • Tests added or updated: none. The existing README consistency and doc-facts checks cover command and link parity.
  • Base reproduction or other evidence: source and link comparison against README.md
  • User-visible CLI/MCP output (if applicable): not applicable
  • Remaining proof gaps: no native Azerbaijani/Turkish reviewer yet; no browser layout check of the generated /az/ fallback pages

Validation performed

  • npm run docs:check: passed (including check-doc-facts README link parity and readmeConsistency.test.ts, 5/5)
  • npx vitest run tests/boundary/filesystem/documentationFacts.test.ts: passed
  • python3 scripts/website.py check: passed; az: 19 English fallback pages, marked noindex
  • npx oxfmt --check on the changed Markdown/JSON: clean after formatting

Compatibility, safety, and release

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

Author readiness

Human owner: @abdullaabdullazade

  • 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/4971 **Author:** [@abdullaabdullazade](https://github.com/abdullaabdullazade) **Created:** 10/18/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `docs/az-tr-readme` --- ### 📝 Commits (2) - [`12e5d90`](https://github.com/morluto/rea/commit/12e5d90842a893884a1b34acac9a4a7c95460d16) docs(i18n): sync Turkish README with the English edition - [`49f9f1d`](https://github.com/morluto/rea/commit/49f9f1dc14c2952c7377eec08f3c0f1308c62da1) docs(i18n): add Azerbaijani README edition ### 📊 Changes **65 files changed** (+55037 additions, -41638 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -1) 📝 `docs/readme/README_ar.md` (+1 -1) ➕ `docs/readme/README_az.md` (+401 -0) 📝 `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` (+32 -12) 📝 `docs/readme/README_uk.md` (+1 -1) 📝 `docs/readme/README_vi.md` (+1 -1) _...and 45 more files_ </details> ### 📄 Description ## Summary Adds an Azerbaijani (`az`) README edition and brings the Turkish README back in line with the current English README, section for section. ## Problem and expected behavior - There was no Azerbaijani README. - `docs/readme/README_tr.md` had fallen behind `README.md`. It was missing the Linux procps `ps` prerequisite, the `rea --update` alias and updater output-limit paragraphs, the GNU objdump/Rizin paragraph, the JavaScript-row `ps` requirement and the Hopper first-run session guidance. It also had wording drift in the .NET row and the bug-report FAQ, and the disclaimer paragraphs were in a different order. Expected: every README edition follows the English structure, links and commands. ## Change and scope - `docs/readme/README_az.md`: a full translation of `README.md`. Commands, code blocks, paths, product names and link targets are unchanged. Website links point to the English site, the same as the Malayalam edition, because there is no Azerbaijani website translation. - `docs/readme/README_tr.md`: adds the missing sections and corrects the drift listed above. The objdump/Rizin link moves from the section navigation into the body, where the English README has it. - An `Azərbaycanca` link is added to the language navigation of `README.md` and all translated editions. - `website/locales/languages.json` now registers `az`, which keeps the README/website inventory contract intact. This follows the same pattern as b27e1a74c (Malayalam): `website.py sync` and `translations extract` regenerated the shared navigation, `messages.pot` and the PO source references. `website/locales/az/messages.po` is untranslated, so its pages use the labeled, nonindexable English fallback. A short note was added to `website/locales/README.md`. Not included: translating the Azerbaijani website catalog. ## Contract and boundary impact - Semantic owner and earliest changed stage: README editions and the website language inventory - Contribution scope fit and linked maintainer decision: not applicable (documentation/translation) - 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 (if applicable): not applicable - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: none; no build outputs committed - [x] Documentation or usability only; no target interaction. ## Evidence and regression coverage - Tests added or updated: none. The existing README consistency and doc-facts checks cover command and link parity. - Base reproduction or other evidence: source and link comparison against `README.md` - User-visible CLI/MCP output (if applicable): not applicable - Remaining proof gaps: no native Azerbaijani/Turkish reviewer yet; no browser layout check of the generated `/az/` fallback pages ## Validation performed - `npm run docs:check`: passed (including `check-doc-facts` README link parity and `readmeConsistency.test.ts`, 5/5) - `npx vitest run tests/boundary/filesystem/documentationFacts.test.ts`: passed - `python3 scripts/website.py check`: passed; `az: 19 English fallback pages, marked noindex` - `npx oxfmt --check` on the changed Markdown/JSON: clean after formatting ## Compatibility, safety, and release - Breaking changes or migration steps: none - Real Hopper/Ghidra, browser, or OS coverage: not applicable - Package or release metadata impact: none - Security, privacy, process, or containment review: not applicable ## Author readiness Human owner: @abdullaabdullazade - [ ] 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 - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] 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. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [x] User-visible CLI/MCP changes include representative output. - [x] 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>
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#6704
No description provided.