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, Daniel Pereira <danielmaraboo@gmail.com>
Subject: Re: [PATCH] docs: pt_BR: update minimal software requirements in changes.rst
Date: Fri, 15 May 2026 08:21:25 -0600	[thread overview]
Message-ID: <87ik8orbx6.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260505194143.32009-1-danielmaraboo@gmail.com>

Daniel Pereira <danielmaraboo@gmail.com> writes:

> Update the Brazilian Portuguese translation of changes.rst to align with
> the latest English version.
>
> Key changes include:
> - Updated minimum versions for Rust (1.85.0), bindgen (0.71.1), and
>   pahole (1.22).
> - Fixed ReST syntax for internal references (:ref:) and external links.
> - Corrected formatting for tool names and config options using inline
>   code backticks.
> - Synchronized technical descriptions for udev, kmod, and NFS-utils.
>
> Signed-off-by: Daniel Pereira <danielmaraboo@gmail.com>
> ---
>  .../translations/pt_BR/process/changes.rst    | 52 +++++++++----------
>  1 file changed, 26 insertions(+), 26 deletions(-)

This doesn't build...?

> Documentation/translations/pt_BR/process/changes.rst:37:
> ERROR: Malformed table.  Text in column margin in table line 7.
> 
> ====================== ===============
>         ======================================== Programa Versão mínima
>         Comando para verificar a versão ======================
>         =============== ======================================== GNU C 8.1
>         gcc --version Clang/LLVM (optional) 15.0.0 clang --version Rust
>         (optional) 1.85.0 rustc --version bindgen (optional) 0.71.1 bindgen
>         --version GNU make 4.0 make --version bash 4.2 bash --version
>         binutils 2.30 ld -v flex 2.5.35 flex --version gdb 7.2 gdb
>         --version bison 2.0 bison --version pahole 1.22 pahole --version
>         util-linux 2.10o mount --version kmod 13 kmod -V e2fsprogs 1.41.4
>         e2fsck -V jfsutils 1.1.3 fsck.jfs -V xfsprogs 2.6.0 xfs_db -V
>         squashfs-tools 4.0 mksquashfs -version btrfs-progs 0.18 btrfs
>         --version pcmciautils 004 pccardctl -V quota-tools 3.09 quota -V
>         PPP 2.4.0 pppd --version nfs-utils 1.0.5 showmount --version procps
>         3.2.0 ps --version udev 081 udevadm --version grub 0.93 grub
>         --version || grub-install --version mcelog 0.6 mcelog --version
>         iptables 1.4.2 iptables -V openssl & libcrypto 1.0.0 openssl
>         version bc 1.06.95 bc --version Sphinx\ [#f1]_ 3.4.3 sphinx-build
>         --version GNU tar 1.28 tar --version gtags (opcional) 6.6.5 gtags
>         --version mkimage (opcional) 2017.01 mkimage --version Python 3.9.x
>         python3 --version GNU AWK (opcional) 5.1.0 gawk --version
>         ====================== ===============
>         ======================================== [docutils]
>         /stuff/k/git/kernel/Documentation/translations/pt_BR/process/changes.rst:71:
>         WARNING: Footnote [#] is not referenced. [ref.footnote]
> 

jon

      reply	other threads:[~2026-05-15 14:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05 19:41 [PATCH] docs: pt_BR: update minimal software requirements in changes.rst Daniel Pereira
2026-05-15 14:21 ` 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=87ik8orbx6.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