Thread:Sarutobii2/@comment-27797856-20160416151047/@comment-1251315-20160416152440

It is  impossible  to do what you are asking. The ruby tag only supports that one format, I cannot make something that extends the capacity of HTML directly in the way you want it: if you wish for something that better supports the Ruby format you want, then you need to go and contact the W3C developers, they make the HTML Specification and created that tag.

From my understanding, there's very little purpose in the Furigana content anyway, since we use Romaji as a translation of the Kanji/Kana that is taken from the series, which explains how to say / read the word. Furigana is apparently only used to help explain how to read Japanese text, which is useless when we're using Romaji as a translation of Kanji/Kana.

Ruby was added directly into the translation template by UltimateSupreme on NP. Seelentau himself said that it was redundant and not very necessary, for the reason I gave above (which is based on Tau's reasoning).

We could use title tags like Tau had suggested, but as UltimateSupreme notes, it doesn't work on all devices such as mobile, and I'd prefer the wiki to be easily readable on all devices, rather than just desktop systems. There's also the fact that Japanese characters do not always register properly because you need a browser/system that supports that encoding format and not all browsers/systems support it properly.

Although it was added to the template on NP, I've not yet seen you complain about the limited usage it's had there, so it's a little odd that you'd complain about its usage here and not at NP, when the ruby text is used in exactly the same manner as here.

Just my 2c on this. Let's not start any issues, as Gou is away today and I don't really want to deal with anything here in his absence.