From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-184.mta0.migadu.com (out-184.mta0.migadu.com [91.218.175.184]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A3C592989B5 for ; Sat, 11 Jul 2026 17:21:56 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.184 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783790518; cv=none; b=I9sACg1K27s5GrR2uAieBApwRbW5M+fl/ph901WQwS4Bo7O5UmA1AmqcZnpJRXWDILshlsoTEs0l3cbS949VR/IMN+fvfNLYRvcLzOUmIXDgDcBvjTISjznEbog1xriJYWRyvBFVKvRfN5/7MKBaeygsQ1XNpwul9XQdcUNyMWs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783790518; c=relaxed/simple; bh=JAx9OBbyCf7VDk3R8nN+a52HruKSIrRfL8jkjmfaCYY=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=L7Ak6y91jHrHoVV41MQQqCRf/VEVZCgTErFrmE/NztIl8n1KOX8glOFyInk2yC8H5kBZBJrQvBDghf6wpyyPtV0L4UOXJNFDhGi7+m2Ma7BhElq8snu1WflycXa8jArwn3OOqoQ4/UyUuHyhonu1wBucoddoYi4IYdaGdSJU4lI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=wyuan.org; spf=pass smtp.mailfrom=wyuan.org; dkim=pass (2048-bit key) header.d=wyuan.org header.i=@wyuan.org header.b=wm4GsIy2; arc=none smtp.client-ip=91.218.175.184 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=wyuan.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=wyuan.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=wyuan.org header.i=@wyuan.org header.b="wm4GsIy2" Date: Sun, 12 Jul 2026 01:21:37 +0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wyuan.org; s=key1; t=1783790514; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=g1wJCJB7Ko+EDwFElwOX16uuWigql3hwBssF2zT1cOQ=; b=wm4GsIy2tBuu+rGSTJSoEDOr2VG1XmqPnhTbpxFm9x6oj8jK5OFmHUjDqOphF3Zf2qvero y360+jf5S8S3vFI91/Qb8KhiZo4SlPLtKh7kYacCjyB/6mX9BmCQxqpcI/xfn6frEmJvUl gQD/1C475Ru4zQm1WjhFSE/LlGYe1e3ZkKU1Y8ubW68NYO2ebtBaOFcSpHlVTJO4nMSFI5 4E3rVFDwVQbODlOincyiQxOGVGKNw2jGggWSFC7zD0mVZ88MzwtSEY0c/N5F63ojV6Uqx1 p+lEYrV+jmbuoYJBtxkPFXCiqIAsS9Np1x81aNUqZf2sqouqBvO4wDTST5I/7Q== X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Weijie Yuan To: =?utf-8?B?6JGJ5a645L2R?= Cc: Dongliang Mu , Hu Haowen <2023002089@link.tyut.edu.cn>, Jonathan Corbet , Shuah Khan , Dongliang Mu , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Yuchen Tian , Alex Shi , Yanteng Si Subject: Re: [PATCH v2] docs: zh_TW: process: localize terminologies and improve fluency in 8.Conclusion Message-ID: References: <20260603082531.263115-1-chenyou910331@gmail.com> <57e42f43-44dd-4b22-8d81-c88e20016138@hust.edu.cn> Precedence: bulk X-Mailing-List: linux-doc@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Migadu-Flow: FLOW_OUT On Sat, Jul 11, 2026 at 02:01:46AM +0800, 葉宸佑 wrote: > Hi Weijie, > > > I think currently having Alex apply your patch is a temporary measure, > > because the maintainer of traditional Chinese seems unlikely to be > > available in the near future. > > Thanks for taking the time to explain the bigger picture in such detail. > Details. I understand the concern: accepting individual fixes doesn’t… > Solve the underlying problem that zh_TW documents have been facing. > Stagnant for a long time. So I'm very glad and grateful to hear more people's opinions. Of course, that's only my wish, I have no intention of forcing anyone. > > So if we are doing zh_TW instead of a direct simplified and > > traditional Chinese conversion, I don't think we can handle this > > properly without the help of Taiwanese friends. > > For what it's worth, I am from Taiwan and a native zh_TW speaker. > That is actually what motivated this patch: much of the current text > reads like converted zh_CN rather than natural Taiwanese Mandarin, So, back to my confusion again, and quote myself: How exactly we define the position of Traditional Chinese or zh_TW? 1. Simple conversion between simplified and traditional Chinese characters 2. Taiwanese localized traditional Chinese This issue needs to be confirmed by the senior maintenance personnel. (I will review the archives to confirm. If there is already a clear definition, please forgive me.) > and 8.Conclusion was simply where I started. Within my ability as a > newcomer, I would be happy to help review zh_TW patches or keep > improving the process/ documents, if that is useful to the discussion > you are planning to start. If we are conducting the localization of the traditional Chinese version for Taiwan, then it would be a good idea to start by continuing identifying these terminology issues now. However, for such similar terminology issues, using a series of patches in bulk is better than sending out one word correction at a time, like previous similar single patches. > This is also my first kernel patch, so naturally I would be glad to > see it applied. That said, I fully respect whatever direction you and > the docs maintainers decide is best for zh_TW as a whole, and I am > happy to rebase or adjust it if the discussion lands somewhere that > requires changes. Congrats! You have made your first step. btw, I have no say in any decision, i.e. my proposed direction has no effect at all. I respect maintainers' decision. At the same time, I feel ashamed that I haven't made any contribution yet. > > I can help review patches in traditional Chinese. With the help of > > LLM, it is fine for me to handle local terminologies in zh_TW. > > Thank you for offering to help with review, and thanks again for your > comments on v1. > > Thanks, > Chen-Yu Yes, thank you very much, Dongliang! But it seems that finding a more reasonable workflow is the best way to solve the problem. This would also relieve the burden on our reviewers. The current situation might not be too bad, but if it keeps going like this, it could be a problem.