From: Haoyang Liu <tttturtleruss@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>,
Dongliang Mu <dzm91@hust.edu.cn>,
Yanteng Si <si.yanteng@linux.dev>, Alex Shi <alexs@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools/docs/checktransupdate.py: use metadata to lookup origin path
Date: Tue, 10 Mar 2026 01:05:08 +0800 [thread overview]
Message-ID: <2bd7d364-6e23-4980-9852-b1561ac17709@gmail.com> (raw)
In-Reply-To: <87pl5dxfep.fsf@trenco.lwn.net>
On 3/9/2026 10:10 PM, Jonathan Corbet wrote:
> Haoyang LIU <tttturtleruss@gmail.com> writes:
>
>> The get_origin_path() function assumes that translation files have the
>> same relative path as their origin files, just with "translations/{locale}"
>> inserted after "Documentation/". However, this assumption is incorrect
>> for several translation files where the origin path differs. For example:
>> translations/zh_CN/dev-tools/gdb-kernel-debugging.rst
>> -> process/debugging/gdb-kernel-debugging.rst
> Honestly, rather than trying to work around such things, I think it
> would be far better to fix the places where the translated structure
> differs from the original. Those differences can only lead to
> confusion, and I've been trying to avoid creating any more of them.
Dear Jon,
That makes sense. I agree that keeping the translated directory
structure consistent with the original would avoid confusion and
reduce the need for special handling in the script.
I’ll take a look at the places where the structures differ and see
whether they can be aligned with the original layout instead.
Sincerely,
Haoyang
>
> Thanks,
>
> jon
--
Sincerely,
Haoyang
prev parent reply other threads:[~2026-03-09 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 9:58 [PATCH] tools/docs/checktransupdate.py: use metadata to lookup origin path Haoyang LIU
2026-03-09 14:10 ` Jonathan Corbet
2026-03-09 17:05 ` Haoyang Liu [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=2bd7d364-6e23-4980-9852-b1561ac17709@gmail.com \
--to=tttturtleruss@gmail.com \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=si.yanteng@linux.dev \
--cc=skhan@linuxfoundation.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