I think it's just a mistake. Modules should not use sandboxes, because everybody should be allowed to use the sandboxes - that's the point of having sandboxes. Christian75 (talk) 07:32, 17 January 2019 (UTC)[reply]
Just an oversight on my part; fixed. I have raised to protection level of this module and ~/data to match {{Infobox Chinese}}.
@Trappist the monk: I'm currently implementing the mergers with {{Infobox East Asian name}} and found that alternative names aren't supported for Korean and Japanese. Could this be added? I will take a look at implementing it myself, but if you who already understand this template and have done it already for chinese could do it that would be very appreciated. Thanks! --Trialpears (talk) 21:20, 23 September 2019 (UTC)[reply]
Ping did not work. What do you mean by alternative names aren't supported for Korean and Japanese?
{{infobox Chinese
|title=Appropriate title text
|lang1=txg
|lang-content1=txg content
|lang-hdr1=Header text for Tangut
|lang-ipa1=ipa text
|lang-rom1=romanized text
|lang-std1=romanization label
|lang-lit1=literal translation
}}
Could any language lover advised me how to replace the plain-text column "Romanization" with [[Romanization of Wu Chinese|Wu romanization]] for the language wuu (Wu Chinese)? For example, see the transcription section of the Template:Infobox Chinese on the right. -- love.wh09:27, 6 August 2021 (UTC)[reply]
It tags the Zhuang language text in this font. Test the article, Nanning. I see that, Namzningz is written in basic Latin alphabet, therefore, it is very unnecessary, and if it should still be, then a class must be included to allow us to change (nullify) the choice of the font.