About ruby, compatibility is the major flaw. but I suppose we can do something with CSS. Yata Talk to me 04:58, J(UTC)Ībout tabbers, is there a particular reason why you suggest them? What's wrong about using normal sections? I don't really like the style. Majority seems contend with tabbers, right? So what about ruby? Having the pronunciation on top of the respective kanji/phrase seems favorable, to indicate how Oda wanted the term to be pronounced. Yup, tabbers do help organize the page's physical appearance. And didn't the toaru majutsu no index wiki have extra brackets that even without the installed add-on, the brackets would still be visible? Making it both ways? Yata Talk to me 01:13, J(UTC)
Furigana is the pronunciation intended, such as "pistoru", while the kanji is simply to make Japanese readers more understanding in case the attack name is written in another language (hence the furigana is necessary to pronounce the original meaning). I meant the Yu-Gi-Oh wiki as the second example. The wiki must be as much compatible as possible.
CORNER TABBER INSTALL
Also, I guess that extension won't work on mobile devices (since you can't install it). We have to assume that the viewer hasn't installed the extension, otherwise we will only cause confusion. As I said, simply because you have to install an external add-on it should be avoided, unless we can come up with a format which will still be correct when viewed without the extension, for example: 銃 (ピストル) = 銃(ピストル). I wanted to know more about what the furigana is and what we are currently using. My opinion would be different if the ruby feature was available by default in all major browsers, but as things stand I agree with Levi. The Index wiki also did a terrible job of advertising that the ruby extension was needed, so even though I've visited it fairly regularly in the last couple of months, I had no idea that the feature was available, which is something we have to keep in mind - how many people are we going to expect will install the add-on? If it's less than half of everyone who visits the wiki, then it's definitely not worth doing (presumably we'd be removing the katakana from the side to the top and not doubling up, so people without the add-on installed would no longer be able to read it at all). It looks alright, although a little hard to read without zooming in on the text (maybe I'm just tired and my eyes are blurring). This and this wiki utilizes such format, looks nice. we know that the furigana refers to "pistol" instead of "Gomu Gomu no Pistol"). The second point is having the furigana on top of the kanji, so we know how each kanji is pronounced, as pposed to having the whole phrase (i.e. Also, it's easy to say "set a bot to do that", but you have to come up with an algorithm to do that.
Though if there are no issues with viewing 銃ピストル then it shouldn't be a problem, I don't really understand how it works. The wiki should compatible as much as possible with every kind of viewer and browser. About your second point, can you explain better what the problem is about? But simply because you have to install and addon to view them is pretty much a no in my opinion.I'm not against using tabbers in special pages, but I don't really like them on normal articles, because I don't see a problem in not using them and they are also poorly styled.