Moderators: Moderator Team, Admin Team
JohnCBriggs wrote:Jasonさん,
The benefits of ruby characters are clear enough that they are a common feature of many published book both for young native Japanese and Japanese language learners. I have even seen furigana used for katakana characters in children's books. This is presumably because the children don't know katakana well. Furigana is widely used in the Japanese For Busy People series.
As for the crutch aspect, I don't really buy the argument here. I assume JPOD is already holding back on the use of kanji. So the kanji version of the transcripts are not written at the full adult level. We are already working on a sliding scale of complexity in the writing style, and furigana can be used in much the same way. For simpler kanji, the furigana can be ommited.
In fact, rather than simply being a crutch for kanji we should not, furigana can be used to introduce new kanji to the student. I think that for some of the complex kanji JPOD has simply written it in hiragana to avoid complexity. That is the real crutch.
Another way furigana could be used is to only present the furigana for the first occurance of a kanji in an article. This is how it is used in Japanese For Busy People. The first time they use a kanji on a page, it has furigana. After that it is omitted.
One more point, the furigana is so small, if at all possible, the reader will avoid using it.
Honestly the mixture of kanji-ban and hiragana-ban is really cumbersome. There should be a single transcript with ruby characters as needed.
Regarding the browser issue, since IE supports ruby characters, that is about 79.8% of the browser market right away. Firefox has a plug-in so that is about another 13.7%. So I think Ruby characters are here to stay.
I think there should be an attempt to incorporate ruby characters into new lower intermediate and intermediate lessons.
John