Why does the right side radical strokes order  are different than alone?

  • This is the stroke order I expect for : kakijun.jp/page/kkto16200.html There might be a story behind different stroke orders, or it might be an error--I don't know.
    – user1478
    Commented Aug 9, 2013 at 20:21
  • @snailboat that's the order I expected too, is the page wrong? I asked because that page and "imi wa?" app whhave the same stroke order for 踵. Doing some research, both are based on KanjiVG project maybe a bug? Commented Aug 9, 2013 at 20:23
  • I can't say for sure. Any large project like KanjiVG is sure to have a few errors here and there, though. Their web page says to report errors via GitHub issues, but the link isn't loading for me right now. If you do report it to them, I'm sure they'll be able to figure out whether or not it's an error.
    – user1478
    Commented Aug 9, 2013 at 20:48

1 Answer 1


There are sometimes more than one acceptable stroke order. The Japanese wikipedia article on stroke order mentions that there is not always a single correct stroke order - some kanji have two or more which are commonly used, and also sometimes the stroke order changes when writing 行書{ぎょうしょ}. In 1958, the Ministry of Education in Japan published a document which showed stroke orders for the then 881 kanji on the 'education' list:


That is, one stroke order per character was given for teaching, but that did not mean that stroke orders which had been used in the past should be considered incorrect.

For 踵 specifically, I don't think there is an 'official' determination in Japan on how it should be written, although I agree it would be normal to follow the stroke order for 重.

It may be that some of the stroke orders on that site are taken from Chinese sources, where there are official guidelines for more characters. For example, here is an official Taiwanese source (Ministry of Education) which uses the same one as you link.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .