From: Jonathan Corbet <corbet@lwn.net>
To: Wu XiangCheng <bobwxc@email.cn>
Cc: Alex Shi <alexs@kernel.org>,
Federico Vaga <federico.vaga@vaga.pv.it>,
Masahiro Yamada <masahiroy@kernel.org>,
Tsugikazu Shibata <tshibata@ab.jp.nec.com>,
SeongJae Park <sjpark@amazon.de>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC 0/2] Add a new translation tool scripts/trslt.py
Date: Thu, 15 Apr 2021 15:00:36 -0600 [thread overview]
Message-ID: <871rbbi7pn.fsf@meer.lwn.net> (raw)
In-Reply-To: <cover.1618208899.git.bobwxc@email.cn>
Wu XiangCheng <bobwxc@email.cn> writes:
> Hi all,
>
> This set of patches aim to add a new translation tool - trslt.py, which
> can control the transltions version corresponding to source files.
>
> For a long time, kernel documentation translations lacks a way to control the
> version corresponding to the source files. If you translate a file and then
> someone updates the source file, there will be a problem. It's hard to know
> which version the existing translation corresponds to, and even harder to sync
> them.
>
> The common way now is to check the date, but this is not exactly accurate,
> especially for documents that are often updated. And some translators write
> corresponding commit ID in the commit log for reference, it is a good way,
> but still a little troublesome.
>
> Thus, the purpose of ``trslt.py`` is to add a new annotating tag to the file
> to indicate corresponding version of the source file::
>
> .. translation_origin_commit: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
> The script will automatically copy file and generate tag when creating new
> translation, and give update suggestions based on those tags when updating
> translations.
>
> More details please read doc in [Patch 2/2].
So, like Federico, I'm unconvinced about putting this into the
translated text itself. This is metadata, and I'd put it with the rest
of the metadata. My own suggestion would be a tag like:
Translates: 6161a4b18a66 ("docs: reporting-issues: make people CC the regressions list")
It would be an analogue to the Fixes tag in this regard; you could have
more than one of them if need be.
I'm not sure we really need a script in the kernel tree for this; it
seems like what you really want is some sort of git commit hook. That
said, if you come up with something useful, we can certainly find a
place for it.
Thanks,
jon
next prev parent reply other threads:[~2021-04-15 21:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 7:04 Wu XiangCheng
2021-04-12 7:05 ` [PATCH 1/2] scripts: Add new translation tool trslt.py Wu XiangCheng
2021-04-12 7:05 ` [RFC 2/2] docs: doc-guide: Add document for scripts/trslt.py Wu XiangCheng
2021-04-13 23:27 ` [RFC 0/2] Add a new translation tool scripts/trslt.py Federico Vaga
2021-04-16 8:45 ` Wu X.C.
2021-04-15 21:00 ` Jonathan Corbet [this message]
2021-04-17 2:47 ` Wu X.C.
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=871rbbi7pn.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=alexs@kernel.org \
--cc=bobwxc@email.cn \
--cc=federico.vaga@vaga.pv.it \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=sjpark@amazon.de \
--cc=tshibata@ab.jp.nec.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®