This feature is great for typo catching, but at the moment it sometimes calls valid pinyin invalid. I answered 接着 with jie4zhe (correct is jie1zhe or jie1zhe5) and it blocked the answer as invalid pinyin, when it should have just been an incorrect answer with valid pinyin. There is some sort of issue with the way 5th tone/no tone is validated.
1 Like
You would be correct 
the way it currently works is to first check if there is a number attached to each pinyin. If there isn’t, then it refuses – the only exception is that previously we allowed omitting the fifth tone for answers. For these cases, we check if that’s the answer first before stepping through the validation process.
We wanted to continue to support omitting the fifth tone, but now when someone omits a number, was it intentional or was it a flub? I figure the solution was to mark it as correct if it wasn’t a flub, otherwise guard against it when it’s wrong. It does allow for a little “cheating” though.
1 Like