Template talk:Infobox Chinese

Following the example for Korean where there is a field lk for a literal meaning from Korean, a field such as lj would be useful and pertinent for literal meanings for the Japanese section. Waerloeg (talk) 08:26, 23 February 2022 (UTC)

Seconded toobigtokale (talk) 22:06, 15 August 2023 (UTC)

The Uyghur parameter of this template doesn't display Arabic text properly. It's missing the rendering present at Template:lang-ar for example. Can somebody fix this? Haffaz (talk) 23:47, 4 March 2022 (UTC)

 Not done: it's not clear what changes you want to be made. Please mention the specific changes in a "change X to Y" format. The edit request template should only be added once the way to fix it is figured out and tested in the sandbox. DannyS712 (talk) 00:07, 5 March 2022 (UTC)

At the very least, provide links to examples where you think that the infobox is not doing the correct thing.

The infobox at right looks correct to me. When I look at the html rendered by that infobox I find this:

<templatestyles src="Ug-textonly/styles.css" /><span lang="ug" class="font-uig" style="font-size:125%;">جۇڭخۇا مىنگو پرېزىدېنت</span>‎

The <templatestyles src="Ug-textonly/styles.css" /> tag refers to Template:Ug-textonly/styles.css where class="font-uig" is defined

{{infobox chinese}} calls {{ug-textonly}} to get that output (see Module:Infobox multi-lingual name line 849); cf:

جۇڭخۇا مىنگو پرېزىدېنت‎ ← {{ug-textonly|جۇڭخۇا مىنگو پرېزىدېنت}} – should look the same as the infobox at right except for font size which is reduced in infoboxen by MediaWiki:Common.css

جۇڭخۇا مىنگو پرېزىدېنت ← {{lang|ar|جۇڭخۇا مىنگو پرېزىدېنت}} – because you mentioned {{lang-ar}}, may, probably does, look similar but different because browser selects a different font

جۇڭخۇا مىنگو پرېزىدېنت – plain text which may, probably does, look different from both the ug and ar renderings because browser probably uses the same font that it uses for Latn-script text

—Trappist the monk (talk) 01:26, 5 March 2022 (UTC)

Do we really need any font specification in 2023 for the template? Currently, the template spans the Zhuang text as in the example<span style="font-family: Arial Unicode MS, sans-serif;">Namzningz</span> and without a class,even though the text shown is within the ASCII characters that need no special fonts. Please, remove the font-family specification. The module in question is this: Module:Infobox multi-lingual name; the edit in question by user:Trappist the monk who barred the template from editing by non-template editors. Thanks --Mahmudmasri (talk) 12:29, 4 January 2023 (UTC)

You appear to be accusing me of wrongdoing. Why?

Function ibox_mln_za() merely implements the (now deleted) template {{Infobox Chinese/Zhuang}}. At the 16:43 5 November 2014 edit to {{Infobox Chinese/Zhuang}}, Editor ASDFGH changed:

|  data2  = {{{zha<includeonly>|</includeonly>}}}

to:

|  data2  = <span style="font-family: Arial Unicode MS, Arial, sans-serif;">{{{zha<includeonly>|</includeonly>}}}</span>

Editor ASDFGH did not leave an edit summary and there was no discussion at Template talk:Infobox Chinese/Zhuang. Alas, Editor ASDFGH has not been with us since 11 October 2021 so we will likely never know why the <span>...</span> tag was added.

For my part, the <span>...</span> tag was simply copied from the template to the module assuming good faith that it was necessary. Is the tag breaking anything? When the Zhuang text is written using Sawndip characters, does the tag help or hinder that rendering? Is there a consensus to remove the tag?

—Trappist the monk (talk) 14:52, 4 January 2023 (UTC)

Hi Trappist. I didn't intend to accuse you of anything bad if that appeared to be so. I only wanted to make it easier for whomever is gonna follow up with me to remove the font specification which is unnecessary and the words written for Zhuang are always in ASCII characters, therefore we need to remove them.

I have the fonts in question on my system, but they fail to display Sawndip anyway and it is never written in that template.

Since you have access to remove the code, I would like to request you to do it, please. Many texts were tagged with font specifications in the part, but over the years, they have been removed as newer systems don't require them in most cases. Thanks. --Mahmudmasri (talk) 13:23, 5 January 2023 (UTC)

 Not done 10 days later and I don't know a reason for that. --Mahmudmasri (talk) 10:55, 16 January 2023 (UTC)

@Jc86035, Trialpears, and WOSlinker: You are the rest of the editors of the template and I wish someone proceeds. Thanks. --Esperfulmo (talk) 13:16, 25 January 2023 (UTC)

From what I can tell is this extra span completely useless. All text in articles inherit font-family: sans-serif if nothing else is specified and I don't see any reason why we should be more specific for this specific element. --Trialpears (talk) 23:10, 25 January 2023 (UTC)

Thanks Trialpears for your input. Well, I think we are one step closer to deleting the line. --Esperfulmo (talk) 13:47, 26 January 2023 (UTC)

Add a "lang(x)_translit" field to compliment the lang(x)_content and lang(x) fields. Viewable via dropdown menu, like the languages already included in the template. Otherwise, add Kazakh and Kyrgyz fields to the template; I do not know why Tetum, a language spoken only on the island of Timor which has no significant Chinese community, is included in this infobox's fields, but not Kazakh or Kyrgyz which have their own autonomous areas in China. Yue🌙 07:06, 30 April 2023 (UTC)

This template is not just for China nowadays and really should be named something like Infobox transcription but that RM failed. I agree with adding Kazakh and Kyrgyz since they are (usually at least) not written in the Latin script. I'm not quite sure what exactly a translit field would do though. Usually edit requests are only for implementing edits in the sandbox rather than suggesting features but I won't close it quite yet since a few more qualified eyes may come here if it's open. --Trialpears (talk) 12:11, 30 April 2023 (UTC)

Closing per Trialpears' comment - it appears no qualified eyes are coming. * Pppery * _{it has begun...} 16:59, 6 May 2023 (UTC)

Hey, I want to have two manchu names appear. Is it possible to do this? toobigtokale (talk) 00:55, 2 May 2023 (UTC)

oh nvm got it; just nest another infobox chinese inside, and enable the child=yes flag. toobigtokale (talk) 00:59, 2 May 2023 (UTC)

I'm not sure where exactly it is implemented, but the value of the bpmf parameter ends up incorrectly marked up as zh-Latn instead of zh-Bopo. – MwGamera (talk) 12:03, 28 June 2023 (UTC)

I also ran into this. Remsense诉 22:07, 11 February 2024 (UTC)

Pe̍h-ōe-jī has now a variant tag in BCP 47: Its text should emit nan-Latn-pehoeji instead of just nan-Latn.-- Error (talk) 12:40, 22 May 2024 (UTC)

Same about Tâi-uân Lô-má-jī Phing-im Hong-àn and nan-Latn-tailo --Error (talk) 12:49, 22 May 2024 (UTC)