From: weibu@redadmin.org
To: Akira Yokosawa <akiyks@gmail.com>
Cc: corbet@lwn.net, shibata@linuxfoundation.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Subject: [PATCH] docs: ja_JP: Move submitting-patches to process/ and add to build
Date: Mon, 27 Oct 2025 13:25:37 +0900 [thread overview]
Message-ID: <1a97317518d8dcd7d5f0aea898e21f09@redadmin.org> (raw)
In-Reply-To: <67d1cfd2-a3e3-4a3f-89f5-38e822321578@gmail.com>
Hi Akira-san,
Thank you for the detailed review. I will work on a v2 patch based on
your suggestions.
Thanks, Akiyoshi Kurita
2025-10-27 11:53 に Akira Yokosawa さんは書きました:
> Hi Kurita-san,
>
> Thank for your continued work on this!
>
> On Sat, 25 Oct 2025 08:54:37 +0900, Akiyoshi Kurita wrote:
>> As requested by Jonathan, move the Japanese translation of
>> 'SubmittingPatches' to its proper location under 'process/' and
>> convert it to reStructuredText.
>
> In https://lore.kernel.org/87jz0xbk6f.fsf@trenco.lwn.net/, Jon said:
>
>>> That said ... this is not an RST file, and won't be pulled into the
>>> docs
>>> build. I would *love* to see a patch that moves this file into its
>>> proper location under .../process/ and brings it into the build.
>
> This patch does the *minimal* thing, namely the rename of the file,
> with minor changes near the top of the doc.
>
> Yes, the resulting .rst doesn't cause any *new* warnings from Sphinx,
> but looking at the resulting HTML (or PDF), I don't think the rendered
> page looks nice.
>
> I'm wondering if this is what Jon would love to see. (Well, Jon doesn't
> read Japanese and would not mind.)
>
> Of course, I understand you are going to do both translation and reST
> markup
> updates as follow-up changes. But I'd rather refrain from exposing
> work-in-progress doc in the translations docs.
>
> Please read on in-line comments below:
>
>>
>> This patch also wires the new file into the Japanese documentation's
>> toctree, allowing it to be included in the Sphinx build.
>>
>> Signed-off-by: Akiyoshi Kurita <weibu@redadmin.org>
>> ---
>> Documentation/translations/ja_JP/index.rst | 1 +
>> .../submitting-patches.rst} | 61
>> ++++++++++---------
>> 2 files changed, 32 insertions(+), 30 deletions(-)
>> rename Documentation/translations/ja_JP/{SubmittingPatches =>
>> process/submitting-patches.rst} (96%)
>>
>> diff --git a/Documentation/translations/ja_JP/index.rst
>> b/Documentation/translations/ja_JP/index.rst
>> index 4159b417bfdd..8e01619d4170 100644
>> --- a/Documentation/translations/ja_JP/index.rst
>> +++ b/Documentation/translations/ja_JP/index.rst
>> @@ -11,6 +11,7 @@
>> .. toctree::
>> :maxdepth: 1
>>
>> + process/submitting-patches
>
> This should come below process/howto. Still, as I said above, I think
> this
> addition is premature. One option would be to put a fat warning at the
> top
> of the doc saying "This section is work-in-progress!!", or so.
>
>> disclaimer-ja_JP
>> process/howto
>> process/submit-checklist
>> diff --git a/Documentation/translations/ja_JP/SubmittingPatches
>> b/Documentation/translations/ja_JP/process/submitting-patches.rst
>> similarity index 96%
>> rename from Documentation/translations/ja_JP/SubmittingPatches
>> rename to
>> Documentation/translations/ja_JP/process/submitting-patches.rst
>> index b950347b5993..4bfa84cc705d 100644
>> --- a/Documentation/translations/ja_JP/SubmittingPatches
>> +++ b/Documentation/translations/ja_JP/process/submitting-patches.rst
>> @@ -1,33 +1,34 @@
>> -NOTE:
>> -This is a version of Documentation/process/submitting-patches.rst
>> into Japanese.
>> -This document is maintained by Keiichi KII <k-keiichi@bx.jp.nec.com>
>> -and the JF Project team <http://www.linux.or.jp/JF/>.
>> -If you find any difference between this document and the original
>> file
>> -or a problem with the translation,
>> -please contact the maintainer of this file or JF project.
>> -
>> -Please also note that the purpose of this file is to be easier to
>> read
>> -for non English (read: Japanese) speakers and is not intended as a
>> -fork. So if you have any comments or updates of this file, please try
>> -to update the original English file first.
>> -
>> -Last Updated: 2011/06/09
>> -
>> -==================================
>> -これは、
>> -linux-2.6.39/Documentation/process/submitting-patches.rst の和訳
>> -です。
>> -翻訳団体: JF プロジェクト < http://www.linux.or.jp/JF/ >
>> -翻訳日: 2011/06/09
>> -翻訳者: Keiichi Kii <k-keiichi at bx dot jp dot nec dot com>
>> -校正者: Masanari Kobayashi さん <zap03216 at nifty dot ne dot jp>
>> - Matsukura さん <nbh--mats at nifty dot com>
>> - Takeshi Hamasaki さん <hmatrjp at users dot sourceforge dot
>> jp>
>> -==================================
>> -
>> - Linux カーネルに変更を加えるための Howto
>> - 又は
>> - かの Linus Torvalds の取り扱い説明書
>> +..
>> + NOTE:
>> + This is a version of
>> Documentation/process/submitting-patches.rst into Japanese.
>> + This document is maintained by Keiichi KII
>> <k-keiichi@bx.jp.nec.com>
>> + and the JF Project team <http://www.linux.or.jp/JF/>.
>> + If you find any difference between this document and the
>> original file
>> + or a problem with the translation,
>> + please contact the maintainer of this file or JF project.
>> +
>> + Please also note that the purpose of this file is to be easier
>> to read
>> + for non English (read: Japanese) speakers and is not intended as
>> a
>> + fork. So if you have any comments or updates of this file,
>> please try
>> + to update the original English file first.
>> +
>> + Last Updated: 2011/06/09
>> +
>> + ==================================
>> + これは、
>> + linux-2.6.39/Documentation/process/submitting-patches.rst の和訳
>> + です。
>> + 翻訳団体: JF プロジェクト < http://www.linux.or.jp/JF/ >
>> + 翻訳日: 2011/06/09
>> + 翻訳者: Keiichi Kii <k-keiichi at bx dot jp dot nec dot com>
>> + 校正者: Masanari Kobayashi さん <zap03216 at nifty dot ne dot jp>
>> + Matsukura さん <nbh--mats at nifty dot com>
>> + Takeshi Hamasaki さん <hmatrjp at users dot sourceforge dot
>> jp>
>> + ==================================
>
> This historic contribution record can be removed. The same happened in
> howto.rst when Shibata-san did the conversion in commit f012733894d3
> ("Documentation: Add HOWTO Japanese translation into rst based build
> system").
>
> Instead, please put a translation note referencing the disclaimer
> under the document title as is done in (ja_JP's) howto.rst and
> submit-checklist.rst.
>
>> +
>> +========================================
>> +Linux カーネルに変更を加えるための Howto
>> +========================================
>
> Title of the original now reads:
>
> Submitting patches: the essential guide to getting your code into the
> kernel
>
> Back in 2005, it read:
>
> How to Get Your Change Into the Linux Kernel
> or
> Care And Operation Of Your Linus Torvalds
>
> And the Japanese translation has never had the title updated ...
>
> Probably you can align the title with the current one.
>
> As before, if you are not sure of the way to do, please ask me
> before submitting a next version.
>
> Thanks, Akira
>
>>
>> Linux カーネルに変更を加えたいと思っている個人又は会社にとって、パッ
>> チの投稿に関連した仕組みに慣れていなければ、その過程は時々みなさんを
prev parent reply other threads:[~2025-10-27 4:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 23:54 [PATCH] Subject: [PATCH] docs: ja_JP: Move submitting-patches to process/ and add to build Akiyoshi Kurita
2025-10-27 2:53 ` Akira Yokosawa
2025-10-27 4:25 ` weibu [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=1a97317518d8dcd7d5f0aea898e21f09@redadmin.org \
--to=weibu@redadmin.org \
--cc=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shibata@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