[PR #6589] docs(pt-BR): translate remaining English passages #7382

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/6589
Author: @paulapeclat
Created: 10/23/2026
Status: 🔄 Open

Base: main ← Head: docs/pt-br-fixes


📝 Commits (1)

  • a46cf07 docs(pt-BR): translate remaining English passages and align native-engine wording

📊 Changes

1 file changed (+18 additions, -17 deletions)

View changed files

📝 docs/readme/README_pt-BR.md (+18 -17)

📄 Description

Summary

docs/readme/README_pt-BR.md still contained passages in English and one sentence that had drifted from the English README. This PR translates those passages and aligns the wording, so Portuguese readers get the full README in their language.

Problem and expected behavior

  • The "Rust binaries" row of the target table, the second paragraph of "Aviso legal" and the whole "Licença" section were untranslated.
  • The intro sentence listed only Hopper and Ghidra as native engines, while the English README lists Hopper, Ghidra and IDA.
  • The showcase image caption used "panoramização" while the heading and body use "panorâmica".

Expected: the pt-BR README matches the English meaning in these places, in Portuguese, with consistent terminology.

Change and scope

  • Translated the Rust row, using the current English content (crate names, versions, sources and dependency edges; built-in static ELF/PE/thin Mach-O inspection).
  • Translated the responsible-use paragraph and the License section, keeping links, product names and the bold emphasis.
  • Added IDA to the native-engine sentence and replaced "nenhum dos dois motores" with "um motor de análise nativa", matching the English wording.
  • Unified "panorâmica" in the image caption.

Not included: the other sections where the pt-BR README lags behind the English one (missing table rows, the Linux ps note, REA_MCP_INPUT_SCHEMA_PROFILE, update details, objdump/Rizin paragraph). Those can follow in a separate PR.

Contribution scope: not applicable (documentation-only translation fix within existing boundaries).

Contract and boundary impact

  • Semantic owner and earliest changed stage: docs/readme/README_pt-BR.md only.
  • Contribution scope fit and linked maintainer decision: 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 (if applicable): not applicable.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: none.

Expected effects (check known effects; use documentation-only on its own).
Unchecked items do not establish absence; leave uncertainties visible.

  • Read existing files or captured data.
  • Launch or attach to a process.
  • Inject instrumentation or run scripts/code.
  • Change process memory, registers, files, or configuration.
  • Contact network services.
  • Recover protected code or work around protections.
  • Documentation or usability only; no target interaction.
  • Not sure yet; investigation or maintainer guidance needed.

Evidence and regression coverage

  • Tests added or updated: none (documentation only).
  • Base reproduction or other evidence: source comparison of README_pt-BR.md against README.md on main.
  • User-visible CLI/MCP output (if applicable): not applicable.
  • Remaining proof gaps: rendered Markdown not checked beyond the GitHub diff view.

Validation performed

  • git diff upstream/main -- docs/readme/README_pt-BR.md — 1 file changed, 18 insertions, 17 deletions; only the passages listed above.
  • No npm checks were run (documentation-only change).

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: <@paulapeclat>

  • 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/6589 **Author:** [@paulapeclat](https://github.com/paulapeclat) **Created:** 10/23/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `docs/pt-br-fixes` --- ### 📝 Commits (1) - [`a46cf07`](https://github.com/morluto/rea/commit/a46cf07bec67eba20b1b3085f57cf5317727b33a) docs(pt-BR): translate remaining English passages and align native-engine wording ### 📊 Changes **1 file changed** (+18 additions, -17 deletions) <details> <summary>View changed files</summary> 📝 `docs/readme/README_pt-BR.md` (+18 -17) </details> ### 📄 Description ## Summary `docs/readme/README_pt-BR.md` still contained passages in English and one sentence that had drifted from the English README. This PR translates those passages and aligns the wording, so Portuguese readers get the full README in their language. ## Problem and expected behavior - The "Rust binaries" row of the target table, the second paragraph of "Aviso legal" and the whole "Licença" section were untranslated. - The intro sentence listed only Hopper and Ghidra as native engines, while the English README lists Hopper, Ghidra and IDA. - The showcase image caption used "panoramização" while the heading and body use "panorâmica". Expected: the pt-BR README matches the English meaning in these places, in Portuguese, with consistent terminology. ## Change and scope - Translated the Rust row, using the current English content (crate names, versions, sources and dependency edges; built-in static ELF/PE/thin Mach-O inspection). - Translated the responsible-use paragraph and the License section, keeping links, product names and the bold emphasis. - Added IDA to the native-engine sentence and replaced "nenhum dos dois motores" with "um motor de análise nativa", matching the English wording. - Unified "panorâmica" in the image caption. Not included: the other sections where the pt-BR README lags behind the English one (missing table rows, the Linux `ps` note, `REA_MCP_INPUT_SCHEMA_PROFILE`, update details, objdump/Rizin paragraph). Those can follow in a separate PR. Contribution scope: not applicable (documentation-only translation fix within existing boundaries). ## Contract and boundary impact - Semantic owner and earliest changed stage: `docs/readme/README_pt-BR.md` only. - Contribution scope fit and linked maintainer decision: 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 (if applicable): not applicable. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: none. Expected effects (check known effects; use documentation-only on its own). Unchecked items do not establish absence; leave uncertainties visible. - [ ] Read existing files or captured data. - [ ] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [x] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests added or updated: none (documentation only). - Base reproduction or other evidence: source comparison of `README_pt-BR.md` against `README.md` on `main`. - User-visible CLI/MCP output (if applicable): not applicable. - Remaining proof gaps: rendered Markdown not checked beyond the GitHub diff view. ## Validation performed - `git diff upstream/main -- docs/readme/README_pt-BR.md` — 1 file changed, 18 insertions, 17 deletions; only the passages listed above. - No npm checks were run (documentation-only change). ## 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: <@paulapeclat> - [ ] 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>
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#7382
No description provided.