Strict Standards: Declaration of SkinTJP::initPage() should be compatible with SkinTemplate::initPage(OutputPage $out) in /var/www/ on line 0 Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /var/www/ on line 1349 Talk:WagaWiki Policies - WagaWiki

Talk:WagaWiki Policies

From WagaWiki

Jump to: navigation, search

Use of Ruby tag

As you probably know the Ruby tag is used in HTML to display Furigana however it is not natively supported by many browsers (including the popular Firefox). Words with proper ruby tags will display like ...


on Firefox. The two questions are 1) Is that 'better' than just not giving the reading 食べます or does the bracketted text distract? and 2) Should WagaWiki have a policy on using / not using ruby?

This is a good point. I added ruby tags to Expressing and/or in Japanese recently, because it was really cool in IE, where the furigana would be properly rendered.
It is one of the few things that I'm jealous of IE users about ;-) I wish somebody would implement Ruby properly in Firefox.Paul b
You know about the Ruby Support Extension? (since loading can be slow, native support in Firefox would be better, but until then...)--Richvh 13:06, 31 August 2006 (EDT)
Yeah I know about it - but until there is native support in Firefox I don't think I can recommend using the tag in wiki pages. We can't tell people to "just get the extension" before they read our pages.
However, having all those brackets does slow down reading for someone who already knows the reading of the kanji in question. I do, however, believe that there are some cases where it is better to have the brackets (e.g. introductory lessons).
In the really introductory lessons there is full romaji available. I tend to use little kanji in the sentences themselves but sometimes include vocabulary lists where there are kanji.Paul b
And in some cases (such as the Keigo page), it is best to leave them out entirely. As such, it might not be appropriate to institute a wiki-wide policy regarding use of ruby tags, but rather take it on a case-by-case basis, depending on the nature of the article.
Another option would be to include a completely kana version of the text afterward, like this:
or this:
Any other opinions? Vega12 03:24, 19 August 2006 (EDT)
Footnotes and a vocabulary list may be better for intermediate lessons. That way people have a chance to try to read it in kanji without having it given away by the furigana / yomikata. I tried footnotes once but the instructions I followed from WikiPedia didn't work. Paul b
After more thought, I believe that for lessons the best way would be to have vocabulary lists, as it will make people less lazy when it comes to reading kanji. As for other pages, it will probably be best to just leave kanji as is. If there is a kanji that is too difficult for the material the page is covering, then just leave it in kana, provide a translation for it, or come up with an example that doesn't use it. Vega12 18:27, 20 August 2006 (EDT)
I'll have another go at getting footnotes to work sometime. Paul b
Personal tools