From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-179.mta1.migadu.com (out-179.mta1.migadu.com [95.215.58.179]) (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 040ED30EF77 for ; Sun, 12 Jul 2026 07:24:16 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.179 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783841059; cv=none; b=jq/j+o+Job+cpKFea1NVG7eCB020avUZzfd3bC4YPKMeHQfN0Qo7jFFap0q/h2F6aGt9xzFp1w+A2yzCcKkTPSO8sMyB7DBb9GOinRLADwZpAKuRppaw/5HM59UC+FG7BXPlHD87RTJyfjMjCVJMwn4vC+tBRyZDJ7IxHbEWYqU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783841059; c=relaxed/simple; bh=FmGfWVl4SPiZQHbm3g0iaQU+LjNa91xTan8Si2TBpjI=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=joIabG1ZWhJc3aZo8nrLgsyZ7S7C7m4GQkYrZsHH1LGJvgY5hFvM3AT7S6I880xngW1Zqp/oLZcu6qpLijVxZzqxMM8SQXlFCU62hF72eydZeE538K9rhwYwxBDZOwa8TTMLd3JASxxDUZa3fOONth+yakO66LWdtFHzZYtNX38= 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=Z6Fkdk0l; arc=none smtp.client-ip=95.215.58.179 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="Z6Fkdk0l" Date: Sun, 12 Jul 2026 15:23:51 +0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wyuan.org; s=key1; t=1783841055; 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=uT0GtxNyEflTuwT/zqAcYMhMTQmP5u1Qq80F4H/LMt0=; b=Z6Fkdk0lp64PNSiFy9ecFnfhsA04e30mnIWzbYaezACOOzFoBRNTHRIIRfNW/gsJo+s5pt btQl1Da/accb1bjF8Z4+x6rMMl8BDJu2ZsVRSgVXdZIPoRvg2w9996x5UyRULluqxMRV7E m7eZtiu8kHA5VQNOkMlvMKMrYTaSPRsBlrwTZahkMf2u+CCEWCSxI6ZWSfQHzluQ+lmS1o 1DWPOypvaLveRM9HPOjUECgbbGQdA6h4s+2ziaH3aaoGt9udxcUVe4xH/eVNR6xky7K4DO 4TTHA7TInyBs7+AjFdRfiywGYMqKiTW2GzFTXN7v0AiNQV63iGDxtkxX4B6WvQ== X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Weijie Yuan To: Alex Shi Cc: =?utf-8?B?6JGJ5a645L2R?= , 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> <40155119-b6c1-40cc-bbf2-5d1bbe5743e8@gmail.com> 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: <40155119-b6c1-40cc-bbf2-5d1bbe5743e8@gmail.com> X-Migadu-Flow: FLOW_OUT On Sun, Jul 12, 2026 at 12:33:36PM +0800, Alex Shi wrote: > On 2026/7/12 01:21, Weijie Yuan wrote: > > > 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.) > > Hi Weijie, > > Regarding this issue, we also have Hong Kong and Macau Traditional > Chinese. While they are mutually intelligible with Taiwanese Chinese, > there are slight differences. If a Taiwan-specific Traditional Chinese > translation is required, does this imply that we would also need other > corresponding localized translations? This is similar to English-the > English used in the UK, the US, Australia, and so on all differ > slightly, yet the kernel documentation does not maintain separate > versions for different countries. Hi Alex, Agreed, so I can understand that your point is that Traditional Chinese (Taiwan) actually doesn't have much practical use? > Furthermore, aside from a few differences in computing terminology, > there are no significant differences between Taiwanese Chinese and > Mainland Chinese that would lead to misunderstandings. Agreed. > In fact, many of the current Simplified Chinese translations were > contributed by people from Taiwan, like Haowen and others. Sorry, but I guess he is very likely not from Taiwan. 1. Based on the recent several patches, his initial translation was merely a simple conversion between simplified and traditional Chinese characters, without taking into account the local language expressions specific to Taiwan. If he were from Taiwan, many obvious linguistic habits would surely have been noticed, such as "软件" vs. "軟體". 2. His previous email domain shows he is studying in the mainland. 3. His personal blog is written in simplified chinese. Of course, I have no intention of intruding on others' privacy. I just merely made a brief observation. > 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. Absolutely agreed. These minor issues in expression habits, of course, will not have much impact on reading. 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. Thanks, Weijie