Dear Mike
Two things - the free answer pronunciation test - the four boxes that appear for the pinyin: on WM machines the box isn't big enough to hold the 7 characters that can make up a pinyin pronunciation (E.g. zhuang4) instead just showing the first 6 characters.
Also, about stroke orders again - it seems that the Taiwanese/traditional stroke orders are different for some parts of characters. If you remember, I was talking about the 或 part of 國 before. Please check this page from the R.O.C. Ministry of Education and this suggests that these characters are written to a slightly different stroke order. http://www.edu.tw/files/site_content/M0 ... 4.htm?open So, perhaps the traditional stroke order data isn't as buggy as was thought (although I found only one that was definitely wrong - 禮).
Obviously, depending on how you've implemented it, there could be a simple solution in allowing the selection of one or other of the stroke order diagrams (assuming you have two sets of complete data and the traditional set isn't a sub-set) based upon how a test has been set up and if referred to from the dictionary, based on whether the simplified or traditional character option has been selected. Just now, when traditional is selected, you seem to have a mix and match of the simplified and the traditional character stroke order diagrams. Whereas when simplified is selected, it just sticks with the simplified set. Because I study traditional, I keep getting marked wrong for changing my basic methods of writing from one way and then wrong again, and so it's a bit frustrating. There seem to be quite a few characters that differ in the stroke order for the parts that they are composed of.
If you haven't implemented it with two mapped sets of stroke order diagrams for the unicode characters that look the same in both simplified and traditional rendering, then it's probably a bit of a bugger of a job to correct.
Just in case it makes a difference, I set up my stroke order testing flashcards using Ryan Kellogg's 5000 character files at viewtopic.php?f=7&t=1674 and these were mapped to the unihan dictionary. Perhaps there's a way of forcing simplified/traditional at the import stage and perhaps that's where my mixed traditional/simplified character problem has arisen from???
Best
Ben
Two things - the free answer pronunciation test - the four boxes that appear for the pinyin: on WM machines the box isn't big enough to hold the 7 characters that can make up a pinyin pronunciation (E.g. zhuang4) instead just showing the first 6 characters.
Also, about stroke orders again - it seems that the Taiwanese/traditional stroke orders are different for some parts of characters. If you remember, I was talking about the 或 part of 國 before. Please check this page from the R.O.C. Ministry of Education and this suggests that these characters are written to a slightly different stroke order. http://www.edu.tw/files/site_content/M0 ... 4.htm?open So, perhaps the traditional stroke order data isn't as buggy as was thought (although I found only one that was definitely wrong - 禮).
Obviously, depending on how you've implemented it, there could be a simple solution in allowing the selection of one or other of the stroke order diagrams (assuming you have two sets of complete data and the traditional set isn't a sub-set) based upon how a test has been set up and if referred to from the dictionary, based on whether the simplified or traditional character option has been selected. Just now, when traditional is selected, you seem to have a mix and match of the simplified and the traditional character stroke order diagrams. Whereas when simplified is selected, it just sticks with the simplified set. Because I study traditional, I keep getting marked wrong for changing my basic methods of writing from one way and then wrong again, and so it's a bit frustrating. There seem to be quite a few characters that differ in the stroke order for the parts that they are composed of.
If you haven't implemented it with two mapped sets of stroke order diagrams for the unicode characters that look the same in both simplified and traditional rendering, then it's probably a bit of a bugger of a job to correct.
Just in case it makes a difference, I set up my stroke order testing flashcards using Ryan Kellogg's 5000 character files at viewtopic.php?f=7&t=1674 and these were mapped to the unihan dictionary. Perhaps there's a way of forcing simplified/traditional at the import stage and perhaps that's where my mixed traditional/simplified character problem has arisen from???
Best
Ben