rust-lang / rust-lang/book

Brazilian Portuguese Translation

Open
#448 8 comments 11 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

blocked upstream Enhancement Translations
Dominant language
Rust
Stars
18.3k
Forks
4.1k
Avg merge
14m
Merged PRs (30d)
1

Description

Hey there! Following our exchange on Hacker News yesterday, I've started translating the new version of the book to Brazilian Portuguese. I've translated the first part of the intro (to contextualize the book to potential readers) and I'll focus my efforts on chapters 2, 3, 4, and 6, as per your advice. (Chapter 3 has some translated parts already)

Like on #375, I've created a new repo/github pages site for the translation:

Compiled Site: https://coreh.github.io/rust-book-pt-br/
Repo: https://github.com/coreh/rust-book-pt-br

Once I have more content available, and the mdbook side of things is unblocked, I can structure my translation in the right format, and open a PR to this repo.

Quick question: I'm currently planning to translate non-standard library and non-crate-specific trait, struct and file names to Portuguese, (e.g. having Usuario instead of User, but preserving names like Box or rand::thread_rng() in English). This seems to be the trend among most programming books in Brazilian Portuguese, for didactical reasons, since it eases a bit of the cognitive load on non-english speaking readers, while preserving correctness. Are you okay with that approach, or would you like me to preserve the code examples as-is?

Thanks in advance!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked rust-book-pt-br repository and compiled site, then review the translation work for the introduction and chapters 2, 3, 4, and 6. Check the mdbook integration once it is unblocked; done means the translation is structured in the format expected by this repository and its terminology approach is approved.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
documentation, localization
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.