From: Daniel Pereira <danielmaraboo@gmail.com>
To: corbet@lwn.net
Cc: linux-doc@vger.kernel.org, Daniel Pereira <danielmaraboo@gmail.com>
Subject: [PATCH 0/4] docs: pt_BR: process: Add remaining core process translations
Date: Wed, 9 Sep 2026 09:48:43 -0300 [thread overview]
Message-ID: <20260909124905.6156-1-danielmaraboo@gmail.com> (raw)
This patch series introduces new Portuguese (pt_BR) translations for core kernel process documentation files.
Changes included in this series:
- New translations for coding-style.rst, kernel-enforcement-statement.rst, maintainer-tip.rst, and submitting-patches.rst.
- Meticulous alignment of all section underlines in coding-style.rst to match the title lengths precisely, preventing Sphinx compilation warnings.
- Thorough localization of internal cross-references across these documents. We applied the `pt_BR_` prefix to anchors such as `pt_BR_describe_changes`, `pt_BR_backtraces`, `pt_BR_resend_reminders`, `pt_BR_split_changes`, `pt_BR_the_canonical_patch_format`, `pt_BR_interleaved_replies`, and `pt_BR_maintainer-tip-coding-style`. This prevents "duplicate label" warnings during global Sphinx builds.
- Cleaned up orphan labels (`tagging_people` and `explicit_in_reply_to`) that were completely unused internally to streamline the documentation.
- Improved readability of translated technical terms (e.g., using "comentários no fim da linha" instead of literal "comentários de cauda").
The entire series has been validated with checkpatch.pl and successfully passes `make htmldocs` without syntax errors or broken internal cross-references.
Daniel Pereira (4):
docs: pt_BR: translate coding-style.rst
docs: pt_BR: translate kernel-enforcement-statement.rst
docs: pt_BR: translate maintainer-tip.rst
docs: pt_BR: translate submitting-patches.rst
.../translations/pt_BR/process/2.Process.rst | 2 +-
.../pt_BR/process/coding-style.rst | 1318 +++++++++++++++++
.../translations/pt_BR/process/index.rst | 4 +
.../process/kernel-enforcement-statement.rst | 163 ++
.../pt_BR/process/maintainer-kvm-x86.rst | 6 +-
.../pt_BR/process/maintainer-tip.rst | 847 +++++++++++
.../pt_BR/process/submitting-patches.rst | 961 ++++++++++++
7 files changed, 3297 insertions(+), 4 deletions(-)
create mode 100644 Documentation/translations/pt_BR/process/coding-style.rst
create mode 100644 Documentation/translations/pt_BR/process/kernel-enforcement-statement.rst
create mode 100644 Documentation/translations/pt_BR/process/maintainer-tip.rst
create mode 100644 Documentation/translations/pt_BR/process/submitting-patches.rst
--
2.47.3
next reply other threads:[~2026-09-09 12:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 12:48 Daniel Pereira [this message]
2026-09-09 12:48 ` [PATCH 1/4] docs: pt_BR: translate coding-style.rst Daniel Pereira
2026-09-09 12:48 ` [PATCH 2/4] docs: pt_BR: translate kernel-enforcement-statement.rst Daniel Pereira
2026-09-09 12:48 ` [PATCH 3/4] docs: pt_BR: translate maintainer-tip.rst Daniel Pereira
2026-09-09 12:48 ` [PATCH 4/4] docs: pt_BR: translate submitting-patches.rst Daniel Pereira
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260909124905.6156-1-danielmaraboo@gmail.com \
--to=danielmaraboo@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox