Module talk:Lang-zh

Edit request 20 December 2025

Minor change, but a comment refers to Tongyong Pinyin as "Tongyu Pinyin". This should be changed, for clarity for readers of the module.

Diff:

Tongyu Pinyin
+
Tongyong Pinyin

Ookap (talk) 20:01, 20 December 2025 (UTC)[reply]

 Completed. P.I. Ellsworth , ed. – welcome! – 10:27, 22 December 2025 (UTC)[reply]

Hi all! Could we please add Yale romanization of Mandarin to the template? Given that this is the English-language wikipedia, and the set of spelling/pronunciation rules used by Yale romanization of Mandarin is the closest to English's own spelling/pronunciation rules, it would be helpful if Yale romanization of Mandarin could be added to the template. In many cases, this would be helpful for native English speakers to pronounce Chinese words even if they haven't learnt any system of romaization of Mandarin before, as the system of Yale romanization of Mandarin was designed to be intuitive for English speakers. Many thanks! – 星球统领 (talk) 23:36, 11 February 2026 (UTC)[reply]

@星球统领: The current consensus is that pinyin is the default romanisation of Mandarin, and other systems are only to be used in special cases; see MOS:PINYIN. Freelance Intellectual (talk) 15:35, 12 February 2026 (UTC)[reply]
It isn't this template's objective to require any particular transliteration - that is left to the MOS:PINYIN to decide. The template was designed to support common transliterations that may be required in an article, but it is not exhaustive. For less commonly used transliterations, alternative markup methods exist, such as Template:Transliteration and Template:Langx. Rincewind42 (talk) 13:14, 13 February 2026 (UTC)[reply]

This is a request to add Pe̍h-ūe-jī (Teochew Church Romanisation) to the template. I have recently adding a lot of romanisations for people on singapore related articles and many have teochew names so it is quite frustrating to keep having to type " ; Pe̍h-ūe-jī: " for every single case of teochew usage. Warpswitch (talk) 21:51, 28 March 2026 (UTC)[reply]

Requested move 7 May 2026

– To make it consistent with other East Asian script templates, like {{Korean}} and {{Nihongo}}. Other previous templates like {{Lang-xx}} were largely replaced with {{Langx}}. Absolutiva 08:57, 7 May 2026 (UTC) — Relisting. Jeffrey34555 (talk) 04:17, 14 May 2026 (UTC)— Relisting. Primefac (talk) 17:36, 22 May 2026 (UTC) — Relisting. ⹃Maltazarian parleyinvestigate 12:14, 29 May 2026 (UTC)[reply]

Support per nom. Wasting time is still my passion (talk) 16:38, 17 May 2026 (UTC)[reply]
information Administrator note I have re-opened this discussion (closed without further commentary in Special:Diff/1355278435) as an uninvolved/individual admin action. This is for two main reasons: first, {{chinese}} is transcluded on almost 4k pages. Second (and as a result of the first), the discussion was started by a (now-)blocked sock and only commented on by a single other individual. Third, the final target template name in question is a redirect and should have been dealt with at WP:RFD before this RM was opened, but I probably will do so just for the sake of formality while this discussion is relisted again. Primefac (talk) 17:36, 22 May 2026 (UTC)[reply]
Note: WikiProject China, WikiProject Malaysia, WikiProject Taiwan, WikiProject Macau, WikiProject Hong Kong, WikiProject Singapore, and WikiProject Writing systems have been notified of this discussion. ASUKITE 17:56, 22 May 2026 (UTC)[reply]
Thank you for relisting this, Primefac. I hadn't seen this RM, as no Wikiprojects had been notified. The move makes some sense, since new editors will probably find the template more easily. Replacing it would be a pain, but it seems manageable. So, I guess I'm okay with it? But I'm generally not fussed either way. Toadspike [Talk] 21:54, 22 May 2026 (UTC)[reply]
Weak support What Toadspike said — now that the {{lang-xx}} templates have been superseded by {{langx}}, this name is less important. I would prefer that {{Korean}} and {{Nihongo}} were moved to {{lang-ko}} and {{lang-ja}} — especially the latter, as Nihongo fails ENGLISHTITLE — but I accept that plain English names might be better than expecting users to know ISO 639 codes. I would support this more strongly if we were also moving Template:NihongoTemplate:JapaneseTemplate:Japanese, Module:NihongoModule:Japanese, and bypassing the redirect to Template:Japanese script needed for existing {{Japanese}} calls. But I don't feel strongly enough to make and defend the case for doing so. — OwenBlacker (he/him; Talk) 06:25, 25 May 2026 (UTC)[reply]
I would agree with the Nihongo to Japanese moves. Those are out of the scope of this RM, but if anyone feels like proposing them, be my guest. Toadspike [Talk] 09:11, 25 May 2026 (UTC)[reply]
Support moving for consistency reasons, a Nihongo to Japanese move would also have my support. Yeeno (talk) 04:49, 27 May 2026 (UTC)[reply]
Oppose. {{lang-zh}} follows the same naming convention as the other excluded templates in Wikipedia:Templates for discussion/Log/2024 September 27/lang-?? templates, and {{Infobox Chinese}} follows the naming convention of, e.g., {{Infobox Japanese}}. For consistency, I think {{Korean}} and {{Nihongo}} should be moved to {{lang-ko}} and {{lang-ja}}, respectively. Snowman304|talk 01:11, 28 May 2026 (UTC)[reply]
I would certainly support this more strongly — OwenBlacker (he/him; Talk) 07:50, 28 May 2026 (UTC)[reply]

Wade–Giles superscripts

Now that Wikipedia:Manual of Style/Superscripts and subscripts is a guideline, it's clear that we should use Unicode superscripts for WG tones. Dingolover6969 (talk) 15:15, 5 June 2026 (UTC)[reply]

Content Disclaimer

Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.

  1. The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
  2. There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
  3. It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
  4. Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
  5. Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.