Re: [PATCH v2] docs: zh_TW: process: localize terminologies and improve fluency in 8.Conclusion

[Dongliang Mu <dzm91@hust.edu.cn>]

On 7/13/26 10:44 AM, 葉宸佑 wrote:
> Hi Weijie,
>
>> I suspect that some contributors would run the get_maintainers.pl script
>> or b4 prep --auto-to-cc, so they did not cc Alex, as they didn't know
>> the current situation. Because I noticed that for both two versions,
>> Chen-yu didn't cc Alex or Dongliang or Yanteng. Am I right, @Chen-yu? ;-)
> Yes, exactly. For both v1 and v2 I ran get_maintainer.pl, which only
> lists Hu Haowen and the mailing lists for zh_TW files, so Alex and the
> zh_CN team were never on cc.
>
>> Given that this document has not been maintained for ~2 years and these
>> patches to the terminology actually don't have much significance, it
>> might be more appropriate to directly declare the status of Traditional
>> Chinese as "Orphan" provisionally for now, and remove it directly in the
>> near future, until Hao Wen's return and opinion. Or maybe, waiting for a
>> new good soul to take over, which is unpredictable.
> Before it comes to that: I would like to step up and help carry zh_TW
> forward. I am a native zh_TW speaker from Taiwan, and I understand
> this means staying with it, not a one-off effort.
>
> Dongliang, since you kindly offered to help review zh_TW patches:
> would you be open to doing this together -- either as co-maintainers,
> or with me listed as a reviewer (R:) first if that is a more
> reasonable starting point for a newcomer?

Chen-Yu,I would like to serve as co-maintainers to help maintain zh_TW. The 
script - tools/docs/checktransupdate.py can seamlessly work on zh_TW. 
This can help track the missing changes. But for the current situation 
of zh_TW, re-translation may be more efficient.

As discussed with Alex before, maybe zh_TW patches can first go to 
Alex's kernel tree and then push to Jon's tree. I am not sure if you are 
familar with the maintainer workflow. If not, this solution may be 
better for you to learn maintainer workflow.

Dongliang Mu

>
>>> To avoid scattering our efforts, I suggest we minimize fragmentation
>>> as much as possible. When it comes to technical documentation
>>> translation, not literary translation, a straightforward, unadorned,
>>> and free from misunderstandings is the best translation and easy to
>>> maintain. Let's keep thing simple, unless sth is really necessary.
> Alex, I think this concern is fair, and I have no intention of
> forking the translation effort. The scope I have in mind is
> deliberately narrow: keep zh_TW aligned with zh_CN in structure and
> coverage, and localize only where terminology genuinely differs
> (e.g. 軟體 vs 软件, 介面 vs 接口) -- exactly the kind of differences
> you mentioned. Plain, accurate technical translation, no literary
> rewriting.
>
> Weijie, as a first concrete step I will prepare a terminology series
> (rather than one-word-at-a-time patches, as you suggested) covering
> the existing process/ documents, and use it to build a small glossary
> that future patches and reviews can follow.
You can send a zh_TW tree-wide patchset to change them.
>
> Jon, if this direction sounds acceptable, I am happy to send a
> MAINTAINERS patch once the details are settled in this thread.
>
> Thanks,
> Chen-Yu