Bulbapedia talk:Manual of style/Kanji

From Bulbapedia, the community-driven Pokémon encyclopedia.
Jump to navigationJump to search

Tooltip usage

Although I have been personally responsible for using {{tt}} a lot, I believe we should cease using it altogether. For starters, the mobile version of Bulbapedia, like Wikipedia's equivalent, does not support it, and it's not possible nor practical for users of touch devices to even trigger the tooltips, much less read their contents. As to furigana, Ruby text is an alternative but it unfortunately lacks support from most browser vendors. However, this shouldn't technically be an issue here since we already use the nonstandard APNG format, which is only natively supported by Firefox and Safari (Presto-based Opera did support it but it was discontinued). SatoMew 23:42, 23 December 2014 (UTC)

While my comment is not agreeing nor disagreeing, I do have to play the Devil's Advocate here. How would you handle things like connecting locations from Kanto Route 24 (at right)? In each generation, the way Routes 24 and 25 connect differs, with that upper left corner sometimes being part of 24, and sometimes being part of 25. It would perhaps be possible to use version tags like I've been using in the TM/HM template (such as, for example, TM94 Rock SmashXY, but there might be so many necessary that it would make the pane messy and perhaps too large. It might be worth creating the partial page and playing with it to see how it looks. CycloneGU (talk) 00:19, 24 December 2014 (UTC)
It's obviously a complicated decision. Alternatives to current usage of the template must be tested in the userspace. On an slightly unrelated note, another issue with the mobile version of the site is that our custom templates break in one way or the other. While the wiki shouldn't lose its identity ({{Bulba color}} is one of its characteristic elements, for example), I believe we should return to standard MediaWiki templates, tables, etc. Not only it will simplify things but scaling them for mobile devices will be much less of an issue. I understand that they look pretty and what not but the site should first and foremost focus on the information and accessibility. And when is HTTPS support coming, guys? SatoMew 00:41, 24 December 2014 (UTC)
I can agree with that statement, doing things to make it pretty can be things that eventually break it in some places. Possibly unrelated, but "Leer (move)|Leer" and "m|Leer" provide the exact same result (see Leer and Leer). I still type Wikilinks the long way if I don't know a shortcut, and because I'm used to typing them like that. And I do agree for my part that standard templates should be the norm.
Going back to my example, I don't think it's possible to add the {sup} templates without also changing where the text goes "going to some weird place instead of "Kanto Route 25"). It can append the superscript correctly, but screws up the link. That was the problem I was having trying to do just that example then. CycloneGU (talk) 00:54, 24 December 2014 (UTC)
First, we should try to keep this discussion to just "tt" for now. Your proposal for that, SatoMew2, is already bordering on tangential to this page's topic; let's not venture completely out of reasonable bounds. If you want to discuss wider mobile issues, you should find a better place.
I would think removing "tt" entirely wouldn't be very practical, for such reasons as CycloneGU mentions. More importantly, though, I think that it would be more valuable for someone to actually try to develop alternatives than for us/anyone to just argue abstractly. Take a large survey of "tt" usage on this site, and show examples of alternate solutions so people can argue over whether it's worth it for all parties involved (mobile users and non-mobile users). Tiddlywinks (talk) 01:00, 24 December 2014 (UTC)
I'm not discussing general mobile issues here, it was just to point out other issues similar to the ones caused by {{tt}}.
I believe that a solution to the problem that CycloneGU mentioned would be to separate the information for each different generation in the template. And it is already an issue right now because you have links overlapping the tooltip asterisks. SatoMew 01:08, 24 December 2014 (UTC)