View source for Wiki143 talk:Manual of Style/China- and Chinese-related articles

{{talk header|search=no|wp=yes|noarchive=yes|WT:MOSCHINA}}
{{WikiProjectBannerShell|1=
{{WikiProject Manual of Style}}
{{WikiProject Asia}}
{{WikiProject China}}
{{WikiProject Hong Kong}}
{{WikiProject Macau}}
{{WikiProject Malaysia}}
{{WikiProject Singapore}}
{{WikiProject Taiwan}}
}}
{{User:MiszaBot/config
| algo                = old(180d)
| archive             = Wikipedia talk:Manual of Style/China- and Chinese-related articles/Archive %(counter)d
| counter             = 8
| maxarchivesize      = 200K
| archiveheader       = {{Automatic archive navigator}}
| minthreadstoarchive = 1
| minthreadsleft      = 6
}}
{{Archives|auto=short|bot=lowercase sigmabot III|age=180|1=
* [[/Archive 1]] (Jun 2005–Jul 2007)
* [[/Archive 2]] (Jul 2007–Aug 2007)
* [[/Archive 3]] (Aug 2007–Mar 2008)
* [[/Archive 4]] (May 2008–Oct 2011)
* [[/Archive 5]] (Feb 2012–Sep 2014)
* [[/Archive 6]] (Sep 2014–Feb 2020)
* [[/Archive 7]] (Feb 2020–2021)
* [[/Archive 8]] (2022– )
}}

== Template:ill ==

[[Template:ill]] does a reasonable job for most languages at providing sister language links for redlinked terms on en.wp. For Chinese, I find it totally useless, in every case worse than just including the native characters with no link to zh.wp at all. It creates a redlinked romanised term whilst completely hiding the characters: hover or long press displays the zh.wp url with the characters' unicode codepoints escaped for url compatibility, so if I want to know what / whom the redlink is supposed to indicate, I have to leave the website to a different Wikipedia, which feels like very bad design.{{pb}}My method is usually linking the characters to zh.wp, but I know this isn't shared by everyone. Sometimes alternatively I'll just add the characters in {{tl|lang-zh}} or similar following the transclusion of {{tl|ill}}, although this feels inelegant.{{pb}}What are people's thoughts on this? Should we provide any MOS guidance about it? [[User:Folly Mox|Folly Mox]] ([[User talk:Folly Mox|talk]]) 10:28, 3 July 2024 (UTC)

:I know nothing about template design or url compatibility, but this doesn’t seem to happen to me. When I hover over an {{tl|ill}} link to a Chinese page, Wikipedia displays the characters. 
:Is the issue browser-specific? If so, perhaps there’s a technical fix for this? Personally, I like how using {{tl|ill}} cleans up the running English text. It’d be a shame to have to create call-outs for topics that already have a Chinese-language article. [[User:SilverStar54|SilverStar54]] ([[User talk:SilverStar54|talk]]) 17:08, 3 July 2024 (UTC)
::Oh right, I've been meaning to get back to this. It turns out this does seem to be browser specific. Fails in Firefox and DuckDuckGo, but displays in Chrome.{{pb}}I kind of see the utility of this the other way round, though: a substantially higher proportion of readership is going to be interested in knowing the word for something / name of someone than the proportion who might click through to the sister language project to read about the topic in another language (which is likely a strict subset of the first).{{pb}}In other words, displaying the graphs for the native name is what I see as the higher priority, and the link to zh.wp I see as a low-priority convenience thing. [[User:Folly Mox|Folly Mox]] ([[User talk:Folly Mox|talk]]) 13:43, 6 July 2024 (UTC)
::I suppose we could do something like: {{tt|<nowiki>Lao Laizi ({{ill|Lao Laizi|zh|老萊子|lt=老萊子}})</nowiki>}}
::Which renders as: {{xt|Lao Laizi ({{ill|Lao Laizi|zh|老萊子|lt=老萊子}})}}
::This doesn't feel better than {{xt|Lao Laizi ({{zhi|[[:zh:老萊子|老萊子]]}})}}, although the code for that is less clear:
::{{tt|<nowiki>Lao Laizi ({{zhi|[[:zh:老萊子|老萊子]]}})</nowiki>}}
::[[User:Folly Mox|Folly Mox]] ([[User talk:Folly Mox|talk]]) 13:54, 6 July 2024 (UTC)
:@[[User:Folly Mox|Folly Mox]] I am not sure I follow. I tell my Chinese students (and Koreans) to use ill, see activity here: [[User:Hanyangprofessor2/Module/MoS]] (I'll be refining it in the future). Sample article by my students using Ill: [[Iron flower]]. What's wrong with it and how would you make it better? Note I tell my students to do a red link and add Chinese charas in the parenthesis if they cannot locate the zh wiki article for the notable concept that should be linked, but if there is one, ill works well enough. Why do we need do display the non-Latin characters for something that has an article? (additionally, today's digital literacy includes machine translating stuff in browsers, so any competent internet user who clicks on ill and goes to zh wiki should be able to read zh article with two mouse clicks). <sub style="border:1px solid #228B22;padding:1px;">[[User:Piotrus|Piotr Konieczny aka Prokonsul Piotrus]]&#124;[[User talk:Piotrus|<span style="color:#7CFC00;background:#006400;"> reply here</span>]]</sub> 14:21, 9 July 2024 (UTC)
::I guess my perspective is that if I'm reading about a Chinese topic, and come across a transliterated name or translated title I'm not familiar with, I want to know its name. That's the basic piece of information I look for to determine whether or not I'm familiar with the topic and whether I want to read more about it.{{pb}} Being unable to see the names of things in English language topic area sources is something that deeply bothers me, to the point where I'll discontinue reading a book or article if the native terms are not provided, and I don't want that experience for myself or anyone else whilst reading Wikipedia. Granted our case is different, because we can click through to a zh.wp article with {{tl|ill}}, so we're not cutting people off from looking more deeply into a topic should they wish to, but not having the information present on the page is something that upsets my pedagogical sensibilities.{{pb}}It does look like I hold something of a minority opinion here, and about half my concerns would be alleviated if I switched browsers, so I'm fine with not saying anything in guidance about this. I do think that it should be {{xt|permitted}} to retain characters where {{tl|ill}} produces a redlink locally, and people shouldn't remove them just because {{tl|ill}} is present, but no further guidance seems necessary. [[User:Folly Mox|Folly Mox]] ([[User talk:Folly Mox|talk]]) 14:16, 11 July 2024 (UTC)
:::I see. I am not opposed to your example of Lao Laizi (老萊子 [zh]) although I am not sure it is necessary given the link. I most often use this template for Polish Wikipedia, and occasionally Polish words are different and even use diacritics, but unless they have been used in English works, I think we don't need the reader to know them. For Chinese and such, they are even more useless, as readers cannot read (pronouce) or memorize the characters. I certainly see the need to use them when no link is present, to allow people to research them, but otherwise... shrug; as I said, I am not opposing your idea because while I feel displaying the characters when zh link is present is IMHO not needed, WP:NOTPAPER, so why not. <sub style="border:1px solid #228B22;padding:1px;">[[User:Piotrus|Piotr Konieczny aka Prokonsul Piotrus]]&#124;[[User talk:Piotrus|<span style="color:#7CFC00;background:#006400;"> reply here</span>]]</sub> 12:02, 12 July 2024 (UTC)

== Infobox Chinese + other infobox redundancies ==

Many general-use infoboxes have a {{para|native_name}} parameter somewhere. Would it be worth specifying that listing the same native forms in both {{tlx|Infobox Chinese}} and an article's primary infobox is redundant and usually undesirable?

Moreover, the use of {{tlx|Infobox royalty}} in the Chinese context has been killing me: I'm not even sure I would remove the native form conventionally placed right at the top ({{cf.}}[[Kangxi Emperor]] or any other emperor), but I'm leaning towards that being ideal if we're not even making {{para|native_name}} a proper parameter for that one. [[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:00, 13 July 2024 (UTC)

:Is it redundant and undesirable? I really like the native names of subjects being visible on the first screen, before scrolling down. It makes a lot of sense to have the name at the top of the article, since a lot of people will be looking for that. I'd go as far as saying that if we were to remove either the native name or transliterated name from the header of {{tl|infobox royalty}}, I'd remove the transliterated name, since it already introduces the lead sentence, and leave only the native name, but having both looks correct to me.{{pb}}{{tl|Infobox Chinese}} is a separate matter entirely. In my experience, it mostly exists to shove diacritic pinyin out of the prose, and then gradually become increasingly bloated with pronunciations. Most of this information seems crufty at first glance, although doubtless it's useful to someone, and removing pronunciations from people's own minority topolect probably feels like a personal affront. Removing the characters from this infobox would leave us without an "index item" (not a good term, sorry about my brain) to compare the pronunciations against. I suppose the characters could be moved to the bottom, if we're concerned about increasing the distance between appearances of the same terms.{{pb}}I think I'm more pro–"sprinkle 漢字 throughout" than most. Someone in a thread somewhere above called Chinese characters something like {{tqq|unavoidable}}; I'd call them {{tqq|desirable}}. Our educational value is significantly enhanced by including them where they're not too obtrusive. [[User:Folly Mox|Folly Mox]] ([[User talk:Folly Mox|talk]]) 00:24, 14 July 2024 (UTC)
::I really do think the {{tlx|Infobox royalty}} case is plausible—I just wish it was its own parameter.
::I think the reason my particular opinions are what as strong as they are—{{small|maybe "ductile" is a better word? I like having deep justifications for opinions on these things, as long as I'm willing to uproot them and change my mind, as happens often}}—because I start as an editor with desiring a parsimony of data, i.e. within reason every piece of information appears in the specific place for it. Of course, this  doesn't always align with what's good for readers or even other editors, which is why I appreciate the pushback when I lead myself to overly dogmatic positions. [[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>]] 00:56, 14 July 2024 (UTC)

:::What if we created a wrapper template? And by {{tqq|we}} I'm not really volunteering myself because I don't have any background coding templates here and am not really sure where to look for guidance, but as a hypothesis:{{pb}}We could create a template that wrapped {{tl|Infobox royalty}} or {{tl|Infobox officeholder}} and bundled {{tl|Infobox Chinese}} underneath? I'm not sure if that's technically possible or if we'd have to wrap the first template and just output the second based on input parameters.{{pb}}But the idea would be that the native name goes up top, then the main infobox, then pronunciations at the bottom, without duplicating the native name. Or, if that's impossible to do, create a single template that doesn't wrap anything, but accepts all the parameters of {{tl|Infobox royalty}}, {{tl|Infobox officeholder}}, and {{tl|Infobox Chinese}}, and spits out a single box for every applicable biography? [[User:Folly Mox|Folly Mox]] ([[User talk:Folly Mox|talk]]) 11:04, 14 July 2024 (UTC)

::::I guess before we commit to any such mad undertaking, I'd like to hear from other people active on this talkpage whether the duplication of characters between two infoboxes bothers them.{{pb}}I definitely used to have a similar idea about how often information should be repeated (never), which came from a background in database programming. That was before the adult-onset ADHD. Now I'm a person who keeps copies of everything important in at least three places, because chances are one is lost and I've probably forgotten another on the way somewhere. I forget what's at the top of the first infobox by the time I've scrolled down to the second paragraph of the lead section.{{pb}}Mainspace (and projectspace, now that I think of it) hugely duplicate information across a broad array of related pages, and I've come round to a position of inelegant and messy convenience: if someone is looking for information in a place, might as well put it there too, irrespective of wherever else it already is. This is just my opinion as an editor, though, not a firmly held belief. [[User:Folly Mox|Folly Mox]] ([[User talk:Folly Mox|talk]]) 11:04, 14 July 2024 (UTC)

:::Note that {{tl|infobox royalty}} has {{para|module}}, which can contain {{tlx|infobox Chinese|child=yes}}, which bundles it at the bottom, whereas {{para|native_lang_name}} would go at the top. (e.g: [[Michael Nylan]], with a diffent infobox) [[User talk:Kanguole|Kanguole]] 11:34, 14 July 2024 (UTC)
::::Thank you for the technical insights (and for creating that article; I always wanted her to have one, since I cite her all the time, but never got round to it).{{pb}}Maybe if people are bothered by the duplication of characters, we could either get consensus to add {{para|native_name}} to the top of Infoboxen {{tt|royalty}} and {{tt|officeholder}}, then {{para|module|Infobox Chinese}} them and remove the {{para|c}} from the child templates. Or construct a wrapper that does the same if consensus to change the widely used templates cannot be achieved. [[User:Folly Mox|Folly Mox]] ([[User talk:Folly Mox|talk]]) 13:44, 14 July 2024 (UTC)

== `Infobox sinogram`? ==

I've had the idea of creating a derivative of {{tlx|Infobox grapheme}} specialized for characters for a while now. Use would likely be relatively niche, i.e. when a character is itself the subject of encyclopedic analysis while not running afoul of [[WP:NOTADICTIONARY]], like on [[Dao]]. Any thoughts? [[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>]] 21:44, 30 July 2024 (UTC)

== What should generally be included in the articles for emperors? ==

Also kicking this one off since it's probably of interest to several people floating around lately.
# We currently use {{tlx|Infobox royalty}} for the lead, which has some specific niceties for Chinese emperors built in. I'm not convinced the template really needs changing at this moment, but naturally there's historically been an impulse to stuff these way past the function of an infobox. Specifically, I don't think there's any justification for including the Chinese calendar reckoning for dates of birth etc, as has often been added. Maybe some loose consensus could be made about this?
# At the bottom of articles, there's usually a fairly bespoke nesting list showing every descendant an Emperor is associated with that someone decided to write down. It seems fairly trivial to me that it's always [[WP:UNDUE]] to this degree, and there would be very few cases where non-notable figures with no historiographical content whatsoever should be mentioned even once.
[[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>]] 06:07, 31 July 2024 (UTC)

:I think the date reckoning stuff came about because there was a fairly high profile calendar conversion tool active till the end of the 2010s or so, and it was (and, often, still remains) easier to source vital dates and accession dates in Chinese sources then do the conversion, than to find a source that supported the dates using a Western calendar.{{pb}}Genealogical information has been an area of cruft expansion due in part to the organisational schemata of official histories. The most recent thread on my usertalk, a tangent from an AFD, touches on this as well.{{pb}}I have to go and don't have time right now to engage on substance, but I did want to provide my impression on where these informal conventions came from. [[User:Folly Mox|Folly Mox]] ([[User talk:Folly Mox|talk]]) 11:15, 31 July 2024 (UTC)

== Why here "China" not "mainland China" ==

{{difftext|when editing articles concerning China, Taiwan, Hong Kong, Macau|when editing articles concerning mainland China, Taiwan, Hong Kong, Macau}}{{quote|(I)t should (only) be used when a distinction with Hong Kong, Macau, or Taiwan is required.|[[WP:NC-CN]]}} [[User:Donttellu8|Donttellu8]] ([[User talk:Donttellu8|talk]]) 16:30, 7 September 2024 (UTC)

:Because that would sound strange, and we still probably need to specify HK + MO for some. <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> 20:41, 7 September 2024 (UTC)

== Converting full-width punctuation and currency symbols in horizontal text ==

Greetings! Over the past few years, there have been no objections to converting Latin letters and Arabic numerals to ASCII from their full-width forms when they appear in horizontal Chinese, Korean, or Japanese text. I've raised it on MOS and Wikiproject talk pages and made many cleanup edits to articles. I'm making a push to finish that cleanup, and I've been noticing that punctuation, currency symbols, and spaces have the same problem. It looks weird to have the full-width versions mixed in, and they sometimes leak into English-language text. My plan was to start converting punctuation and currency symbols in horizontal text (except where the characters themselves are being discussed) when the July 1 database dump becomes available in a week or two. If you have any questions, objections, concerns, or suggestions, please let me know! Open-circle full stop is not included; the affected characters are: {{char|＂ ＃ ＄ ％ ＆ ＇ ＊ ＋ － ／ ＠ ＼ ＾ ＿ ｀ ￠ ￥ ￦ ＜ ＝ ＞ ｜ ￤}} and the space character. -- [[User:Beland|Beland]] ([[User talk:Beland|talk]]) 17:51, 29 June 2024 (UTC)

:Will the areas targetted include {{tag|blockquote|o}}, {{para|quote}}, etc? Or will direct quotes be avoided and only article prose affected? [[User:Folly Mox|Folly Mox]] ([[User talk:Folly Mox|talk]]) 21:16, 29 June 2024 (UTC)
::I think this advice should be presented with caution, as fullwidth punctuation doesn't fit all the time. Otherwise I don't see the problem.
::{{midsize|{{My OR}} Tangentially, I think I'm the only one outside both the W3C and East Asia that knows one can specify CSS lengths in units of {{code|ic}} as well as {{code|px}} and {{code|em}}—with {{code|1ic}} equal to the width of a fullwidth character for practical purposes, [https://developer.mozilla.org/en-US/docs/Web/CSS/length#ic and more technically] {{xt|equal to the used advance measure of the "水" glyph (CJK water ideograph, U+6C34), found in the font used to render it.}} I think that means it's equal to the <em>height</em> of {{xt|水}} instead when the text is being rendered vertically, neat. Can't figure out what {{code|ic}} stands for though, other than that {{code|i}} is probably "ideograph".}} [[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>]] 21:34, 29 June 2024 (UTC)
:::Did you have specific wording in mind for "with caution"? I'm not sure what you mean by "fullwidth punctuation doesn't fit all the time", as that would be what we are getting rid of. Did you have an example or two in mind? Just trying to make these suggestions actionable. -- [[User:Beland|Beland]] ([[User talk:Beland|talk]]) 22:32, 29 June 2024 (UTC)
::::Oh, I was thinking of Anglo-style halfwidth quote marks {{xtn|“⋯”}}, which aren't always appropriate to swap out with fullwidth corner brackets {{xtn|「⋯」}}. [[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>]] 00:43, 30 June 2024 (UTC)
:::::Curvy quotes like {{char|“}} and {{char|”}} are prohibited by [[MOS:STRAIGHT]]; both those and full-width {{char|＂}} would get converted to ASCII {{char|"}}. Corner brackets don't have a direct ASCII equivalent, so I did not put them on the list of affected characters, and they would be left alone. -- [[User:Beland|Beland]] ([[User talk:Beland|talk]]) 00:52, 30 June 2024 (UTC)
::::::This is the only bit that low key concerns me. The glyphs I care most about preserving (，,：,。,「」,、,（）,！,？) are not in the list of affected punctuation. I'm well aware of [[MOS:CURLY]], but I find that the default ascii straight double quote is easily lost in a string of Chinese characters, and does a very poor job of marking out the quoted material.{{pb}}But, this might be my eyesight, and I suppose if we find ascii-width double quotes getting lost after the punctuation changes, we can replace them with the permissible 「」. [[User:Folly Mox|Folly Mox]] ([[User talk:Folly Mox|talk]]) 14:05, 30 June 2024 (UTC)
:::::::That sounds like an elegant solution. -- [[User:Beland|Beland]] ([[User talk:Beland|talk]]) 19:35, 30 June 2024 (UTC)
::My practice has been and would continue to be to change formatting of direct quotations, because [[MOS:CONFORM]] says to change quotation marks, dashes, ligatures, etc., to match Wikipedia house style. -- [[User:Beland|Beland]] ([[User talk:Beland|talk]]) 22:30, 29 June 2024 (UTC)
:::{{ping|Beland}} I've unarchived this—somehow having missed its conclusion for months on end, and that's on me. If this is seen as an exception to [[WP:CONFORM]], then to me it's one with very clear reasoning behind it—the impetus behind [[MOS:CONFORM]] doesn't naturally extend to requiring the awkward mingling of full width and half width text. I don't disagree with specifics about curly quotes here, but I must reiterate that generally it is simply a different situation, because we're dealing with snippets of a qualitatively different writing environment than almost all others. <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> 17:09, 11 March 2025 (UTC)
::::Hmm, these punctuation characters occur in CJK contexts both inside and outside of quotations. I think it would look typographically sloppy to have the full-width versions inside quotations and the ASCII versions outside quotations. If we decide this is undesirable "awkward mingling" then it would make sense to use fullwidth forms consistently. So far the consensus across Chinese, Japanese, and Koreak WikiProjects seems to have been that the upsides of easier searching and whatnot outweigh the downside of some people not liking the appearance. Using fullwidth-only in CJK contexts would also require not matching quoted and cited sources, as the ASCII characters commonly appear in CJK language text, including in professional publications. -- [[User:Beland|Beland]] ([[User talk:Beland|talk]]) 18:00, 11 March 2025 (UTC)
:::::Searching isn't a point I hadn't considered deeply. I should note that much of the time search algorithms in web browsers etc. are smart enough to alias characters together—e.g. {{key|Ctrl+F}} for {{code|。}} here in Firefox matches every Unicode full stop code point unless I check a box (that says "match diacritics", a bit silly but understandable why that is). I think it's especially worth considering the incongruence with pre-20th century anything—while I understand Chinese punctuation as we use it is largely a 20th-century invention, it's an invention often adapted to older texts. The use of inverted commas where a Literary Chinese passage may generally be typeset to use 「」 is simply distractingly wrong to me—to the point of seeming unintentionally mangled or sloppy. I don't know, I'm obviously a bit more uptight than most on this, but. (I also need to get some rest, so apologies if you got a particularly disheveled response here.) <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> 18:10, 11 March 2025 (UTC)
::::::As noted above, {{char|。}} and {{char|「」}} are not on the conversion list, and other editors support using {{char|「」}} where you feel the visual appearance would justify it. -- [[User:Beland|Beland]] ([[User talk:Beland|talk]]) 18:19, 11 March 2025 (UTC)