All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chen-Yu Yeh <chenyou910331@gmail.com>, corbet@lwn.net, alexs@kernel.org
Cc: dzm91@hust.edu.cn, wy@wyuan.org, si.yanteng@linux.dev,
	srcres258@furdevs.cn, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Chen-Yu Yeh <chenyou910331@gmail.com>,
	Vegard Nossum <vegard.nossum@oracle.com>
Subject: Re: [PATCH 4/4] docs/zh_TW: add missing :Original: fields
Date: Tue, 29 Sep 2026 17:40:18 +0300	[thread overview]
Message-ID: <c719c6756f345c6c39db483654578ef09de1948f@intel.com> (raw)
In-Reply-To: <20260929131020.266120-5-chenyou910331@gmail.com>

On Tue, 29 Sep 2026, Chen-Yu Yeh <chenyou910331@gmail.com> wrote:
> Every zh_TW translation names the English document it mirrors in an
> :Original: field, except these four.  Add one to each, in the plain path
> form that automarkup turns into a link.

I'm wondering, are these :Original: fields useful anymore since the
translations extension adds the button to switch between languages?

The pretty much hard-coded expectation is that the English version at
path/to/foo.rst is the original, and its translations are at
translations/xx_YY/path/to/foo.rst.

I.e. neither the HTML nor the RST benefit from it, and it's just
repetition.

BR,
Jani.

>
> dev-tools/sparse.rst still carries the old plain-text header rather than
> the disclaimer include, so its field goes at the top of the file.
>
> With this, the only .rst files without the field are index.rst,
> disclaimer-zh_TW.rst and glossary.rst, none of which translates an
> English document.
>
> Signed-off-by: Chen-Yu Yeh <chenyou910331@gmail.com>
> ---
>  .../translations/zh_TW/admin-guide/clearing-warn-once.rst     | 2 ++
>  Documentation/translations/zh_TW/admin-guide/cpu-load.rst     | 2 ++
>  Documentation/translations/zh_TW/arch/index.rst               | 2 ++
>  Documentation/translations/zh_TW/dev-tools/sparse.rst         | 4 +++-
>  4 files changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/translations/zh_TW/admin-guide/clearing-warn-once.rst b/Documentation/translations/zh_TW/admin-guide/clearing-warn-once.rst
> index 95614600604c..15d54440d224 100644
> --- a/Documentation/translations/zh_TW/admin-guide/clearing-warn-once.rst
> +++ b/Documentation/translations/zh_TW/admin-guide/clearing-warn-once.rst
> @@ -2,6 +2,8 @@
>  
>  .. include:: ../disclaimer-zh_TW.rst
>  
> +:Original: Documentation/admin-guide/clearing-warn-once.rst
> +
>  清除 WARN_ONCE
>  --------------
>  
> diff --git a/Documentation/translations/zh_TW/admin-guide/cpu-load.rst b/Documentation/translations/zh_TW/admin-guide/cpu-load.rst
> index 20ec5bcd5f18..13f03195ac7e 100644
> --- a/Documentation/translations/zh_TW/admin-guide/cpu-load.rst
> +++ b/Documentation/translations/zh_TW/admin-guide/cpu-load.rst
> @@ -2,6 +2,8 @@
>  
>  .. include:: ../disclaimer-zh_TW.rst
>  
> +:Original: Documentation/admin-guide/cpu-load.rst
> +
>  ========
>  CPU 負載
>  ========
> diff --git a/Documentation/translations/zh_TW/arch/index.rst b/Documentation/translations/zh_TW/arch/index.rst
> index 7c0490589465..724468687c20 100644
> --- a/Documentation/translations/zh_TW/arch/index.rst
> +++ b/Documentation/translations/zh_TW/arch/index.rst
> @@ -1,5 +1,7 @@
>  .. SPDX-License-Identifier: GPL-2.0
>  
> +:Original: Documentation/arch/index.rst
> +
>  處理器體系結構
>  ==============
>  
> diff --git a/Documentation/translations/zh_TW/dev-tools/sparse.rst b/Documentation/translations/zh_TW/dev-tools/sparse.rst
> index 7a3487a7b2c7..7ca7fdf6e1e6 100644
> --- a/Documentation/translations/zh_TW/dev-tools/sparse.rst
> +++ b/Documentation/translations/zh_TW/dev-tools/sparse.rst
> @@ -1,4 +1,6 @@
> -Chinese translated version of Documentation/dev-tools/sparse.rst
> +:Original: Documentation/dev-tools/sparse.rst
> +
> +Chinese translated version of Documentation/dev-tools/sparse.rst
>  
>  If you have any comment or update to the content, please contact the
>  original document maintainer directly.  However, if you have a problem

-- 
Jani Nikula, Intel

  reply	other threads:[~2026-09-29 14:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29 13:10 [PATCH 0/4] docs/zh_TW: relocate translations to follow the English layout Chen-Yu Yeh
2026-09-29 13:10 ` [PATCH 1/4] docs/zh_TW: move security-bugs to process/ Chen-Yu Yeh
2026-10-02 14:31   ` Weijie Yuan
2026-10-03  9:53     ` 葉宸佑
2026-10-03  9:56       ` 葉宸佑
2026-10-03 10:02         ` Weijie Yuan
2026-09-29 13:10 ` [PATCH 2/4] docs/zh_TW: move magic-number to staging/ Chen-Yu Yeh
2026-10-03  4:08   ` Weijie Yuan
2026-09-29 13:10 ` [PATCH 3/4] docs/zh_TW: move gdb-kernel-debugging to process/debugging/ Chen-Yu Yeh
2026-10-03  4:19   ` Weijie Yuan
2026-10-03 10:22     ` 葉宸佑
2026-09-29 13:10 ` [PATCH 4/4] docs/zh_TW: add missing :Original: fields Chen-Yu Yeh
2026-09-29 14:40   ` Jani Nikula [this message]
2026-09-30 12:49     ` 葉宸佑
2026-10-01 14:00       ` Jani Nikula
2026-10-02  3:44         ` 葉宸佑
2026-10-02 16:51     ` Weijie Yuan
2026-10-03  4:22   ` Weijie Yuan

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=c719c6756f345c6c39db483654578ef09de1948f@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=alexs@kernel.org \
    --cc=chenyou910331@gmail.com \
    --cc=corbet@lwn.net \
    --cc=dzm91@hust.edu.cn \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=si.yanteng@linux.dev \
    --cc=srcres258@furdevs.cn \
    --cc=vegard.nossum@oracle.com \
    --cc=wy@wyuan.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.