Re: [PATCH] docs: translations: pt_BR: add maintainer PGP guide

From: Daniel Pereira

Date: Wed Oct 28 2026 - 16:30:11 EST


On Wed, Oct 28, 2026, Gabriel Ribeiro <ic.gabrielribeiro@xxxxxxxxx> wrote:

> docs: translations: pt_BR: add maintainer PGP guide
>
> Translate the maintainer PGP guide into Brazilian Portuguese and add it
> to the pt_BR process index.

Hi Gabriel,

Thanks for the patch. I applied it on top of your programming-language.rst
patch (index.rst depends on it), compared the translation against the
original, and ran a full make htmldocs. No warnings were emitted for this
file, but I found a few things, commented inline below.

Also, checkpatch warns about a commit message body line over 75 columns
(the "Translate the maintainer PGP guide ..." line quoted above). Please
wrap it. The MAINTAINERS warning can be ignored, since
Documentation/translations/pt_BR/ is already covered.

> +++ b/Documentation/translations/pt_BR/process/maintainer-pgp-guide.rst

> +- Snapshots periódicas de versões (tarballs)

I believe it should be "periódicos", since "snapshot" is masculine.

> +- Os tarballs vêm acompanhados de assinaturas PGP destacadas.

"Separadas" sounds more natural to me for "detached signatures", but this
is a preference.

> +Desde o comprometimento de sistemas centrais do kernel.org em 2011, o
> +princípio operacional do projeto Kernel Archives é presumir que qualquer

The original says "the main operating principle", so "principal" got
dropped here.

> +.. _pt_BR_devs_not_infra:

Same for pt_BR_pgp_tools, pt_BR_protect_your_key, pt_BR_smartcards,
pt_BR_pgp_with_git, pt_BR_kernel_identities and
pt_BR_kernel_org_trust_repository: none of these labels is referenced
anywhere in the tree. The ones that matter are pt_BR_pgpguide (document
anchor) and pt_BR_verify_identities (used by :ref:). The original has the
same unused labels, so keeping or dropping them is a matter of taste.

> +- Chaves **[S]** podem ser usadas para assinar.

(Also for the [E]/[A]/[C] items.) These end with a period and the original
ones do not. Not a problem, just a difference.

> +Use uma frase secreta forte
> +--------------------------------

The underline is longer than the title (27 vs 32 characters). RST accepts
it, but the original keeps them the same length. The same happens at
"Entenda as subchaves PGP", "Use o gpg-agent via SSH", "Crie commits
assinados" and "Instale e configure o patatt".

> +- `Nitrokey Start <pt_BR_nitrokey_start_>`_: hardware aberto e software

Instead of the embedded alias with a separate prefixed target, you can
keep the original form:

`Nitrokey Start`_
.. _`Nitrokey Start`: https://www.nitrokey.com/products/nitrokeys

The pt_BR_ prefix only matters for labels used with :ref:, which are
global; hyperlink targets are local to the file. The embedded-alias form
also makes docutils report a duplicate-name INFO for "Proteção da
integridade do código", which appears twice.

> + resistente a adulterações e com mais recursos de segurança e formatos
> + USB.
> + Oferece suporte à criptografia de curva elíptica (ED25519 e NISTP).

"USB." is left alone on a line and "Oferece suporte..." starts on the
next one; the wrapping could be adjusted.

> +``key 1`` (é a primeira da lista, a subchave **[E]**):
> +
> + gpg> key 1

This one is a real bug: the paragraph is missing the "::" at the end. The
original ends with ")::". Without it, the "gpg> key 1" line is not a
literal block; in the generated HTML it comes out as a blockquote. Sphinx
does not warn about this, so a clean build does not catch it.

> +qual chave está “selecionada”. Ele funciona como um *alternador*: Se você

"Se" should be lowercase after the colon.

> +Use o repositório de chaves confiáveis do kernel.org

The original heading is "Using the kernel.org web of trust repository",
so "web of trust" got lost here.

> +`adicione o UID à sua chave <pt_BR_add_kernel_uid_>`_ para tornar o WKD

The link text in the original is "add the kernel.org UID to your key", so
"do kernel.org" got lost.

Everything else matches the original: the remaining 40 literal blocks are
byte-identical, URLs, e-mail addresses and numbers match, and the heading
structure and notes/warnings are the same.

With the "::", the lowercase "Se", "periódicos" and the commit message
wrapping fixed, this looks good to me.

Thanks,
Daniel