Re: [PATCH 4/4] docs/zh_TW: add missing :Original: fields

From: Weijie Yuan

Date: Fri Oct 02 2026 - 12:53:03 EST


Hi,

On 2026-09-29 17:40:18 +0300, Jani Nikula <jani.nikula@xxxxxxxxxxxxxxx> wrote:

> On Tue, 29 Sep 2026, Chen-Yu Yeh <chenyou910331@xxxxxxxxx> 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.

On 2026-10-01 17:00:23 +0300, Jani Nikula <jani.nikula@xxxxxxxxxxxxxxx> wrote:

> On Wed, 30 Sep 2026, 葉宸佑 <chenyou910331@xxxxxxxxx> wrote:
> > You are right, and I should have seen it -- the rest of this series is
> > built on that same expectation. checktransupdate.py also finds the
> > original purely from the path, which is why 1/4-3/4 move the files
> > rather than fix their :Original: fields. By the same token, at their old
> > paths the language switcher cannot pair them with their originals
> > either, which is a better argument for the moves than the one I gave.
>
> Oh, by the way, I do think the series as a whole is worthwhile cleanup,
> and having the :Original: fields is the current practice. Removing them
> should be a separate change.

I am a newcomer and might lack contextual information, but I don't see
anything rely heavily on this field either? I only find that on March
this year, Jon did not expect that the script checktransupdate.py uses
this field to get the original file of each translation.

So is this a convention or is there some additional circumstance that
forces us to keep this field?

Hmm, btw, I noticed that the Japanese translations do not have this
field.

Thanks.