Hi!
In the simplified course I belive there is a typo in 老板. It is using the traditional version of the character “闆” instead of the simplified version if I’m understanding correctly.
This is in the example sentences for the word 摸鱼
Hi!
In the simplified course I belive there is a typo in 老板. It is using the traditional version of the character “闆” instead of the simplified version if I’m understanding correctly.
This is in the example sentences for the word 摸鱼
Thanks for the report! I’ll fix it up sometime this week before the next curriculum update.
Hi, Kevin. I noticed the same issue in other words. Maybe we can use this thread to post all the issues that we find to make it more practical to report the same issue?
Are you talking about using 闆 instead of 板 in the example sentences of other words? Those will also be fixed in the next update. (The root issue was in some of our curriculum processing code, so all instances of this particular error will be fixed next time we issue an update.)
I mean traditional character being used in the example sentences instead of simplified. I remember seeing this issue for 只 and 制
Yeah, there are some limitations in the current way we do traditional<->simplified character remapping in our curriculum processing pipeline. I think I found a solution and will work on it tomorrow to see if I can eliminate these final stragglers.
Pasting any ones you find in this thread can help me make sure I’m getting everything.
For 只, are you referring to instances where 隻 is showing instead?
That is correct! One instance that I noticed was for the word 看到. I will post more as I come across them.
The 制 one is foun in 手工, for example.
I manually went through and manually added any missing simplified ↔ traditional character mapping pairs as well as adding a suite of tests to make sure only simplified character show up in simplified character examples going forward. This fixed a couple hundred different sentences across our simplified curriculum!
I’ll be issuing a curriculum update in the next hour or so to publish these changes.
Thanks again to both of you for letting me know about these bugs.
Good job! Glad to help.