Jump to content

Template talk:Infobox Chinese

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Jdlrobson (talk | contribs) at 18:53, 11 July 2024 (→‎Issue in dark mode or inappropriate use of infobox: new section). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Request for Literal meaning Japanese field

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)[reply]

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

Template-protected edit request on 30 April 2023

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)[reply]

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)[reply]
Closing per Trialpears' comment - it appears no qualified eyes are coming. * Pppery * it has begun... 16:59, 6 May 2023 (UTC)[reply]

Lang of bpmf parameter

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)[reply]

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

Pe̍h-ōe-jī and Tâi-Lô

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)[reply]

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)[reply]

Template-protected edit request on 11 May 2024

ENGVAR support: all I need is for labels to say "Romanisation" instead of "Romanization" (et al.) when an |engvar=b parameter is supplied, but I couldn't quite figure out how to do it in the corresponding module code. Remsense诉 08:07, 7 June 2024 (UTC)[reply]

Issue in dark mode or inappropriate use of infobox

It seems this infobox can sometimes have Chinese characters in the main image as in Kiwifruit and and sometimes photos as in Guanyin.

In dark mode (e.g. https://en.wikipedia.org/wiki/Guanyin?vectornightmode=1, not to be confused with gadget), the former works great as it is inverted, but the latter is broken. The invert doesn't appear to always work as in Hong_Kong.

Looks like the infobox description should be clarified to describe if photos are permitted and if so, be altered to support both use cases (only applying the invert when SVG text is given)

Thanks in advance for your help working on how to fix this! I am not sure how?

@User:Queen of Hearts fixed this like so but it would be good if there were clearer guidelines on this template about how to handle this situation! 🐸 Jdlrobson (talk) 18:53, 11 July 2024 (UTC)[reply]

Retrieved from "https://en.wikipedia.org/w/index.php?title=Template_talk:Infobox_Chinese&oldid=1233941863"