Hi guys, I think this character probably should change it Pinyin to zhu4 and it corresponded meaning, since it will have a much larger vocabulary associated with it.
谢谢大师。
Hi guys, I think this character probably should change it Pinyin to zhu4 and it corresponded meaning, since it will have a much larger vocabulary associated with it.
2 Likes
Agreed! Since this character in simplified pretty much only refers to zhu4 in relation to knowledge and writing.
1 Like
This one is a bit tricky and on our radar. We even have a couple page long internal documentation page about this specific character when we were trying to brainstorm solutions on how to handle it.
Basically most of our internal data is “traditional first” and we map it over to simplified via a bunch of complicated machinery and data files. This almost always works, because simplified characters are, well, a “simplified” subset of traditional characters.
However, the one exception are the characters 著 and 着. For Traditional characters, a single character 著 is used to represent both the zhe5 “continuing” and the zhu4 “write” meaning! In simplified Chinese, these two meanings are split out into 著 zhu4 and 着 zhe5. This exception to the rule doesn’t (currently) fit into our current data structures and pipelines.
Anyway, thanks for bringing it up. I went back and looked through the internal write-up we had and I think we have some good ways of dealing with this. The solution we previously settled on is not complicated on the technical side, so I think we can proceed with it soon. I can see us tackling this in the next month or two. 
1 Like