Template talk:Han char

Definition from Wiktionary, the free dictionary
Jump to: navigation, search

Template for Han character section[edit]

This is used under the Han character header, in the Translingual section of the entry for a single Han character, which precedes the language sections. It adds the character to Category:Han characters in radical/stroke sort order (then by Unicode order).

Usage: {{Han char|parameters}}

All parameters are named:

  • alt= alternate form(s)
  • rad= single character radical
  • rn= radical number
  • as= additional strokes. This must be a two digit number for the radical/stroke sorting to work in Category:Han characters! So 3 additional strokes is "03".
  • asj=additional strokes in Japanese
  • sn= stroke number (total) Three here is "3", not "03".
  • so= stroke order, image width should be 40px times the number of characters shown, no caption[1]
  • four= four corner system
  • canj= Canji input
  • ids= IDS composition sequence
  • gso= graphical significance and origin[1]
  • cmean= common meaning[1]


These are all from the information loaded by "NanshuBot". The idea is that some of them will change/go away/be represented differently. These changes can be made with the template in some cases; even when a bot is required, it can find the template instance and operate on it.

  • alt= is usually used for simplified/traditional Chinese. But not always. Might take manual fix.[1]
  • gso= should become Etymology, but this probably takes manual edits in all cases[1]

The template uses 2-column format; this was just done to make the first pass easy.

  1. 1.0 1.1 1.2 1.3 1.4 parameter proposed but not used


This shows using the seal and bronze script images from Commons, as well as the stroke order image from Commons; these are available for a number of characters.

[[Image:字-bronze.svg|thumb|70px|[[w:bronze script|Bronze]]]]
[[Image:字-seal.svg|thumb|70px|[[w:seal script|Seal]]]]
From [[宀]] roof + [[子]] child.  Root meaning: to give birth.  [[子]] also serves as a phonetic element.
===Han character===
{{Han char|alt=|rad=子|rn=39|as=03|sn=6|so=[[Image:字-bw.png|280px]]|four=3040<sub>7</sub>|canj=十弓木 (JND)
|gso=|cmean=[[letter]], [[character]], [[word]]}}

(see ) which looks like:



From roof + child. Root meaning: to give birth. also serves as a phonetic element.

Han character[edit]

  • Radical 39 + stroke: 子+03
  • Stroke count: 6
  • Four-corner system: 30407
  • Cangjie input: 十弓木 (JND)
  • Common meaning: letter, character, word
Stroke order


visual appearance of template[edit]

Can this template be worked on? The layout, in two columns, is confusing and unattractive. Badagnani 09:57, 24 October 2006 (UTC)

Well, I kind of like it the way it is ... ;-) But yes, of course; the layout is just a simple first pass; the idea is that the template can be improved. I just used top2/mid2 etc as a starting point. What did you have in mind? Robert Ullmann 12:00, 24 October 2006 (UTC)

Well, good job creating the template (though I'm not sure how it improves on the previous system, which I'm now quite used to). The main thing is that one has to look over to the right for the normal meaning. It seems that everything should be in one column unless it's a single section that's being broken up (as with "translations," that are broken into columns to save space). Also, the columns are showing up in different widths, especially if there's a long URL in the left column. Badagnani 22:37, 24 October 2006 (UTC)

This new arrangement seems better, with important info kept on the left. The only thing I see on the right is the Unihan, which seems to tie in with what's on the left. Badagnani 04:25, 27 October 2006 (UTC)

Oh, I notice that the "Graphical Significance and Origin" field doesn't appear. I think it's important that this remain as a blank field in all the hanzi entries so that knowledgeable editors may add this eventually for each character. If the blank field isn't there, editors may not know to add it. Badagnani 04:28, 27 October 2006 (UTC)

(I was going to ask what you thought ...) I hadn't played with the Han ref template again yet, I'm wondering if there are other sources besides Unihan we could point to. (The problem being that most aren't as comprehensive.)
gso is moved to Etymology (where it belongs) if not blank. Someone adding this information should be adding an Etymology section, not adding gso to the template. And I think you underestimate editors, anyone knowledgeable about etymologies who has worked with the wikt even a little bit will see what is missing! Robert Ullmann 11:35, 27 October 2006 (UTC)

Personally, I think the etymology should be moved to be a subsection of the han character section. Is that okay? Habemus 17:38, 22 February 2009 (UTC)


May I open a discussion about expansions of the template? I suggest the following:

  1. categorization: The category:Han characters comprises 21461 elements; a bit crowded. From my work with Chinese characters I would prefer an own category for the 214 radicals, with all radical variants it may be about 270 which is an amount giving a better overview. Either the radicals are only in category:Han character radicals (a subcategory of category:Han characters), or they occur redundantly in both (which I think better).
  2. variations: When a radical has also variations, it could be distinguished between the main radical and its variations, by setting a new parameter e.g. var=0 if one of the 214 main radicals. Variations may get var=1, var=2 and so on, the number depending on Unicode codepoint ascending order.
  3. commonscat: In the Commons, any image of a chinese character has either an own category which is linked to the Wiktionary character article, or the character has not an own category but is linked itself to the Wiktionary. This is a fine option to look for the characters specifications. Another fine thing would be to link each Wiktionary radical to its Commons category (since not each Wiktionary character has an image at the Commons, I restrict for the moment on radicals).
    This link is established since recently from the 214 articles Index:Chinese radical/...

Because such a link might need frequent maintenance – at least during its developement stage – the best thing would be to solve that by a sub-template, that is invoked only in the ~270 cases when additional strokes are zero, e.g. {{#ifeq:{{{as|}}}|00|{{Han rad|{{{rad}}}|{{{rn}}}|{{{var|}}}}}}} (passing character, radical number and the variation distinguisher var whether it exists, or not). Of course that template can care for category:Han character radicals.

Your opinion? -- sarang사랑 14:05, 17 April 2012 (UTC)

This is a good idea. :) I will let one of our more template-savvy editors comment on the technical details. - -sche (discuss) 20:54, 17 April 2012 (UTC)
Your agreement enjoys me. When everything about is discussed, I can continue and create an empty template {{Han rad}} or another accepted name, so the authorized template-savvy can insert the string above. This done, further discussions my come up about the sub-templates layout. I have my ideas for that and will then discuss them on the sub-templates talk page. -- sarang사랑 05:45, 18 April 2012 (UTC)
Well, no-one has commented here with any concerns, so I've unprotected this template, so you can improve it. :) If you need me to unprotect any other templates so you can lower them, let me know. - -sche (discuss) 02:28, 23 April 2012 (UTC)


The suggested expansion, for linking to the Commons category, is now inserted. For the details, see the documentation of {{Han rad}}.

A large number of transclusions happen with insufficient parameters. To find and repair them, the contained maintenance category Category:Chinese terms needing attention is expanded too, and provided with the pages in error and their error type (a, n, q, s); for the details, see the category. Of course, the category should always kept empty. -- sarang사랑 16:47, 24 April 2012 (UTC)

Characters with multiple possible IDS descriptions[edit]

There seems to be characters that can have different representations in IDS due to Han unification (like (G:⿰虫单 J, K:⿰虫単) or (G, K:⿰甬攴 T:⿰甬攵)). Is there a way to handle this? (Is this the right place to discuss this?) —umbreon126 06:59, 8 November 2014 (UTC)