Module talk:Lang-zh

This module falls within the scope of WikiProject Writing systems, a WikiProject interested in improving the encyclopaedic coverage and content of articles relating to writing systems on Wikipedia. If you would like to help out, you are welcome to drop by the project page and/or leave a query at the project’s talk page.Writing systemsWikipedia:WikiProject Writing systemsTemplate:WikiProject Writing systemsWriting system

China

This module is within the scope of WikiProject China, a collaborative effort to improve the coverage of China related articles on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ChinaWikipedia:WikiProject ChinaTemplate:WikiProject ChinaChina-related

Taiwan

This module is within the scope of WikiProject Taiwan, a collaborative effort to improve the coverage of Taiwan on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.TaiwanWikipedia:WikiProject TaiwanTemplate:WikiProject TaiwanTaiwan

Hong Kong

This module is within the scope of WikiProject Hong Kong, a project to coordinate efforts in improving all Hong Kong-related articles. If you would like to help improve this and other Hong Kong-related articles, you are invited to join this project.Hong KongWikipedia:WikiProject Hong KongTemplate:WikiProject Hong KongHong Kong

Hong Kong To-do:

Attention needed (60)

...needing expert attention (4) • ...without infoboxes (29)

Collaboration needed

Recommend topic

Improvement needed

GA-Class articles (60) • B-Class articles (308)

Cleanup needed

C-Class articles (1,105)

Image needed (348)

Destub needed

Start-Class articles (5,615) • Stub-Class articles (6,677)

Deorphan needed

...orphans

Page creation needed

Requested articles

Miscellaneous tasks

...maintain popularity • ...assess the un-Class (361) • ...assess the un-Importance (1,384)

Macau

This module is within the scope of WikiProject Macau, an attempt to better organize and improve articles related to Macau.MacauWikipedia:WikiProject MacauTemplate:WikiProject MacauMacau

Singapore

This module is within the scope of WikiProject Singapore, a collaborative effort to improve the coverage of articles related to Singapore on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.SingaporeWikipedia:WikiProject SingaporeTemplate:WikiProject SingaporeSingapore

Malaysia

This module is within the scope of WikiProject Malaysia, a collaborative effort to improve the coverage of Malaysia and Malaysia-related topics on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.MalaysiaWikipedia:WikiProject MalaysiaTemplate:WikiProject MalaysiaMalaysia

To help centralize discussions and keep related topics together, Template talk:Lang-zh and Template talk:Lang-zh/doc redirect here.

Archives

1, 2, 3, 4, 5

This page has archives. Sections older than 180 days may be automatically archived by when more than 4 sections are present.

Template-protected edit request on 5 February 2024

This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

This may be politically inclined, but I am highly unsure if Tongyong Pinyin should be our generic zh-Latn, as the mainland Pinyin wins by a very large margin in users.

I propose the following changes:

--- Module:Lang-zh
+++ Module:Lang-zh
@@ -54,8 +54,8 @@ local ISOlang = {
 	["c"] = "zh",
 	["t"] = "zh-Hant",
 	["s"] = "zh-Hans",
-	["p"] = "zh-Latn-pinyin",
-	["tp"] = "zh-Latn",
+	["p"] = "zh-Latn",
+	["tp"] = "zh-Latn-tongyong",
 	["w"] = "zh-Latn-wadegile",
 	["j"] = "yue-Latn-jyutping",
 	["cy"] = "yue-Latn",

Alternatively, if Pinyin is not a suitable generic zh-Latn, we should still add variant tags for Tongyong Pinyin:

--- Module:Lang-zh
+++ Module:Lang-zh
@@ -55,7 +55,7 @@ local ISOlang = {
 	["t"] = "zh-Hant",
 	["s"] = "zh-Hans",
	["p"] = "zh-Latn-pinyin",
-	["tp"] = "zh-Latn",
+	["tp"] = "zh-Latn-tongyong",
 	["w"] = "zh-Latn-wadegile",
 	["j"] = "yue-Latn-jyutping",
 	["cy"] = "yue-Latn",

NasssaNser_talk 11:01, 5 February 2024 (UTC)[reply]

This seems sensible to me – hanyu pinyin is more widely used than tongyong pinyin, and indeed MOS:PINYIN mentions that hanyu pinyin is the default romanization we use. What would the effect of this change be from the reader's perspective? —Mx. Granger (talk · contribs) 15:30, 10 February 2024 (UTC)[reply]

Like the rest of the language metadata, it adds specificity for screenreaders, as well as other possible presentations of articles. Remsense诉 23:21, 10 February 2024 (UTC)[reply]

Agree– I double-checked, and IANA added Tongyong as a valid language subtag variant in 2020. Remsense诉 23:20, 10 February 2024 (UTC)[reply]

Done * Pppery * _{it has begun...} 04:53, 11 February 2024 (UTC)[reply]

Template-protected edit request on 5 April 2024

This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

I would like to enable the option "first=poj" analogously to "first=j". The "first=j" option allows Cantonese romanisations to be given before Mandarin romanisations, in articles where Cantonese is more relevant. The proposed "first=poj" option would allow Hokkien romanisation (POJ) to be given first, in articles where Hokkien more relevant, e.g. for Bukit Ho Swee, Hong-Gah Museum, Tamsui District.

I believe this could be achieved by adding the following:

From line 114, after:

	local j1 = false -- whether Cantonese Romanisations go first

insert:

	local poj1 = false -- whether Hokkien Romanisations go first

From line 121, after:

			if (testChar == "j") then
				j1 = true
			 end

insert:

			if (testChar == "poj") then
				poj1 = true
			end

(The variable is named "testChar" but it is defined by the regular expression "%a+", which will match not only a single character but also longer strings.)

(On a separate note, there seems to be a superfluous space before "end" on lines 120 and 123.)

From line 137, after:

	if (j1) then
		orderlist[4] = "j"
		orderlist[5] = "cy"
		orderlist[6] = "sl"
		orderlist[7] = "p"
		orderlist[8] = "tp"
		orderlist[9] = "w"
	end

insert:

	if (poj1) then
		orderlist[4] = "poj"
		orderlist[5] = "p"
		orderlist[6] = "tp"
		orderlist[7] = "w"
		orderlist[8] = "j"
		orderlist[9] = "cy"
		orderlist[10] = "sl"
	end

This puts POJ before the Mandarin and Cantonese romanisations. Freelance Intellectual (talk) 08:49, 5 April 2024 (UTC)[reply]

Done * Pppery * _{it has begun...} 02:53, 15 April 2024 (UTC)[reply]

Double-quotes around glosses

Is there a reason we use double-quotes rather than single-quotes to show the output of |tr=? MOS:SIMPLEGLOSS suggests we should prefer singles. — OwenBlacker (he/him; Talk) 17:37, 18 June 2024 (UTC)[reply]

Because |l= is used for literal translations & glosses, and |tr= is (much more rarely) used for non-literal translations. Remsense诉 17:39, 18 June 2024 (UTC)[reply]

Aha, that makes sense. So I have probably been misusing |tr= when I should have been using |l=. Thank you! — OwenBlacker (he/him; Talk) 18:03, 18 June 2024 (UTC)[reply]

Commas within literal glosses

What should we do if there needs to be a comma within a literal translation? I noticed this on Yi Jian Mei (song), where the quotes should be placed around the whole comma-separated phrase, not individually around each side of the comma. pacificboy (talk) 03:56, 11 July 2024 (UTC)[reply]

My assumption when adding this feature was that if one needed to add a comma, it should probably be treated as a proper translation, not a gloss. It turns out I never use this formatting, so I could very plausibly disable it. Remsense诉 05:49, 11 July 2024 (UTC)[reply]