View source for Module talk:Lang-zh/Archive 5

{{talk archive navigation}}

== Cantonese Pinyin? ==

Hello, how does one indicate use of [[Cantonese Pinyin]] romanization? For example, in [[March Tian Boedihardjo]] (I assume this is Cantonese Pinyin). <b>[[User:Audacity|<span style="color:black">Λυδ</span>]][[User talk:Audacity|<span style="color:blue">α</span>]][[User:Audacity|<span style="color:black">cιτγ</span>]]</b> 06:11, 18 July 2018 (UTC)
: I can’t find the Romanisation in any of the sources (though many are dead links). It seems unlikely it would be used, as in e.g. English media his Indonesian name is fine, and that seems to be what’s used. In Chinese media his Chinese name is all that’s needed.--<small>[[User:JohnBlackburne|JohnBlackburne]]</small><sup>[[User_talk:JohnBlackburne|words]]</sup><sub style="margin-left:-2.0ex;">[[Special:Contributions/JohnBlackburne|deeds]]</sub> 07:51, 18 July 2018 (UTC)
: I’ve removed it. Seems it was changed from pinyin to this other Romanisation in [https://en.wikipedia.org/w/index.php?title=March_Tian_Boedihardjo&diff=760471639&oldid=759630200 this change] several months ago, with no rationale by an IP editor. Neither it nor the pinyin was sourced that I can see, and as there’s no evidence he uses anything other than his Indonesian name there’s no need for it.--<small>[[User:JohnBlackburne|JohnBlackburne]]</small><sup>[[User_talk:JohnBlackburne|words]]</sup><sub style="margin-left:-2.0ex;">[[Special:Contributions/JohnBlackburne|deeds]]</sub> 11:05, 18 July 2018 (UTC)

== CJKV ==

Like the various templates that have been merged into {{tl|lang-zh}}, {{tl|CJKV}} is a bit of a sprawling mess of template syntax right now. This module is currently focused on Chinese, but I wonder if we could generalize it to cover Japanese, Korean, and Vietnamese romanizations of Chinese characters as well, since there's already significant overlap between {{tl|CJKV}} and this module. &ndash;&nbsp;[[User:Mxn|Minh <span style="font-variant: small-caps;">Nguyễn</span>]]&nbsp;<sup>[[User talk:Mxn|<span style="display: inline-block;">&#x1f4ac;</span>]]</sup> 20:54, 18 July 2018 (UTC)

== How to display Traditional first, then Simplified, then Cantonese, then Mandarin? ==

At [[Verax (film)]] I want to display Traditional first, then Simplified, then Cantonese, then Mandarin. How may I do this?

Thanks,
[[User:WhisperToMe|WhisperToMe]] ([[User talk:WhisperToMe|talk]]) 22:09, 6 August 2018 (UTC)

* {{U|WhisperToMe}}, you can use the parameter {{para|first}} with {{mono|t,j}}. See [[Template:Lang-zh#Ordering]].--<small>[[User:JohnBlackburne|JohnBlackburne]]</small><sup>[[User_talk:JohnBlackburne|words]]</sup><sub style="margin-left:-2.0ex;">[[Special:Contributions/JohnBlackburne|deeds]]</sub> 05:08, 14 August 2018 (UTC)

== Needs a parameter to stop changing labels to just "Chinese" if either |t= or |s= is missing ==

Many times we'll want to be specific. It should not be impossible to get "[[Traditional Chinese]]:" from {{tlx|zh|t{{=}}趙豐邦}}. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 03:00, 25 July 2018 (UTC)
: {{U|SMcCandlish}} I disagree. If a sentence article contains just one sort of Chinese, whether simplified or traditional (and all Chinese is one or the other, perhaps both) then by far the most sensible article to link to is [[Chinese language]]. The vast majority of readers won’t notice or care which of traditional or simplified is used.
: There are exceptions. If both simplified and traditional Chinese text is included then it makes sense to name and link to both articles at least once, and the template does this automatically. If a particular point is being made about it being traditional Chinese then the link should be incorporated into the text that is making that point.
: But in normal usage it makes sense to work as it does. It’s worked like that for a very long time, from before I rewrote it to use Lua. If you really need to do it another way on a case by case basis then it’s probably best to do it manually, using e.g. {{tl|lang}} which does not add any links.--<small>[[User:JohnBlackburne|JohnBlackburne]]</small><sup>[[User_talk:JohnBlackburne|words]]</sup><sub style="margin-left:-2.0ex;">[[Special:Contributions/JohnBlackburne|deeds]]</sub> 05:24, 14 August 2018 (UTC)
: re-ping {{U|SMcCandlish}} as I messed it up first time.--<small>[[User:JohnBlackburne|JohnBlackburne]]</small><sup>[[User_talk:JohnBlackburne|words]]</sup><sub style="margin-left:-2.0ex;">[[Special:Contributions/JohnBlackburne|deeds]]</sub> 05:24, 14 August 2018 (UTC)
::Hmm. "I disagree" followed by "There are exceptions" is contradictory.  My statement that "it should not be impossible" to be specific, and your statement that there are exceptions to your [[Chinese language]] generality link idea, and that we should sometimes be specific, are directly equivalent statements.  I'll approach this from a different angle: The only reason I have not simply fixed it is that I suck at Lua.  If this were a regular template, I would have resolved this in a few minutes of editing in the template code, and I really don't think anyone would be objecting. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 16:43, 8 November 2018 (UTC)

== Template Data broken ==

I use the visual editor a lot and I realized in the past week the template data is broken. Has this been a problem for anyone else? --[[User:Daviddwd|Daviddwd]] ([[User talk:Daviddwd|talk]]) 19:28, 19 January 2019 (UTC)

== Xiao'erjing ==

Having just noticed [[Xiao'erjing]] text in the lead to [[Taklamakan Desert]], I wondered if it's worthwhile to add another argument to this module to allow something like {{para|x|تَاكْلامَاقًا شَاموْ}}, which would then add {{xt|[[Xiao'erjing]]: {{lang|zh-Arab|تَاكْلامَاقًا شَاموْ}} }} (so the equivalent of <code><nowiki>[[Xiao'erjing]]: {{lang|zh-Arab|تَاكْلامَاقًا شَاموْ}}</nowiki></code>) to the end of the output? — <span class="vcard"><span class="fn">[[User:OwenBlacker|OwenBlacker]]</span> <small>([[User talk:OwenBlacker|talk]]; please &#123;&#123;[[Template:ping|ping]]&#125;&#125; me in replies)</small></span> 18:23, 15 August 2018 (UTC)
: I'm in favor of this.  --[[User:Daviddwd|Daviddwd]] ([[User talk:Daviddwd|talk]]) 19:57, 21 January 2019 (UTC)

== Requested change ==

This template displays double quotes with the parameter <code>l=</code>.  Could this please be changed to single quotes per [[MOS:SINGLE]] and other language templates (e.g. {{tlx|lang-ar}}).  [[User:Shhhnotsoloud|Shhhnotsoloud]] ([[User talk:Shhhnotsoloud|talk]]) 20:44, 16 December 2018 (UTC)

: I support this. --[[User:Daviddwd|Daviddwd]] ([[User talk:Daviddwd|talk]]) 19:59, 21 January 2019 (UTC)

== [[MOS:SINGLE]] ==
{{Resolved}}
The literal gloss ({{para|l}} parameter) needs to be bracketed in single not double quotations, per [[MOS:SINGLE]]. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 22:52, 20 February 2019 (UTC)
::See [[#Requested change]] above. Just need someone competent to do it! [[User:Shhhnotsoloud|Shhhnotsoloud]] ([[User talk:Shhhnotsoloud|talk]]) 07:52, 21 February 2019 (UTC)
Suggestion executed. On a more general note, the fact that this request took three months to get executed is exactly why I think there is far too much use of lua and go around TfDing modules. [[User:Pppery|&#123;&#123;3x&#124;p&#125;&#125;ery]] ([[User talk:Pppery|talk]]) 05:05, 22 February 2019 (UTC)
:{{ping|Pppery}} I agree (though this particular request dates to this month; I think you were looking at a different tab). But discussing it here won't help, since this is a backwater. :-)  I've raise a larger thread at TfD talk, as an RfC: [[Wikipedia talk:Templates for discussion#RfC: Proposal to make TfD more RM-like, as a clearinghouse of template discussions]].<br /><span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 05:14, 27 February 2019 (UTC)</p>
:: {{ping|SMcCandlish}} It was originally proposed at [[#Requested change]] in December. (I was exaggerating a little bit, it was only two months) [[User:Pppery|&#123;&#123;3x&#124;p&#125;&#125;ery]] ([[User talk:Pppery|talk]])  05:21, 27 February 2019 (UTC)
:::Noted! <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 05:41, 27 February 2019 (UTC)
:Also pinging {{U|Shhhnotsoloud}}. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 05:15, 27 February 2019 (UTC)
{{ping|Pppery}} You changed the opening quote but not the closing quote. [[User:Toohool|Toohool]] ([[User talk:Toohool|talk]]) 06:16, 27 February 2019 (UTC)
:I noticed that and went to fix it but the module is cascade protected at the moment. [[User:Johnuniq|Johnuniq]] ([[User talk:Johnuniq|talk]]) 06:21, 27 February 2019 (UTC)
Wouldn't an edit request template have resolved this more quickly? As you say, this is a backwater, but the edit request lists are watched by many competent editors. – [[User:Jonesey95|Jonesey95]] ([[User talk:Jonesey95|talk]]) 07:22, 27 February 2019 (UTC)
: {{ping|Jonesey95}} [[File:Red information icon with gradient background.svg|20px|link=|alt=]] '''Not done:''' please make your requested changes to the module's sandbox first; see [[Wikipedia:Template sandbox and test cases|WP:TESTCASES]].<!-- Template:ETp --> (seriously, an edit request template could easily have attracted someone responding with that boilerplate message) [[User:Pppery|&#123;&#123;3x&#124;p&#125;&#125;ery]] ([[User talk:Pppery|talk]])  20:32, 27 February 2019 (UTC)
{{edit fully-protected|answered=yes}}
Please edit this module to change line 185 from the first of the following lines to the second, per discussion just above.
<pre>
val = "'" .. val .. '"'
val = "'" .. val .. "'"
</pre>
This puts an apostrophe on both sides of val. [[User:Johnuniq|Johnuniq]] ([[User talk:Johnuniq|talk]]) 08:47, 27 February 2019 (UTC)
:[[File:Yes check.svg|20px|link=|alt=]] '''Done'''<!-- Template:EP --> —[[User:TheDJ|Th<span style="color: green">e</span>DJ]] ([[User talk:TheDJ|talk]] • [[Special:Contributions/TheDJ|contribs]]) 09:31, 27 February 2019 (UTC)

== A problem with defaulting to simplified ==

The parameter c renders characters in the simplified typeface. This has resulted in inconsistencies for Taiwan, Hong Kong and Macau names. I propose that the parameter be removed or use be discouraged. [[User:Ythlev|Ythlev]] ([[User talk:Ythlev|talk]]) 14:31, 19 June 2019 (UTC)

: Parameter <code>c=</code> doesn't render anything, it only marks text as Chinese ([https://www.w3schools.com/tags/ref_language_codes.asp <code>zh</code>]). Which [[Locale (computer software)|locale]] incl. typeface is selected for that purpose depends on your browser/system settings. <small>[[Wikipedia:WikiLove|Love]]</small>&nbsp;—[[:commons:User:LiliCharlie|LiliCharlie]]&nbsp;<small>([[User talk:LiliCharlie|talk]])</small> 16:56, 19 June 2019 (UTC)

== Minor romanization formatting points ==
I've noticed when Peh-oe-ji or jyutping is provided, it uses fullwidth characters. Furthermore, {{para|j}} does not superscript the numbers included automatically as does Wade-Giles ({{para|w}}). Could we fix this? --[[User:Daviddwd|Daviddwd]] ([[User talk:Daviddwd|talk]]) 19:59, 21 January 2019 (UTC)

{{edit fully-protected|answered=yes}}
I have the same problem. The troublesome code seems to be this:
<pre>
["cy"] = "yue",
["sl"] = "yue",
["poj"] = "nan",
</pre>
which could be simply changed to
<pre>
["cy"] = "yue-Latn",
["sl"] = "yue-Latn",
["poj"] = "nan-Latn",
</pre> [[User:Wikifresc|Wikifresc]] ([[User talk:Wikifresc|talk]]) 23:47, 8 March 2019 (UTC)
:Putting in an edit request for the above edit to be carried out, though it won't fix the issue with {{para|j}}. Romanisations should obviously be tagged as Latin script and rendered appropriately. —[[User:Nizolan|Nizolan]] <sup>([[User talk:Nizolan|talk]])</sup> 19:21, 12 July 2019 (UTC)
:{{done}} — [[User:Xaosflux|<span style="color:#FF9933; font-weight:bold; font-family:monotype;">xaosflux</span>]] <sup>[[User talk:Xaosflux|<span style="color:#009933;">Talk</span>]]</sup> 13:38, 23 July 2019 (UTC)

===Jyutping===
{{edit fully-protected|answered=yes}}
In addition to Wikifresc's proposed edit, and for the same reason, please edit <code>"yue-jyutping"</code> on line 57 to <code>"yue-Latn-jyutping"</code>. This has also been added to the sandbox and fixes the fullwidth character issue Daviddwd identified (see [[:Template:Lang-zh/testcases]]). —[[User:Nizolan|Nizolan]] <sup>([[User talk:Nizolan|talk]])</sup> 20:37, 12 July 2019 (UTC)
:{{done}} — [[User:Xaosflux|<span style="color:#FF9933; font-weight:bold; font-family:monotype;">xaosflux</span>]] <sup>[[User talk:Xaosflux|<span style="color:#009933;">Talk</span>]]</sup> 13:38, 23 July 2019 (UTC)
::{{re|Xaosflux}} Might be missing something but it doesn't look like you made any edits at [[:Module:Zh]]—guessing this is a mistake. Reopening the requests for now. —[[User:Nizolan|Nizolan]] <sup>([[User talk:Nizolan|talk]] · [[Special:Contributions/Nizolan|c.]])</sup> 19:36, 23 July 2019 (UTC)
:::{{Re|Nizolan}} very very odd, my commit must have failed, I even had my edit summary saved in my browser's autocomplete.  Check now? — [[User:Xaosflux|<span style="color:#FF9933; font-weight:bold; font-family:monotype;">xaosflux</span>]] <sup>[[User talk:Xaosflux|<span style="color:#009933;">Talk</span>]]</sup> 20:23, 23 July 2019 (UTC)
::::{{re|Xaosflux}} Works great now, thanks. —[[User:Nizolan|Nizolan]] <sup>([[User talk:Nizolan|talk]] · [[Special:Contributions/Nizolan|c.]])</sup> 20:56, 23 July 2019 (UTC)

== Proposal to add Foochow Romanized (BUC) ==

Hello all. I am doing some work on the Matsu Islands and the Fuzhou area of Fujian Province, and I was wondering if we could add BUC to the module. Articles like [[Dongyin, Lienchiang]] have BUC written on the page with no blue link to the Foochow Romanized page, and I think it looks unprofessional (as well as uninformative). Thanks for any help or suggestions. [[User:Geographyinitiative|Geographyinitiative]] ([[User talk:Geographyinitiative|talk]]) 06:30, 31 August 2019 (UTC)
:(Also, BUC is the form used on the Mìng-dĕ̤ng-ngṳ̄ Wikipedia ( https://cdo.wikipedia.org )- why exclude them?) [[User:Geographyinitiative|Geographyinitiative]] ([[User talk:Geographyinitiative|talk]]) 06:31, 31 August 2019 (UTC)
== Requested move 29 October 2019 ==
<div class="boilerplate" style="background-color: #efe; margin: 0; padding: 0 10px 0 10px; border: 1px dotted #aaa;"><!-- Template:RM top -->
:''The following is a closed discussion of a [[Wikipedia:Requested moves|requested move]]. <span style="color:red">'''Please do not modify it.'''</span> Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a [[Wikipedia:move review|move review]] after discussing it on the closer's talk page. No further edits should be made to this discussion. ''

The result of the move request was: '''moved''' <small>([[Wikipedia:Requested moves/Closing instructions#Closure by a page mover|closed by non-admin page mover]])</small> [[User:DannyS712|DannyS712]] ([[User talk:DannyS712|talk]]) 06:28, 6 November 2019 (UTC)
----



[[:Module:Zh]] → {{no redirect|Module:Lang-zh}} – Match name with template [[User:Pppery|* Pppery *]] [[User talk:Pppery|<sub style="color:#800000">it has begun...</sub>]] 22:10, 29 October 2019 (UTC)
* '''Support''' per nom. --[[User:Gonnym|Gonnym]] ([[User talk:Gonnym|talk]]) 14:00, 30 October 2019 (UTC)
----
:''The above discussion is preserved as an archive of a [[Wikipedia:Requested moves|requested move]]. <b style="color:red">Please do not modify it.</b> Subsequent comments should be made in a new section on this [[Help:Using talk pages|talk page]] or in a [[Wikipedia:Move review|move review]]. No further edits should be made to this section.''<!-- Template:RM bottom --></div>

== Proposal for "first=poj" ==

The first sentence of [[Hong-Gah Museum]] and [[Tamsui]] would be made better with 'first=poj'. [[User:Geographyinitiative|Geographyinitiative]] ([[User talk:Geographyinitiative|talk]]) 10:49, 19 November 2019 (UTC)

== The romanization name "Cantonese Yale" is confusing ==

As someone who has some familiarity with Chinese Romanization systems, upon looking up "New Territories" I was confused by the phrase "Cantonese Yale", generated by the zh template. Upon examining the template definition, I find that "Cantonese Yale" is the phrase used to denote the Yale Romanization system. That phrase looks strange in English as it 
(1) inverts the usual English adjective-noun order
(2) omits the word "Romanization".

Searching the internet outside of Wikipedia, I find that occurrence of the phrase "Cantonese Yale" to be vanishingly rare.

I suggest that the text produced by the zh template in response to "cy" as a template parameter be changed from "Cantonese Yale:" to simply "Yale:" or maybe "Yale romanization:" 

I am not implementing this change myself at this time, but I request that someone familiar with the zh template please do so. [[User:Dratman|Dratman]] ([[User talk:Dratman|talk]]) 00:01, 3 February 2020 (UTC)

== Template-protected edit request on 24 July 2020 ==

{{edit template-protected|Module:Lang-zh|answered=yes}}
Line 186: please change <code>val = "'" .. val .. "'"</code> to <code><nowiki>val = "{{'}}" .. val .. "{{'}}"</nowiki></code>.

See {{section link|Project 523|Discovery of artemisinin and its derivatives}} as an example. In that section, placing <code><nowiki>''</nowiki></code> around the template would be unnecessarily italicize the entire template-generated text, instead of just the value in the <code>|l=</code> parameter. As is, the <code><nowiki>''</nowiki></code> in the template combine with the <code>'</code> from this module to bold the title, which is unexpected behavior. If we could escape that character here, that would solve that problem without changing the behavior of the template elsewhere. Thanks! [[User:Rotideypoc41352|Rotideypoc41352]] ([[User talk:Rotideypoc41352|talk]] '''·''' [[Special:Contribs/Rotideypoc41352|contribs]]) 22:48, 24 July 2020 (UTC)
:{{to|Rotideypoc41352}} [[File:Red information icon with gradient background.svg|20px|link=|alt=]] '''Not done:'''<!-- Template:ETp --> put that in the [[Module:Lang-zh/sandbox|sandbox]] and all it does is place <nowiki>{{'}}</nowiki> in the template, as in <nowiki>(Chinese: 《肘後備急方》; lit.: {{'}}</nowiki>''The Handbook of Prescriptions for Emergencies''<nowiki>{{'}})</nowiki>. Not sure how to fix this other than using only one apostrophe in the template, as in <nowiki>(Chinese: 《肘後備急方》; lit.: 'The Handbook of Prescriptions for Emergencies'</nowiki> as I have done at {{section link|Project 523|Discovery of artemisinin and its derivatives}}. I'll keep checking back here to see if you have come up with something else. The sandbox can be used in "preview" to see if it works. '''''[[User:Paine Ellsworth|<span style="font-size:92%;color:darkblue;font-family:Segoe Script">P.I.&nbsp;Ellsworth</span>]]'''''&nbsp;&nbsp;[[Editor|<span style="color:black">ed.</span>]]&nbsp;[[User talk:Paine Ellsworth|<sup>put'r&nbsp;there</sup>]]&nbsp;<small>00:14, 25 July 2020 (UTC)</small>
:{{to|Rotideypoc41352}} Looking at this more closely, we find that the "literal translation" parameter, {{para|l}}, is used in the example you gave as follows:
<pre>
l=The Handbook of Prescriptions for Emergencies
</pre>
:That is a lower case letter "l", for "literal", not the number "1", by the way. When the {{para|l}} parameter is used, this module automatically links to [[Literal translation|lit.]] (literal translation) and encloses the text in single quotation marks, as in:
::{{lang-zh|t=《肘後備急方》|l=The Handbook of Prescriptions for Emergencies}}
:For the most part, this is adequate to note the translation. As you have seen, problems arise when the translation is the title of a film or book, and it should be in italics. That is easily dealt with by adding a single quote mark (apostrophe) at the beginning and end of the text, as follows:
<pre>
{{lang-zh|t=《肘後備急方》|l='The Handbook of Prescriptions for Emergencies'}}
</pre>
:and results in:
::{{lang-zh|t=《肘後備急方》|l='The Handbook of Prescriptions for Emergencies'}}
:That is the only way I know of to deal with such titles without mucking up the works for other uses where italics are not called for. Hope this helps''!'' '''''[[User:Paine Ellsworth|<span style="font-size:92%;color:darkblue;font-family:Segoe Script">P.I.&nbsp;Ellsworth</span>]]'''''&nbsp;&nbsp;[[Editor|<span style="color:black">ed.</span>]]&nbsp;[[User talk:Paine Ellsworth|<sup>put'r&nbsp;there</sup>]]&nbsp;<small>06:14, 25 July 2020 (UTC)</small>
::It does! I was hoping for a less work-aroundy solution, but if that's how the cookie crumbles, that's how the cookie crumbles. Thanks again! [[User:Rotideypoc41352|Rotideypoc41352]] ([[User talk:Rotideypoc41352|talk]] '''·''' [[Special:Contribs/Rotideypoc41352|contribs]]) 07:51, 27 July 2020 (UTC)

== Question about rendering of depreciated zh-t and zh-trad ==

I realize that the other zh templates have been consolidated into lang-zh, but when zh is still used, it do not seem to render traditional Chinese characters properly. For example, if I want unicode U+4ECA, then <code>zh-t</code> (and <code>zh-trad</code>) give me {{zh-t|今|labels=no}}, but it should actually render as {{lang-zh|t=今|labels=no}} (as <code>lang-zh|t=</code> correctly does).
Similarly, <code>zh-t</code> incorrectly renders {{zh-t|次|labels=no}} and {{zh-t|骨|labels=no}}, whereas <code>lang-zh|t=</code> correctly renders {{lang-zh|t=次|labels=no}} and {{lang-zh|t=骨|labels=no}}.

This seems to be a result of [[Han unification]] (see [[Han_unification#Examples_of_language-dependent_glyphs|the examples]]), so I was wondering if this is intentional or known behavior. It would make more sense to me, at least for backwards-compatibility, for <code>zh-t</code> to render the same as <code>lang-zh|t=</code>, but it currently does not. [[User:ChromeGames923|ChromeGames923]] ([[User talk:ChromeGames923|talk]] · [[Special:Contributions/ChromeGames923|contribs]]) 19:15, 10 September 2020 (UTC)

== MOS compliance ==
{{block indent|em=1.6|{{small|Notified: [[WP:CHINA]]. — [[User:Goszei|Goszei]] ([[User_talk:Goszei|talk]])  19:00, 14 May 2020 (UTC)}}}}<!-- Template:Notified -->
{{block indent|em=1.6|1=<small>Notified: [[MOS:LEAD]]. — [[User:Goszei|Goszei]] ([[User_talk:Goszei|talk]])  03:04, 23 November 2020 (UTC)</small>}}<!-- Template:Notified -->
The Manual of Style section for foreign-language names ([[MOS:LEADALT]]) states:
:{{tq|{{em|Relevant}} foreign-language names, such as in an article on a person who does not themselves write their name in English, are encouraged. Separate languages should be divided by [[semicolon]]s, and [[romanization]]s of non-Latin scripts by [[comma]]s.}}
This seems to clearly prescribe changes to this template, which currently looks like this:
:{{Lang-zh | t=中國| s=中国| hp=Zhōngguó| tp=Jhongguó}}
At the least, the pinyin fields should be separated by a comma and not a semicolon, because they are romanizations and not separate languages. In cases like:
:{{Lang-zh |s = 最高人民法院 |p = Zuìgāo Rénmín Fǎyuàn }}
The MOS clearly prescribes a comma separator. Comments? — [[User:Goszei|Goszei]] ([[User_talk:Goszei|talk]])  04:39, 14 May 2020 (UTC)
:: I was actually kind of skeptical at first, but I see your point. I noticed this while looking at [[Gyirong Town]], which lists the name in both Mandarin and Nepali, rendered as ({{zh|c=吉隆镇|p=Jílóng zhèn}}; [[Nepali language|Nepali]]:केरुङ). That setup might be confusing for someone unfamiliar with what Chinese or what pinyin means. [[User:WhinyTheYounger|WhinyTheYounger]] ([[User talk:WhinyTheYounger|talk]]) 22:37, 21 May 2020 (UTC)

== Template-protected edit request on 30 March 2020 ==

{{edit template-protected|Module:Lang-zh|answered=yes}}
literal translations should be labeled "lit." not "literally" for brevity when that parameter is used. Or a ''translation'' parameter should be used like [[Template:Lang-ja]]

[[User:Mualphachi|Mualphachi]] ([[User talk:Mualphachi|talk]]) 17:18, 30 March 2020 (UTC)

*'''Support''', here for the same proposal. I think "<small>[[Literal translation|lit.]]</small>" is even better. (consistent with other {{tl|Lang-xx}}) -- [[User:Akira_CA|<span style="color:#DD0000;">'''Akira'''</span>]]😼[[User_talk:Akira_CA|<span style="color:#000080;">'''CA'''</span>]] 10:25, 8 April 2020 (UTC)
*:I've mocked it up, example is in [[Template:Lang-zh/testcases]]. {{ping|Mualphachi|Akira_CA}} if it looks good I'll implement. [[User:Primefac|Primefac]] ([[User talk:Primefac|talk]]) 16:31, 18 April 2020 (UTC)
*:{{ping|Mualphachi|Akira_CA}} your comments please? &mdash;&nbsp;Martin <small>([[User:MSGJ|MSGJ]]&nbsp;·&nbsp;[[User talk:MSGJ|talk]])</small> 07:28, 5 May 2020 (UTC)
:[[File:Yes check.svg|20px|link=|alt=]]&nbsp;'''Done'''<!-- Template:ETp --> No one has said anything about the change, and it's doing what was requested, so in the grand scheme of SILENCE and "why not" I've made the change - no opposition to rolling back if there are serious concerns or bugs. [[User:Primefac|Primefac]] ([[User talk:Primefac|talk]]) 14:07, 15 May 2020 (UTC)
::::::thanks, looks good [[User:Mualphachi|Mualphachi]] ([[User talk:Mualphachi|talk]]) 04:14, 18 May 2020 (UTC)
::{{ping|Primefac|Mualphachi|Akira CA}} I like the change, and would like to suggest two small tweaks (which are not a package, and could be implemented separately).
::
::* the colon in {{tq|lit.:}} could be removed, as it simply looks cleaner without, IMO. This would also match with the format of my next suggestion.
::
::* [[Template:Literal translation]] (renders as {{lit}}) could be used here, as the tooltip gives the necessary level of info, and the wikilink to [[literal translation]] seems like overkill to me. — [[User:Goszei|Goszei]] ([[User_talk:Goszei|talk]])  02:50, 23 November 2020 (UTC)
:::Addendum: I have found another option. Upon inspecting the other {{:lang-x}} templates (French, Spanish, German, etc.), I have found that they all use this format, which utilizes small tags: ({{langx|fr|Marine nationale|lit=National Navy}}). — [[User:Goszei|Goszei]] ([[User_talk:Goszei|talk]])  03:59, 23 November 2020 (UTC)
::::Just a quick note to say that I've seen this and it's on my list of things to get to. [[User:Primefac|Primefac]] ([[User talk:Primefac|talk]]) 12:22, 26 November 2020 (UTC)
:::::{{para|l}} now shows <small>[[literal translation|lit.]]</small> (small, w/o colon). [[User:Primefac|Primefac]] ([[User talk:Primefac|talk]]) 21:23, 3 December 2020 (UTC)

{{ping|Primefac}} Whatever you did to the module, it created error messages on pages using {{tl|Lang-zh}}. Red text stating 'Lua error in Module:Lang-zh at line 218: Tried to read nil global part.' appeared on an article I happened to look at. You can see this in the [[Template:Lang-zh/testcases|testcases]]. Cheers, [[User:Number 57|<span style="color: orange;">Number</span>]] [[User talk:Number 57|<span style="color: green;">5</span>]][[Special:Contributions/Number 57|<span style="color: blue;">7</span>]] 21:32, 3 December 2020 (UTC)
:Fixed, the second was for when there's no param, so it kind of makes sense that it would throw that error. In the back of my mind I wondered about that (at least it's an easy fix). [[User:Primefac|Primefac]] ([[User talk:Primefac|talk]]) 21:34, 3 December 2020 (UTC)

== Request to Add override default ordering option for POJ as the first in the ordering ==

Hi, I'd like to request if someone could please edit the code so as to add an option to also override the default ordering so as to put Hokkien POJ first before Pinyin and the others, just like how Cantonese Jyutping can already do that. I think maybe the order of 'poj, zhu, w, hp, tp' might do.--[[User:Mlgc1998|Mlgc1998]] ([[User talk:Mlgc1998|talk]]) 21:07, 7 December 2020 (UTC)
:Doesn't the template already allow custom ordering? [[User:Primefac|Primefac]] ([[User talk:Primefac|talk]]) 13:43, 8 December 2020 (UTC)
:: {{re|Primefac}} Hi apologies, I just saw this now lol. If you look at the code, it is only hardcoded to accept 2 inputs in the Ordering field, either "t" or "j" to put either Traditional Chinese first or Cantonese Romanizations first. In order to add the option to place POJ first, I suggest to add the code for the if statements to accept these as well, unless you would like to think up the code that accepts custom ordering based on input.

<syntaxhighlight lang="diff">

function p._Zh(args)
	local uselinks = not (args["links"] == "no") -- whether to add links
	local uselabels = not (args["labels"] == "no") -- whether to have labels
	local capfirst = args["scase"] ~= nil
 
	local t1 = false -- whether traditional Chinese characters go first
	local j1 = false -- whether Cantonese Romanisations go first
+	local poj1 = false -- whether Hokkien Romanisations go first
	local testChar
	if (args["first"]) then
	 	 for testChar in mw.ustring.gmatch(args["first"], "%a+") do
			if (testChar == "t") then
				t1 = true
			end
			if (testChar == "j") then
				j1 = true
			end
+			if (testChar == "poj") then
+				poj1 = true
+			end
		end
	end
	if (t1 == false) then
		local title = mw.title.getCurrentTitle()
		t1 = t1st[title.text] == true
	end

	-- based on setting/preference specify order
	local orderlist = {"c", "s", "t", "p", "tp", "w", "j", "cy", "sl", "poj", "zhu", "l"}
	if (t1) then
		orderlist[2] = "t"
		orderlist[3] = "s"
	end
	if (j1) then
		orderlist[4] = "j"
		orderlist[5] = "cy"
		orderlist[6] = "sl"
		orderlist[7] = "p"
		orderlist[8] = "tp"
		orderlist[9] = "w"
	end
+	if (poj1) then
+		orderlist[4] = "poj"
+		orderlist[5] = "zhu"
+		orderlist[6] = "w"
+		orderlist[7] = "p"
+		orderlist[8] = "tp"
+	end

</syntaxhighlight>

== add new translation parameter "tr" ==
{{Edit template-protected|Module:Lang-zh|answered=yes}}
could someone implement these small changes to add a [[Translation]] parameter? the concept of literal translation is limiting in use cases for translating texts...

<syntaxhighlight lang="diff">
diff --git a/lang-zh.lua b/lang-zh.lua
index 7a8791c..1fe24a5 100644
--- a/lang-zh.lua
+++ b/lang-zh.lua
@@ -29,6 +29,7 @@ local labels = {
 	["poj"] = "Pe̍h-ōe-jī",
 	["zhu"] = "Zhuyin Fuhao",
 	["l"] = "lit.",
+	["tr"] = "trans.",
 }
 
 -- article titles for wikilinks for each part
@@ -115,7 +116,7 @@ function p._Zh(args)
 	end
 
 	-- based on setting/preference specify order
-	local orderlist = {"c", "s", "t", "p", "tp", "w", "j", "cy", "sl", "poj", "zhu", "l"}
+	local orderlist = {"c", "s", "t", "p", "tp", "w", "j", "cy", "sl", "poj", "zhu", "l", "tr"}
 	if (t1) then
 		orderlist[2] = "t"
 		orderlist[3] = "s"
@@ -186,7 +187,7 @@ function p._Zh(args)
 				-- add span for language if needed
 				params = {["lang"] = ISOlang[part]}
 				val = mw.text.tag({name="span",attrs=params, content=val})
-			elseif (part == "l") then
+			elseif ((part == "l") or (part == "tr")) then
 				-- put literals in quotes
 				val = "'" .. val .. "'"
 			end
</syntaxhighlight>

<span style="color: #E12144">[[User talk:TRANSviada|<span style="color:#E12144">'''talk'''</span>]]'''&#64;'''[[User:TRANSviada|<span style="color:#E12144">'''TRANSviada'''</span>]]</span> 01:39, 27 February 2021 (UTC)
:{{ping|Jonesey95}} {{ping|Pppery}} {{ping|Xaosflux}} {{ping|firefly}} {{ping|Earl_Andrew}} {{ping|Tol}} help?<span style="color: #E12144">[[User talk:TRANSviada|<span style="color:#E12144">'''talk'''</span>]][[User:TRANSviada|<span style="color:#E12144">'''&#64;TRANSviada'''</span>]]</span> 22:27, 25 November 2021 (UTC)
:{{ping|HJ_Mitchell}} can you have a look at this?<span style="color: #E12144">[[User talk:TRANSviada|<span style="color:#E12144">'''talk'''</span>]][[User:TRANSviada|<span style="color:#E12144">'''&#64;TRANSviada'''</span>]]</span> 21:13, 25 November 2021 (UTC)
::Sorry, I'd have no idea what I was doing. [[User:HJ Mitchell|<b style="color: teal; font-family: Tahoma">HJ&nbsp;Mitchell</b>]] &#124; [[User talk:HJ Mitchell|<span style="color: navy; font-family: Times New Roman" title="(Talk page)">Penny for your thoughts?</span>]] 21:19, 25 November 2021 (UTC)
:::{{ping|HJ_Mitchell}}Do you mean back when you created this template? I implemented the above changes in [[Template:Lang-zh/sandbox/tr]] pretty much by copying what the already existing <code>l</code> (literal translation), so it works just as that but with different letter and abbreviation,  and am using it at [[Shizuka (band)]], so you can have a look that it works. Those are really small changes. The only thing that could go wrong is if the elseif was implemented wrong, but it work as expected in [[Shizuka (band)]].<span style="color: #E12144">[[User talk:TRANSviada|<span style="color:#E12144">'''talk'''</span>]][[User:TRANSviada|<span style="color:#E12144">'''&#64;TRANSviada'''</span>]]</span> 21:59, 25 November 2021 (UTC)
:::::Erm, it looks like I just protected it, back in 2014 (seven and a half years ago!), almost certainly from an RfPP request. As far as I know, I've never made a substantive edit to any Lua module. I write articles, block vandals, and sometimes clear admin backlogs but I don't get involved in technical matters. Sorry. Try a different admin. [[User:HJ Mitchell|<b style="color: teal; font-family: Tahoma">HJ&nbsp;Mitchell</b>]] &#124; [[User talk:HJ Mitchell|<span style="color: navy; font-family: Times New Roman" title="(Talk page)">Penny for your thoughts?</span>]] 22:13, 25 November 2021 (UTC)
:cc {{ping|Primefac}} {{ping|Number 57}} {{ping|Izno}} {{ping|DannyS712}} --<span style="color: #E12144">[[User talk:TRANSviada|<span style="color:#E12144">'''talk'''</span>]][[User:TRANSviada|<span style="color:#E12144">'''&#64;TRANSviada'''</span>]]</span> 03:16, 25 November 2021 (UTC)
:Why is [[Template:Lang-zh/sandbox/tr]] being used in mainspace? There are seventeen uses in [[Shizuka (band)]]; there should be none. --[[User:Redrose64|<span style="color:#a80000; background:#ffeeee; text-decoration:inherit">Red</span>rose64]] &#x1f339; ([[User talk:Redrose64|talk]]) 22:29, 12 May 2021 (UTC)
::Fixed by {{u|Frietjes}}. --[[User:Redrose64|<span style="color:#a80000; background:#ffeeee; text-decoration:inherit">Red</span>rose64]] &#x1f339; ([[User talk:Redrose64|talk]]) 09:41, 5 November 2021 (UTC)
:{{not done}} Please make your edits in [[Module:Lang-zh/sandbox|the sandbox]] and test this first.  Once sandboxed and validated, feel free to reactivate the edit request. — [[User:Xaosflux|<span style="color:#FF9933; font-weight:bold; font-family:monotype;">xaosflux</span>]] <sup>[[User talk:Xaosflux|<span style="color:#009933;">Talk</span>]]</sup> 22:38, 25 November 2021 (UTC)
::{{ping|Xaosflux}} I just made it there [[Module:Lang-zh/sandbox|the sandbox]]. What do you mean by test? Unit test or use case test? If the latter see https://en.wikipedia.org/wiki/Sandbox/TRANSviada/Lang-zh/tr.<span style="color: #E12144">[[User talk:TRANSviada|<span style="color:#E12144">'''talk'''</span>]][[User:TRANSviada|<span style="color:#E12144">'''&#64;TRANSviada'''</span>]]</span> 23:37, 25 November 2021 (UTC)
:::requeued for update. — [[User:Xaosflux|<span style="color:#FF9933; font-weight:bold; font-family:monotype;">xaosflux</span>]] <sup>[[User talk:Xaosflux|<span style="color:#009933;">Talk</span>]]</sup> 00:26, 26 November 2021 (UTC)
:::: {{done}} [[User:Pppery|* Pppery *]] [[User talk:Pppery|<sub style="color:#800000">it has begun...</sub>]] 17:09, 5 December 2021 (UTC)

== Traditional first, optionally ==

If you saw the article of the Cantonese movie, [[Bio Zombie]], you'd notice that the simplified Chinese characters are displayed fisrt, even though the title is in Cantonese. There is no way of altering which appears first, since the template mandates simplified characters first then traditional characters. <small>--[[User:Mahmudmasri|Mahmudmasri]] ([[User talk:Mahmudmasri|talk]]) 16:23, 16 March 2021 (UTC)</small>
:You can alter which appears first. Use the parameter <code>|first=t</code> to put the traditional script first. See [[Template:Lang-zh#Ordering]]. [[User:Rincewind42|Rincewind42]] ([[User talk:Rincewind42|talk]]) 08:21, 21 February 2022 (UTC)

== Link to Wiktionary entry ==

Would it also be desirable to add an option to link the Chinese text to their respective entries in Wiktionary? Perhaps something like <code>wikt=yes</code> would render a {{tlx |Lang-zh| t{{=}}中國 | s{{=}}中国 | wikt{{=}}yes }} entry as:

:[[Simplified Chinese characters|simplified Chinese]]: <span lang="zh-Hans">{{wikt-lang|zh|中国}}</span>; [[Traditional Chinese characters]]: <span lang="zh-Hant">{{wikt-lang|zh|中國}}</span>

This surrounds each entry using <code><nowiki>{{wikt-lang|zh|...}}</nowiki></code>. &mdash; [[User:Umofomia|Umofomia]] ([[User talk:Umofomia|talk]]) 19:00, 19 August 2022 (UTC)

:I just tried implementing the functionality myself [[Special:Diff/1057174846/1105351364|in the sandbox]] and it appears to work:
::[[simplified Chinese characters|simplified Chinese]]&#58; <span lang="zh-Hans"><span lang="zh">[[wikt:中国#Chinese|中国]]</span></span>; [[traditional Chinese characters|traditional Chinese]]&#58; <span lang="zh-Hant"><span lang="zh">[[wikt:中國#Chinese|中國]]</span></span>
:I don't currently have template editor privileges to commit this change to the main template but I can look into requesting it. &mdash; [[User:Umofomia|Umofomia]] ([[User talk:Umofomia|talk]]) 21:03, 19 August 2022 (UTC)

== Foochow Romanized/Bàng-uâ-cê ==

Hello, can a parameter for [[Foochow Romanized]] be created? --[[User:Lousysofa|Lousysofa]] ([[User talk:Lousysofa|talk]]) 17:02, 27 March 2023 (UTC)

== Preventing problems with italic and literals ==

Hi! I noticed a problem when someone wants to use literals with italic next to a bold word. For example the line below...<br>
<code><nowiki>'''Pak Mong''' ({{zh|t=白芒|l=white ''[[miscanthus]]''}})</nowiki> </code><br>
will produce something like...<br>
'''Pak Mong''' ([[Traditional Chinese characters|Chinese]]: 白芒; [[Literal translation|lit.]] 'white ''[[miscanthus]]''<nowiki/>')
<br>instead of...<br>
'''Pak Mong''' ([[Traditional Chinese characters|Chinese]]: 白芒; [[Literal translation|lit.]] 'white [[miscanthus|''miscanthus'']]')
<br>
In order to solve the problem we could just change the line 193 from...
 val = "'" .. val .. "'"
to...
 val = "<nowiki><nowiki></nowiki>'</nowiki>" .. val .. "<nowiki><nowiki></nowiki>'</nowiki>"
What do you think? ({{ping|Underwaterbuffalo}}) -- [[User:Basilicofresco|<span style="font:small-caps 1em Verdana;color:green">Basilicofresco</span>]] ([[User talk:Basilicofresco|msg]]) 17:16, 19 October 2023 (UTC)
:Thank you for raising the issue encountered by [[User:FrescoBot|FrescoBot]] at [[Pak Mong]] article. I don't have any expertise with modules. As long as the fix solves the issue and does not create others, I am all in favor! [[User:Underwaterbuffalo|Underwaterbuffalo]] ([[User talk:Underwaterbuffalo|talk]]) 09:34, 21 October 2023 (UTC)
:Yes, the single quotes used to mark literal glosses should not be interpreted as wiki markup. [[User talk:Kanguole|Kanguole]] 09:42, 21 October 2023 (UTC)
:The pending revision I have to the module currently produces an output of
::{{lang-zh/sandbox|t=白芒|l=white ''[[miscanthus]]''<!--inserted nowiki to fix missing italic end tag--><nowiki/>}}, which i'm noticing isn't entirely correct. i'll fix it asap.
:[[User:Remsense|<span style="border-radius:3px 0 0 3px;padding:4px 3px;background:#1E816F;color:#fff">'''Remsense'''</span>]][[User talk:Remsense|<span lang="zh" style="border:1px solid #1E816F;border-radius:0 2px 2px 0;padding:2px;color:#000">聊</span>]] 21:37, 21 October 2023 (UTC)
::And there we are! Properly escaping quotes now has
:::<code><nowiki>'''Pak Mong''' ({{Lang-zh/sandbox|t=白芒|l=white ''[[miscanthus]]''}})</nowiki></code>
:::output
:::'''Pak Mong''' ({{Lang-zh/sandbox|t=白芒|l=white ''[[miscanthus]]''<!--inserted nowiki to fix missing italic end tag--><nowiki/>}})
::[[User:Remsense|<span style="border-radius:3px 0 0 3px;padding:4px 3px;background:#1E816F;color:#fff">'''Remsense'''</span>]][[User talk:Remsense|<span lang="zh" style="border:1px solid #1E816F;border-radius:0 2px 2px 0;padding:2px;color:#000">聊</span>]] 17:13, 23 October 2023 (UTC)

== Template-protected edit request ==

Allow specifying {{mono|t}} variant: {{mono|zh-Hant-HK}} vs {{mono|zh-Hant-TW}}. See [[:File:Source_Han_Sans_Version_Difference.svg|this image]] for an example of {{lang|zh-HK|返}} vs {{lang|zh-TW|返}}. [[User:Northern Moonlight|<span style="font-family:system-ui,Inter,-apple-system,sans-serif;background-color:#f3f3fe;padding:2px 5px;border-radius:3px;white-space:nowrap">NM</span>]] 02:45, 20 November 2023 (UTC)

:I will write a patch for this ASAP. Here's the question: how should it work? I am thinking just additional parameters {{para|tw}} and {{para|th}}. But how the module presently works, if only one character field is specified, it just gets tagged as {{code|zh}}. But it should be trivial to tweak the code so that the more specific language tag is used when specifying only {{para|t}} or {{para|s}}, et al.[[User:Remsense|<span style="border-radius:3px 0 0 3px;padding:4px 3px;background:#1E816F;color:#fff">'''Remsense'''</span>]][[User talk:Remsense|<span lang="zh" style="border:1px solid #1E816F;border-radius:0 2px 2px 0;padding:2px;color:#000">聊</span>]] 02:54, 20 November 2023 (UTC)
::I don’t think there’s a need to modify the logic for <code>|t=</code> and <code>|s=</code>. Sometimes the region is really irrelevant that you only want to specify the script (for example, in a page that talks about the history of the writing system).
::We should also avoid ambiguous abbreviations and just go with a slightly longer format like <code>t_hk</code> and <code>s_sg</code>.
::[[User:Northern Moonlight|<span style="font-family:system-ui,Inter,-apple-system,sans-serif;background-color:#f3f3fe;padding:2px 5px;border-radius:3px;white-space:nowrap">NM</span>]] 05:08, 26 November 2023 (UTC)
:::fair—it's really difficult, re: abbreviations, because after the 10th time entering it in an article, you might wish concision was favored over disambiguation, but yeah. I still haven't started on this, but I'll keep this in mind when I get to it shortly. [[User:Remsense|<span style="border-radius:3px 0 0 3px;padding:4px 3px;background:#1E816F;color:#fff">'''Remsense'''</span>]][[User talk:Remsense|<span lang="zh" style="border:1px solid #1E816F;border-radius:0 2px 2px 0;padding:2px;color:#000">聊</span>]] 05:26, 26 November 2023 (UTC)

== Template-protected edit request on 14 October 2023 ==

{{edit template-protected|Module:Lang-zh|answered=yes}}
Diff with my sandbox implementation:
{{diffsandbox|Module:Lang-zh|rev1=1117460852|rev2=1180117223}}

This does three major things, things that address real perennial limitations with the {{tlx|zh}} template:
* It adds a new {{para|out}} parameter, allowing one to select one of the terms to place before the rest, which are then put in brackets, an extremely common presentation format when writing Chinese text inline in paragraphs and tables.
* It now uses double quotes for the {{para|tr}} parameter, for "full translations" instead of glosses, as is prescribed in [[MOS:FOREIGN]] and [[MOS:ZH]].
* It enables the use of multiple, correctly quoted glosses (literal translations, {{para|l}}), delineated by commas.

Examples:
:{{tlx|Lang-zh/sandbox|c{{=}}我|p{{=}}wǒ|l{{=}}I, me|j{{=}}ngo<nowiki><sup>5</sup></nowiki>|out{{=}}j}}
:↓
:{{Lang-zh/sandbox|c=我|p=wǒ|j=ngo<sup>5</sup>|l=I, me|out=j}}⸻{{para|out|j}} puts the value for {{para|j}} outside the brackets
:{{hr}}
:{{tlx|Lang-zh/sandbox|s{{=}}中华|t{{=}}中華|p{{=}}Zhōnghuá|l{{=}}China|out{{=}}p|labels{{=}}no}}
:↓
:{{Lang-zh/sandbox|s=中华|t=中華|p=Zhōnghuá|l=China|out=p|labels=no}}
:{{hr}}
:{{tlx|Lang-zh/sandbox|s{{=}}她刚刚离开了|l{{=}}she's just left|out{{=}}l}}
:↓
:{{Lang-zh/sandbox|s=她刚刚离开了|l=she's just left|out=l}}
:{{hr}}
:{{tlx|Lang-zh/sandbox|s{{=}}电脑|t{{=}}電腦|tr{{=}}computer|p{{=}}diànnǎo|l{{=}}electric brain|out{{=}}tr|labels{{=}}no}}
:↓
:{{Lang-zh/sandbox|s=电脑|t=電腦|tr=computer|p=diànnǎo|l=electric brain|out=tr|labels=no}}⸻double quotes now used for {{para|tr}}
{{hr}}
I was apprehensive about patching the template, but I'm pretty sure I haven't broken anything, I'm sure someone more experienced than I will take a look-see before it gets merged. :) [[User:Remsense|<span style="border-radius:3px 0 0 3px;padding:4px 3px;background:#1E816F;color:#fff">'''Remsense'''</span>]][[User talk:Remsense|<span lang="zh" style="border:1px solid #1E816F;border-radius:0 2px 2px 0;padding:2px;color:#000">聊</span>]] 17:20, 14 October 2023 (UTC)
:[[User:Remsense|Remsense]], would you be so kind in adding testcases for this change at [[Template:Lang-zh/testcases]]? [[User:SWinxy|SWinxy]] ([[User talk:SWinxy|talk]]) 20:36, 14 October 2023 (UTC)
::Certainly! I'll try to cover all the edge cases I can think of. [[User:Remsense|<span style="border-radius:3px 0 0 3px;padding:4px 3px;background:#1E816F;color:#fff">'''Remsense'''</span>]][[User talk:Remsense|<span lang="zh" style="border:1px solid #1E816F;border-radius:0 2px 2px 0;padding:2px;color:#000">聊</span>]] 20:37, 14 October 2023 (UTC)
::I've gone ahead and added some! if you'd like me to be more thorough/any test cases you need to see, let me know. (Oh, and I found a bug in the process.) [[User:Remsense|<span style="border-radius:3px 0 0 3px;padding:4px 3px;background:#1E816F;color:#fff">'''Remsense'''</span>]][[User talk:Remsense|<span lang="zh" style="border:1px solid #1E816F;border-radius:0 2px 2px 0;padding:2px;color:#000">聊</span>]] 21:17, 14 October 2023 (UTC)
::I fixed the (very obvious!) bug, and added the ability to put both simplified and traditional outside the parentheses. hopefully everything is good now! [[User:Remsense|<span style="border-radius:3px 0 0 3px;padding:4px 3px;background:#1E816F;color:#fff">'''Remsense'''</span>]][[User talk:Remsense|<span lang="zh" style="border:1px solid #1E816F;border-radius:0 2px 2px 0;padding:2px;color:#000">聊</span>]] 00:37, 18 October 2023 (UTC)
: I have had a look at the testcases, and it's unclear from them what the use case for this is, what articles it would be used in. I mean when you have something like

:: "computer" (电脑; 電腦; diànnǎo; 'electric brain')

: It would be normal to use the template for everything inside the bracket, and normal text for "computer". The ones where that wouldn't work such as:

:: pinyin: Cài Yīngwén (Chinese: 蔡英文)

: I can't see a use for. You would never put pinyin like that in body text, with the Chinese characters in brackets. Generally in an article both the Chinese and Romanisations should go in brackets so as not to upset the flow of the English text, with the Chinese first. When the Chinese is being discussed, such as in an article on the language, this template isn't really suited for it.--[[Special:Contributions/2A04:4A43:90AF:FAB6:29E3:5D64:C243:2A6D|2A04:4A43:90AF:FAB6:29E3:5D64:C243:2A6D]] ([[User talk:2A04:4A43:90AF:FAB6:29E3:5D64:C243:2A6D|talk]]) 02:08, 15 October 2023 (UTC)
::You are able to put any field outside the brackets: gloss, characters, or romanization. There are situations where any of the three are appropriate, usually depending on whether the orthography, semantics, or phonetics are the focus of the prose. I've worked with all of them editing Chinese-related articles. The Tsai Ing-wen example was copied from above, I wouldn't actually write a personal name in such a way in an article. The cases were meant to demonstrate that all the features are working properly.
::Here is a tweaked excerpt  from [[Chinese characters]] where a pinyin-first example is the best-flowing, in my opinion.
::: The barrier between pronunciation and meaning is never total, however: in the Chinese system, phonetic characters may be deliberately chosen as to create certain connotations. This regularly happens for corporate brand names: for example, '[[Coca-Cola]]' is translated phonetically as {{Lang-zh/sandbox|labels=no|s=可口可乐|t=可口可樂|p=Kěkǒu Kělè|out=p}}, with the characters selected so as to possess an additional meaning of 'delicious and enjoyable'. A more literal translation would be 'the mouth can be happy', though the phrase is technically grammatically sound.
:: Also, I think it's worth putting non-diacritical pinyin in {{para|lang}} tags when you can, because it will still be pronounced better by a screenreader than an English voice selected will attempting to read it aloud, e.g. {{tlx|zh|labels{{=}}no|c{{=}}蔡英文|p{{=}}Cai Yingwen|out{{=}}p}} is better for screenreaders than just {{code|Cai Yingwen <nowiki>({{zh|labels=no|c=蔡英文}}</nowiki>)}}.
:: [[User:Remsense|<span style="border-radius:3px 0 0 3px;padding:4px 3px;background:#1E816F;color:#fff">'''Remsense'''</span>]][[User talk:Remsense|<span lang="zh" style="border:1px solid #1E816F;border-radius:0 2px 2px 0;padding:2px;color:#000">聊</span>]] 02:13, 15 October 2023 (UTC)
::: {{done}} [[User:Pppery|* Pppery *]] [[User talk:Pppery|<sub style="color:#800000">it has begun...</sub>]] 00:01, 27 October 2023 (UTC)
::::[[User:Pppery|Pppery]], thank you so much!<span id="Remsense:1698365581970:Module_talkFTTCLNLang-zh" class="FTTCmt"> —&nbsp;[[User:Remsense|<span style="border-radius:3px 0 0 3px;padding:4px 3px;background:#1E816F;color:#fff">'''Remsense'''</span>]][[User talk:Remsense|<span lang="zh" style="border:1px solid #1E816F;border-radius:0 2px 2px 0;padding:2px;color:#000">聊</span>]] 00:13, 27 October 2023 (UTC)</span>
::::[[User:Pppery|Pppery]], Actually, I made several revisions to the module from the initial one, making initial fixes. Could you merge the newest revision of the sandbox?<span id="Remsense:1698366611655:Module_talkFTTCLNLang-zh" class="FTTCmt"> —&nbsp;[[User:Remsense|<span style="border-radius:3px 0 0 3px;padding:4px 3px;background:#1E816F;color:#fff">'''Remsense'''</span>]][[User talk:Remsense|<span lang="zh" style="border:1px solid #1E816F;border-radius:0 2px 2px 0;padding:2px;color:#000">聊</span>]] 00:30, 27 October 2023 (UTC)</span>
::::: {{done}} Those too. [[User:Pppery|* Pppery *]] [[User talk:Pppery|<sub style="color:#800000">it has begun...</sub>]] 00:44, 27 October 2023 (UTC)
{{re|Pppery|Remsense}} Was it after these edits that the lead of [[Prunus kansuensis]] started to look so bold? [[Special:Contributions/77.223.109.164|77.223.109.164]] ([[User talk:77.223.109.164|talk]]) 17:09, 19 December 2023 (UTC)

:Yes. I thought I tested adequately for this. It's not a bug that should've been introduced, but also I think there's never a real reason to put bold text inside this template, so it's good to identify when it's happening at least. [[User:Remsense|<span style="border-radius:2px 0 0 2px;padding:3px;background:#1E816F;color:#fff">'''Remsense'''</span>]][[User talk:Remsense|<span lang="zh" style="border:1px solid #1E816F;border-radius:0 2px 2px 0;padding:1px 3px;color:#000">留</span>]] 20:48, 19 December 2023 (UTC)

== Template-protected edit request on 5 February 2024 ==

{{edit template-protected|Module:Lang-zh|answered=yes}}
This may be politically inclined, but I am highly unsure if [[Tongyong Pinyin]] should be our generic <code>zh-Latn</code>, as the mainland [[Pinyin]] wins by [[Demographics of China|a very large margin in users]].

I propose the following changes:

<syntaxhighlight lang="diff">
--- 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",
</syntaxhighlight>

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

<syntaxhighlight lang="diff">
--- 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",
</syntaxhighlight> [[User:NasssaNser|NasssaNser]]<sub>[[User talk:NasssaNser|talk]]</sub> 11:01, 5 February 2024 (UTC)

: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? —[[User:Mx. Granger|Mx. Granger]]&nbsp;([[User talk:Mx. Granger|talk]] '''·''' [[Special:Contributions/Mx. Granger|contribs]]) 15:30, 10 February 2024 (UTC)
::Like the rest of the language metadata, it adds specificity for screenreaders, as well as other possible presentations of articles. [[User:Remsense|<span style="border-radius:2px 0 0 2px;padding:3px;background:#1E816F;color:#fff">'''Remsense'''</span>]][[User talk:Remsense|<span lang="zh" style="border:1px solid #1E816F;border-radius:0 2px 2px 0;padding:1px 3px;color:#000">诉</span>]] 23:21, 10 February 2024 (UTC)
:{{agree}}– I double-checked, and IANA added Tongyong as a [https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry valid language subtag variant] in 2020. [[User:Remsense|<span style="border-radius:2px 0 0 2px;padding:3px;background:#1E816F;color:#fff">'''Remsense'''</span>]][[User talk:Remsense|<span lang="zh" style="border:1px solid #1E816F;border-radius:0 2px 2px 0;padding:1px 3px;color:#000">诉</span>]] 23:20, 10 February 2024 (UTC)
:: {{Done}} [[User:Pppery|* Pppery *]] [[User talk:Pppery|<sub style="color:#800000">it has begun...</sub>]] 04:53, 11 February 2024 (UTC)

== Template-protected edit request on 5 April 2024 ==

{{edit template-protected|Module:Lang-zh|answered=yes}}
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. [[User:Freelance Intellectual|Freelance Intellectual]] ([[User talk:Freelance Intellectual|talk]]) 08:49, 5 April 2024 (UTC)
: {{Done}} [[User:Pppery|* Pppery *]] [[User talk:Pppery|<sub style="color:#800000">it has begun...</sub>]] 02:53, 15 April 2024 (UTC)

== Double-quotes around glosses ==

Is there a reason we use double-quotes rather than single-quotes to show the output of {{para|tr}}? [[MOS:SIMPLEGLOSS]] suggests we should prefer singles. — <span class="vcard"><span class="fn">[[User:OwenBlacker|OwenBlacker]]</span> <small>(he/him; [[User talk:OwenBlacker|Talk]])</small></span> 17:37, 18 June 2024 (UTC)

:Because {{para|l}} is used for literal translations & glosses, and {{para|tr}} is (much more rarely) used for non-literal translations. [[User:Remsense|<span style="border-radius:2px 0 0 2px;padding:3px;background:#1E816F;color:#fff">'''Remsense'''</span>]][[User talk:Remsense|<span lang="zh" style="border:1px solid #1E816F;border-radius:0 2px 2px 0;padding:1px 3px;color:#000">诉</span>]] 17:39, 18 June 2024 (UTC)
::Aha, that makes sense. So I have probably been misusing {{para|tr}} when I should have been using {{para|l}}. Thank you! — <span class="vcard"><span class="fn">[[User:OwenBlacker|OwenBlacker]]</span> <small>(he/him; [[User talk:OwenBlacker|Talk]])</small></span> 18:03, 18 June 2024 (UTC)

== 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. [[User:Pacificboy|pacificboy]] ([[User talk:Pacificboy|talk]]) 03:56, 11 July 2024 (UTC)

: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. [[User:Remsense|<span style="border-radius:2px 0 0 2px;padding:3px;background:#1E816F;color:#fff">'''Remsense'''</span>]][[User talk:Remsense|<span lang="zh" style="border:1px solid #1E816F;border-radius:0 2px 2px 0;padding:1px 3px;color:#000">诉</span>]] 05:49, 11 July 2024 (UTC)
::Ah, that makes sense! I’ll convert it to a translation. Thanks. [[User:Pacificboy|pacificboy]] ([[User talk:Pacificboy|talk]]) 02:45, 12 July 2024 (UTC)

== Further romanization discussion ==
Coming off of my request to add Tâi-lô, what other romanization systems should be added to the template? I feel like [[Pha̍k-fa-sṳ]] annd [[Wugniu]] could be helpful. I don't see any IANA latn subtages for other Sinitic languages however. [[User:MSG17|MSG17]] ([[User talk:MSG17|talk]]) 15:53, 17 August 2024 (UTC)

== Template-protected edit request on 17 August 2024 ==

{{Edit template-protected|Module:Lang-zh|answered=yes}}

I propose the following changes to add [[Tâi-uân Lô-má-jī Phing-im Hong-àn|Tâi-lô]] romanization support. Of course, POJ covers 95% of Hokkien/Minnan use cases (hence why I have added the "tailo" IANA subtag) but it could still be useful for Taiwanese-specific pages. Additions and modifications below: 

<syntaxhighlight lang="diff">
--- Module:Lang-zh
+++ Module:Lang-zh

@@ after line 29 @@ local labels = {
 	["sl"] = "Sidney Lau",
    ["poj"] = "Pe̍h-ōe-jī",
+	["tl"] = "Tâi-lô",
	["zhu"] = "Zhuyin Fuhao",
	["l"] = "lit.",
    
@@ after line 46 @@ local wlinks  = {
 	["poj"] = "Pe̍h-ōe-jī",
+	["tl"] = "Tâi-uân Lô-má-jī Phing-im Hong-àn",
    
@@ after line 63 @@ local ISOlang = {
 	["poj"] = "nan-Latn",
+	["tl"] = "nan-Latn-tailo",

@@ after line 74 @@ local italic  = {
 	["poj"] = true,
+	["tl"] = true,

@@ at line 136 @@
-	local orderlist = {"c", "s", "t", "p", "tp", "w", "j", "cy", "sl", "poj", "zhu", "l", "tr"}
+	local orderlist = {"c", "s", "t", "p", "tp", "w", "j", "cy", "sl", "poj", "tl", "zhu", "l", "tr"}

@@ after line 150 @@ if (poj1) then
		orderlist[4] = "poj"
-		orderlist[5] = "p"
-		orderlist[6] = "tp"
-		orderlist[7] = "w"
-		orderlist[8] = "j"
-		orderlist[9] = "cy"
-		orderlist[10] = "sl"
+		orderlist[5] = "tl"
+		orderlist[6] = "p"
+		orderlist[7] = "tp"
+		orderlist[8] = "w"
+		orderlist[9] = "j"
+		orderlist[10] = "cy"
+		orderlist[11] = "sl"
	end
</syntaxhighlight>
[[User:MSG17|MSG17]] ([[User talk:MSG17|talk]]) 15:53, 17 August 2024 (UTC)

:@[[User:MSG17|MSG17]]: This sounds reasonable, and would be helpful on pages such as [[Penang Hokkien]] where both POJ and TL are used in the article text. @[[User:Pppery|Pppery]] or @[[User:Jonesey95|Jonesey95]], would you be able to help here? [[User:Freelance Intellectual|Freelance Intellectual]] ([[User talk:Freelance Intellectual|talk]]) 13:03, 19 September 2024 (UTC)
::I'll take a look at this ASAP, thank you for your improvements! <span style="border-radius:2px;padding:3px;background:#1E816F">[[User:Remsense|<span style="color:#fff">'''Remsense'''</span>]]<span style="color:#fff">&nbsp;‥&nbsp;</span>[[User talk:Remsense|<span lang="zh" style="color:#fff">'''论'''</span>]]</span> 13:06, 19 September 2024 (UTC)
:{{done}}<!-- Template:ETp --> <span style="border-radius:2px;padding:3px;background:#1E816F">[[User:Remsense|<span style="color:#fff">'''Remsense'''</span>]]<span style="color:#fff">&nbsp;‥&nbsp;</span>[[User talk:Remsense|<span lang="zh" style="color:#fff">'''论'''</span>]]</span> 13:48, 19 September 2024 (UTC)

== Trailing bold in l= not being removed ==

In <syntaxhighlight>{{zh|t=竹子林站|j=Zuk1 Zi2 Lam4 Zaam6|l = '''Bamboo Forest station'''}}</syntaxhighlight>, the opening bold markup is properly removed, but the trailing bold markup is not removed. It looks like the regular expression at <syntaxhighlight>term = string.gsub(term, "^([ \"']*)(.*)([ \"']*)$", "%2")</syntaxhighlight> needs some adjustment to the middle wildcard search. – [[User:Jonesey95|Jonesey95]] ([[User talk:Jonesey95|talk]]) 13:23, 16 September 2024 (UTC)

:{{ping|Jonesey95}} This is because the * operator is greedy, so .* matches everything else in the string. Changing .* to .*? would make it lazy, so that the final term catches all trailing characters. In other words, change the line of code to: <syntaxhighlight>term = string.gsub(term, "^([ \"']*)(.*?)([ \"']*)$", "%2")</syntaxhighlight> [[User:Freelance Intellectual|Freelance Intellectual]] ([[User talk:Freelance Intellectual|talk]]) 13:51, 16 September 2024 (UTC)
::Thanks! That fixed the problem at [[Zhuzilin station]] and probably other pages. – [[User:Jonesey95|Jonesey95]] ([[User talk:Jonesey95|talk]]) 17:26, 16 September 2024 (UTC)
::Thank you for fixing my shoddy regex, by the way. <span style="border-radius:2px;padding:3px;background:#1E816F">[[User:Remsense|<span style="color:#fff">'''Remsense'''</span>]]<span style="color:#fff">&nbsp;‥&nbsp;</span>[[User talk:Remsense|<span lang="zh" style="color:#fff">'''论'''</span>]]</span> 13:05, 19 September 2024 (UTC)
:::{{re|Jonesey95|Remsense}} On further reflection, this doesn't work as intended. I had thought the string was a regex, but it is in fact a Lua pattern, which is slightly different. The Lua equivalent of *? is - which would give: <syntaxhighlight>term = string.gsub(term, "^([ \"']*)(.-)([ \"']*)$", "%2")</syntaxhighlight> Writing .*? in Lua (as I suggested above) actually means greedily matching all characters (.*) followed by a single question mark (? can also be an operator, but Lua pattern operators can't be nested so in this context it is interpreted as a literal). So actually the new pattern usually doesn't make a substitution, unless there is a question mark. This means it usually fails, e.g. where there are multiple glosses separated by commas and spaces, the spaces are not stripped. However, looking at what the pattern match applies to, I'm not completely sure I understand why the quotes should be stripped in the first place (is there a set of testcases to check against?). At [[Zhuzilin station]], the current code makes no substitution, and so it keeps the bold formatting, presumably as intended. The old code meant that the bold formatting was stripped at the beginning and not the end, so the rest of the article became bold (which was a bad and confusing error). Correcting .*? to .- as above would strip both, making it impossible to add bold formatting.  Is the intention to catch cases where an editor unnecessarily adds quotes to the gloss?  Is this a common problem?  If so, is removing the ability to add bold and italic formatting a fair price to pay?
::: If we want to strip one quote mark but no more (so that we catch editors manually adding quotes, but allow formatting), pattern matching is a bit more complicated. I think it would be easiest to separate the stripping of whitespace and quotes. When stripping one single quote, we need to check that there isn't more than one, but we also need to allow the string to contain an apostrophe (so we can't just use [^']- in the middle) and a gloss could potentially be a single character (so we can't just use [^'].-[^'] in the middle). So it seems easiest to strip the leading and trailing quotes separately. This gives three lines (I've also removed two sets of brackets that were capturing substrings that weren't used): <syntaxhighlight>term = string.gsub(term, "^ *(.-) *$", "%1")
term = string.gsub(term, "^[\"']?([^\"'].-)$", "%1")
term = string.gsub(term, "^(.-[^\"'])[\"']?$", "%1")</syntaxhighlight> [[User:Freelance Intellectual|Freelance Intellectual]] ([[User talk:Freelance Intellectual|talk]]) 15:43, 24 September 2024 (UTC)
::::I think it's fine to strip all quote marks, in any quantity. That was the original intent of the code, and I don't see any complaints on this page. Adding bold to text is probably against [[WP:MOS]], and adding italics should be done with a parameter. People can use {{tag|b}} and {{tag|i}} tags if they insist on them. – [[User:Jonesey95|Jonesey95]] ([[User talk:Jonesey95|talk]]) 15:51, 24 September 2024 (UTC)
:::::Okay. I had taken your comment about fixing the Zhuzilin station article to mean that keeping the bold markup was intended, but I can see why it could be discouraged. I've also just found [[Template:Lang-zh/testcases]] (I had only looked under Module:Lang-zh before), and I don't see any testcases for stripping markup. So, if stripping markup is the desired functionality, the .- version above would work. I think it would make sense to document this, since there are three different kinds of thing being stripped: whitespace, markup, and quotes (double quotes aren't markup). It could be documented either on [[Template:Lang-zh/doc]] or directly as a code comment next to the line we're discussing, e.g. "remove trailing and leading spaces, quotes, and bold/italic markup". [[User:Freelance Intellectual|Freelance Intellectual]] ([[User talk:Freelance Intellectual|talk]]) 20:39, 24 September 2024 (UTC)
:::::Currently, this stripping only applies to literal glosses and not translations, but they should reasonably be treated the same. So, fixing the pattern, matching all whitespace (not just spaces), expanding the comments, and applying the same to the translation, I suggest changing lines 236-247 to the following:<syntaxhighlight>			elseif (part == "l") then
				local terms = ""
				-- put individual, potentially comma-separated glosses in single quotes
				-- (first strip leading and trailing whitespace and quotes, including bold/italic markup)
				for term in val:gmatch("[^;,]+") do
					term = string.gsub(term, "^([%s\"']*)(.-)([%s\"']*)$", "%2")
					terms = terms .. "&apos;" .. term .. "&apos;, "
				end
				val = string.sub(terms, 1, -3)
			elseif (part == "tr") then
				-- put translations in double quotes
				-- (first strip leading and trailing spaces and quotes, including bold/italic markup)
				val = string.gsub(val, "^([%s\"']*)(.-)([%s\"']*)$", "%2")
				val = "&quot;" .. val .. "&quot;"
			end</syntaxhighlight> [[User:Freelance Intellectual|Freelance Intellectual]] ([[User talk:Freelance Intellectual|talk]]) 09:31, 25 September 2024 (UTC)
:::::{{re|Jonesey95|Remsense}} What do you think? Are you happy with the above suggestion?
{{edit template-protected|Module:Lang-zh|answered=yes}}
:::::Also, instead of directly using a Lua string pattern, it might be more readable and maintainable to use an existing function for stripping leading and trailing characters, namely mw.text.trim:<syntaxhighlight>			elseif (part == "l") then
				local terms = ""
				-- put individual, potentially comma-separated glosses in single quotes
				-- (first strip leading and trailing whitespace and quotes, including bold/italic markup)
				for term in val:gmatch("[^;,]+") do
					term = mw.text.trim(term, "%s\"'")
					terms = terms .. "&apos;" .. term .. "&apos;, "
				end
				val = string.sub(terms, 1, -3)
			elseif (part == "tr") then
				-- put translations in double quotes
				-- (first strip leading and trailing spaces and quotes, including bold/italic markup)
				val = mw.text.trim(val, "%s\"'")
				val = "&quot;" .. val .. "&quot;"
			end</syntaxhighlight> [[User:Freelance Intellectual|Freelance Intellectual]] ([[User talk:Freelance Intellectual|talk]]) 09:02, 27 September 2024 (UTC)
::::::{{re|Jonesey95|Remsense}} pinging again. The current code inserts quotes incorrectly, e.g. on the following pages you can see an opening quote followed by a space: [[Gun (staff)]], [[Indonesian slang]], [[Ping On]]. The code above would fix this. [[User:Freelance Intellectual|Freelance Intellectual]] ([[User talk:Freelance Intellectual|talk]]) 14:23, 8 October 2024 (UTC)
::::::: Reping {{u|Remsense}}. Could you please look at this? I think you're one of the only template editors who has enough understanding of Chinese orthography to understand what is being changed here and why. [[User:Pppery|* Pppery *]] [[User talk:Pppery|<sub style="color:#800000">it has begun...</sub>]] 17:19, 16 November 2024 (UTC)
::::::::Will have this looked at ASAP. Huge apologies for letting it slip through the cracks for months. <span style="border-radius:2px;padding:3px;background:#1E816F">[[User:Remsense|<span style="color:#fff">'''Remsense'''</span>]]<span style="color:#fff">&nbsp;‥&nbsp;</span>[[User talk:Remsense|<span lang="zh" style="color:#fff">'''论'''</span>]]</span> 23:39, 16 November 2024 (UTC)
:::::::::{{done}}{{snd}}so sorry for the delay, again. <span style="border-radius:2px;padding:3px;background:#1E816F">[[User:Remsense|<span style="color:#fff">'''Remsense'''</span>]]<span style="color:#fff">&nbsp;‥&nbsp;</span>[[User talk:Remsense|<span lang="zh" style="color:#fff">'''论'''</span>]]</span> 23:37, 18 November 2024 (UTC)