![]() | This module does not require a rating on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
![]() | To help centralise discussions and keep related topics together, Template talk:Lang-zh and Template talk:Lang-zh/doc redirect here. |
This page has archives. Sections older than 180 days may be automatically archived by Lowercase sigmabot III when more than 4 sections are present. |
![]() | 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)
![]() | 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)
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)
|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)
|tr=
when I should have been using |l=
. Thank you! —
OwenBlacker (he/him;
Talk)
18:03, 18 June 2024 (UTC)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)
![]() | This module does not require a rating on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
![]() | To help centralise discussions and keep related topics together, Template talk:Lang-zh and Template talk:Lang-zh/doc redirect here. |
This page has archives. Sections older than 180 days may be automatically archived by Lowercase sigmabot III when more than 4 sections are present. |
![]() | 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)
![]() | 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)
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)
|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)
|tr=
when I should have been using |l=
. Thank you! —
OwenBlacker (he/him;
Talk)
18:03, 18 June 2024 (UTC)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)