mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Akira Yokosawa <akiyks@gmail.com>
To: corbet@lwn.net
Cc: alexs@kernel.org, chengziqiu@hust.edu.cn, dzm91@hust.edu.cn,
	hust-os-kernel-patches@googlegroups.com,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	siyanteng@loongson.cn, Vegard Nossum <vegard.nossum@oracle.com>,
	Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH] scripts: use ':Original:' tag to locate the origin file
Date: Sat, 14 Sep 2024 12:47:34 +0900	[thread overview]
Message-ID: <2704d2a7-b2cc-4586-8608-10aabbdb91f3@gmail.com> (raw)
In-Reply-To: <875xqz39gf.fsf@trenco.lwn.net>

[+CC: Vegard]

Hi,

On Fri, 13 Sep 2024 08:38:24 -0600, Jonathan Corbet wrote:
> Cheng Ziqiu <chengziqiu@hust.edu.cn> writes:
> 
>> Simply substitute path may cause file finding failed
>> if we have a different dir map for translation. The
>> ':Original:' tag could be used to locate the origin
>> file if both the tag and file exist.
>>
>> Signed-off-by: Cheng Ziqiu <chengziqiu@hust.edu.cn>
>> ---
>>  scripts/checktransupdate.py | 13 +++++++++++++
>>  1 file changed, 13 insertions(+)
> 
> Perhaps we need this, but I would really rather move any files that
> don't conform to the English-language directory structure.  Having them
> be anything but the same can only lead to this sort of confusion.

+1

Furthermore, the "translations" extension for htmldocs available since
v6.8 at:
    Documentation/sphinx/translations.py
assumes the same structure as the English one.

It might be nice for this script to warn about translation docs
whose positions don't match the assumption.

        Thanks, Akira

> 
> Thanks,
> 
> jon


      reply	other threads:[~2024-09-14  3:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-13  8:16 Cheng Ziqiu
2024-09-13 11:23 ` Dongliang Mu
2024-09-13 14:38 ` Jonathan Corbet
2024-09-14  3:47   ` Akira Yokosawa [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=2704d2a7-b2cc-4586-8608-10aabbdb91f3@gmail.com \
    --to=akiyks@gmail.com \
    --cc=alexs@kernel.org \
    --cc=chengziqiu@hust.edu.cn \
    --cc=corbet@lwn.net \
    --cc=dzm91@hust.edu.cn \
    --cc=hust-os-kernel-patches@googlegroups.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=siyanteng@loongson.cn \
    --cc=vegard.nossum@oracle.com \
    /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

all inboxes | Powered by JetHome®