Linux Documentation
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Daniel Pereira <danielmaraboo@gmail.com>
Cc: linux-doc@vger.kernel.org
Subject: Re: [PATCH 0/5] docs: translations: pt_BR: fix refs and start admin-guide
Date: Sat, 26 Sep 2026 09:26:22 -0600	[thread overview]
Message-ID: <87ik3s3ug1.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260916174136.48011-1-danielmaraboo@gmail.com>

Daniel Pereira <danielmaraboo@gmail.com> writes:

> This series has two parts.
>
> Patches 1 and 5 fix cross-references across the existing pt_BR
> translation.  Several documents pointed at the English version of files
> that are already translated, so a reader of the translation was sent
> back to the original.  In code-of-conduct.rst and cve.rst the effect was
> visible in the rendered text, which quoted the English title of the
> referenced document in the middle of a Portuguese sentence.  Nine pt_BR
> anchors were missing and are added here; other translations already
> define their own.  References whose target has no pt_BR translation are
> left pointing at the English document.
>
> Patches 2 to 4 start the admin-guide translation.  The index mirrors the
> section layout of the original and lists the pending documents under a
> Todolist marker, the same way zh_CN tracks its own, so that entries move
> into a toctree as they get translated.  README.rst and devices.rst are
> the first two documents.  For devices.rst the device registry itself is
> pulled in with a literal include of the original devices.txt, keeping
> the numbers in a single place.
>
> The series was built with "make htmldocs" and produces no new warnings;
> in particular there is no undefined label and no broken toctree entry.
> checkpatch is clean apart from the usual "does MAINTAINERS need
> updating?" advisory on the new files, which is already covered by
> F: Documentation/translations/pt_BR/.
>
> Daniel Pereira (5):
>   docs: translations: pt_BR: point refs at the translated documents
>   docs: translations: pt_BR: add admin-guide index
>   docs: translations: pt_BR: translate admin-guide/README.rst
>   docs: translations: pt_BR: translate admin-guide/devices.rst
>   docs: translations: pt_BR: point howto.rst at the translated documents

Series applied, thanks.

jon

      parent reply	other threads:[~2026-09-26 15:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-16 17:41 [PATCH 0/5] docs: translations: pt_BR: fix refs and start admin-guide Daniel Pereira
2026-09-16 17:41 ` [PATCH 1/5] docs: translations: pt_BR: point refs at the translated documents Daniel Pereira
2026-09-16 17:41 ` [PATCH 2/5] docs: translations: pt_BR: add admin-guide index Daniel Pereira
2026-09-16 17:41 ` [PATCH 3/5] docs: translations: pt_BR: translate admin-guide/README.rst Daniel Pereira
2026-09-16 17:41 ` [PATCH 4/5] docs: translations: pt_BR: translate admin-guide/devices.rst Daniel Pereira
2026-09-16 17:41 ` [PATCH 5/5] docs: translations: pt_BR: point howto.rst at the translated documents Daniel Pereira
2026-09-26 15:26 ` Jonathan Corbet [this message]

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=87ik3s3ug1.fsf@trenco.lwn.net \
    --to=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