From: Matthew Wilcox <willy@infradead.org>
To: Daniel <danielmaraboo@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org
Subject: Re: [PATCH v4] docs: pt_BR: add initial Portuguese translation
Date: Tue, 3 Feb 2026 20:20:00 +0000 [thread overview]
Message-ID: <aYJYcBZh3fxvpXLM@casper.infradead.org> (raw)
In-Reply-To: <20260203184826.81594-1-danielmaraboo@gmail.com>
On Tue, Feb 03, 2026 at 03:48:20PM -0300, Daniel wrote:
> diff --git a/Documentation/translations/index.rst b/Documentation/translations/index.rst
> index b826c3479..409b6a84e 100644
> --- a/Documentation/translations/index.rst
> +++ b/Documentation/translations/index.rst
> @@ -11,10 +11,12 @@ Translations
> zh_TW/index
> it_IT/index
> ko_KR/index
> + pt_BR/index
> ja_JP/index
> sp_SP/index
>
>
> +
This seems an unnecessary blank line?
> +Becoming A Kernel Developer
> +---------------------------
Is there a reason to not translate this one heading?
I have a delicate question ... how different are Brazilian and European
Portuguese for technical documentation? We have similar questions for
other languages; for example we freely mix Commonwealth and American
spellings in the English documentation because they're mutually
intelligible, but split Traditional and Simplified Chinese because
they're quite different from each other.
next prev parent reply other threads:[~2026-02-03 20:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 18:48 [PATCH v4] docs: pt_BR: add initial Portuguese translation Daniel
2026-02-03 20:20 ` Matthew Wilcox [this message]
2026-02-03 20:55 ` Randy Dunlap
2026-02-03 21:02 ` Daniel Pereira
2026-02-03 21:04 ` 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=aYJYcBZh3fxvpXLM@casper.infradead.org \
--to=willy@infradead.org \
--cc=corbet@lwn.net \
--cc=danielmaraboo@gmail.com \
--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