in which a user of Jisho.org are confused by the shared parts of 内 and 肉, which makes them wonder if "a third word with 3 人 in its kanji character" (sic.) exists or not.
Overall TODO
1. Use Unicode instead of characters to display RADKFILE encodings.
Rationale:
Referencing RADKFILE's official website by EDRDG group at Monash University: http://www.edrdg.org/krad/kradinf.html, quote: "Where the element alone is not in JIS X 0208, a kanji which contains the element is used instead.". This means radical such as 草 should contain 艸(⺾), instead of 艾.
On EDRDG's website they referenced WWWJDIC, which used image to represent these radicals:
I believe Tangolin's approach suits this sites more, and that most, if not all computer supports Unicode nowadays.
Test, can you see these characters? -> 氵扌幺⺾
2. Change the name of RADKFILE breakdown from "parts" to sth. better or remove it completely.
Rationale:
"parts" can be misinterpreted that the kanji itself contains those radicals, as seen in the said Stackexchange question, where as according to RADKFILE's website they have only intend to assist lookup service only, never intend to imply any kind of constituent breakdown, or any etymological implication.
Currently, it seems the site does contains a better breakdown radicals as shown in this image:
The breakdown display can be compared with the previous images, in which on can see that the "parts" section can be considered problematic (艸 or ⺾ vs 艾). If it is renamed to "RADKFILE breakdown" or "RADK search aid" or "RADK code" it might help prevent such confusion. Alternatively, it can be hidden completely, only using RADKFILE for searching, which is their only intended use.
This is intended to be a tracking ticket, or be tagged for any similar discussions.
Knowing that your team are not professionals, I really do appreciate your work! I can see how the feature can be useful for learners, despite the minor "incorrectness".
Personally, since I understand Kanjis natively, I might not have to same needs of learners whose mother tongue is English.
I have also never used Jisho.org so I am not sure any other related functions has to be changed, and the difficulty of it.
So please help forward this issue to anyplace where it is best to make the maintainers or user to be aware of it.
If this is best done outside of Github, since I won't use Jisho.org feel free to just do that on my behalf, many thanks!
I only intend to follow the ticket on Github.
Hi maintainers:
Background
This tickets spawns from discussion in this Japanese Stackexchange question: https://japanese.stackexchange.com/questions/104823/内-uchi-肉-niku-is-there-a-third-word-with-3-人-in-its-kanji/104833#104833
in which a user of Jisho.org are confused by the shared parts of 内 and 肉, which makes them wonder if "a third word with 3 人 in its kanji character" (sic.) exists or not.
Overall TODO
1. Use Unicode instead of characters to display RADKFILE encodings.
Rationale: Referencing RADKFILE's official website by EDRDG group at Monash University: http://www.edrdg.org/krad/kradinf.html, quote: "Where the element alone is not in JIS X 0208, a kanji which contains the element is used instead.". This means radical such as 草 should contain 艸(⺾), instead of 艾.
On EDRDG's website they referenced WWWJDIC, which used image to represent these radicals:
Ben Bullock's website used a more aesthetically pleasing representation:
Tangolin uses unicode:
I believe Tangolin's approach suits this sites more, and that most, if not all computer supports Unicode nowadays. Test, can you see these characters? -> 氵扌幺⺾
2. Change the name of RADKFILE breakdown from "parts" to sth. better or remove it completely.
Rationale: "parts" can be misinterpreted that the kanji itself contains those radicals, as seen in the said Stackexchange question, where as according to RADKFILE's website they have only intend to assist lookup service only, never intend to imply any kind of constituent breakdown, or any etymological implication.
Currently, it seems the site does contains a better breakdown radicals as shown in this image:
The breakdown display can be compared with the previous images, in which on can see that the "parts" section can be considered problematic (艸 or ⺾ vs 艾). If it is renamed to "RADKFILE breakdown" or "RADK search aid" or "RADK code" it might help prevent such confusion. Alternatively, it can be hidden completely, only using RADKFILE for searching, which is their only intended use.
This is intended to be a tracking ticket, or be tagged for any similar discussions.
Knowing that your team are not professionals, I really do appreciate your work! I can see how the feature can be useful for learners, despite the minor "incorrectness".
Personally, since I understand Kanjis natively, I might not have to same needs of learners whose mother tongue is English. I have also never used Jisho.org so I am not sure any other related functions has to be changed, and the difficulty of it. So please help forward this issue to anyplace where it is best to make the maintainers or user to be aware of it.
If this is best done outside of Github, since I won't use Jisho.org feel free to just do that on my behalf, many thanks! I only intend to follow the ticket on Github.