Template talk:Tt

Is this how we should provide Japanese and the Japanese translation from now on? I mean, outside of episode titles, but just any Japanese? x.x; --Greengiant 13:33, 24 Apr 2005 (UTC)

Only when cramped for space, or for text flow reasons. You can use this for anything appropriate, for instance, abbreviations, if you want. - 振霖_T 13:38, 24 Apr 2005 (UTC)

For minor translations?

I think this could be used, for example, to show the "literal translations" of Pokémon moves (or similar things) from other languages, which are not important enough to actually be part of the article paragraphs. Is this idea okay? --Johans 19:42, 11 August 2007 (UTC)

Code

At the end of the coding, it says [[pt:Predefinição:Tt]]. What's that for? LEVEL X _{Talk to me!} 08:03, 17 May 2009 (UTC)

That's the Portuguese version of this template. --Łӑпçε123 08:15, 17 May 2009 (UTC)

in de it exist a simmilar template de:template:tt --Hanmac

Cursor change

because of what does the cursor change to a "?" in the de wiki i cannot repoduce this thing --Hanmac 08:21, 24 July 2009 (UTC)

The span class "explain". If it doesn't work on Deutschpedia, then it may have been disabled. Best you can do is contact a server admin and get it set up, unless there's another method of calling this that I am unaware of. —darklordtrom 08:30, 24 July 2009 (UTC)

I used the coding you have on our site, and the question mark showed up. Must be something with your server or something. —darklordtrom 08:35, 24 July 2009 (UTC)

It should be noted

Putting any " in either parameter breaks it. See. --SnorlaxMonster 12:20, 7 September 2010 (UTC)

and then there's the edit button Ataro 12:28, 7 September 2010 (UTC)

I don't understand. If you are suggesting I add it to the template, it's protected. --SnorlaxMonster 12:48, 7 September 2010 (UTC)

I'll make a note of this. Although putting " in the first parameter still works. —darklordtrom 22:45, 7 September 2010 (UTC)

Just dump nowiki around {{{2}}} in the template. It should work fine. ~ solaris 22:48, 7 September 2010 (UTC)

There's also ". —darklordtrom 22:53, 7 September 2010 (UTC)

We could also put nowiki tags on the second parameter in the template, as you can't put any working wikicode in there anyway. --SnorlaxMonster 07:35, 8 September 2010 (UTC)

errors

change {{wp|http://en.wikipedia.org/wiki/List_of_XML_and_HTML_character_entity_references|html entity}} to {{wp|List of XML and HTML character entity references|html entity}}

and add a link to [[de:Vorlage:Tt]]

--Hanmac 09:08, 8 September 2010 (UTC)

Phones

there is a problem with the usage of tt for mobile and tablet users, can there be done something?

seemingly, the PokeWiki (German version of bulbapedia) does it with this CSS "hack"

@media screen {

.tt_for_handy {

display: none;

}

}

@media handheld {

.tt_for_handy {

display: inline !important;

}

}

and this as the template itself:

<span class="explain" title="{{{2}}}" lang="{{{lang|}}}" xml:lang="{{{lang|}}}" style="color: #{{{3|}}};border-bottom:dotted 1px;{{{style|}}}">{{{1}}}</span><span class="tt_for_handy"> ({{{2}}})</span>

before anyone asks "handy" is the pseudo German word for mobile phone.

My1 03:50, 8 January 2015 (UTC)

Android and iOS aren't covered by @media handheld, because they decided that they should be treated like screens rather than handhelds. Honestly, that's not a viable solution. --Abcboy (talk) 15:27, 2 May 2015 (UTC)

Delete

Tooltips are an awful way of presenting secondary information or notes. They also don't work in touch devices that well. Instead, we should use the reference tag and a section called "Notes". For furigana, we should use Ruby text. SatoMew 15:12, 1 May 2015 (UTC)

well I dont think they are bad. Furigana are okay but because since Gen5 we got Kanji and then we technically would have to write Kanji, Kana, and Romaji to be perfect and complex ruby isnt that widely supported... for Mobile Devices I already posted a working approach the German Pokewiki uses and that works splendidly. My1

We actually don't worry about romaji much of the time.

It should be said that reference tags are not a perfect solution. "tt" lets you (on devices that aren't solely touch-based) read something inline, whereas a notes section would require you to skip back and forth around the page.

If anything, I would prefer to suggest something like the annotations on the XKCD What if? site, which are clickable (i.e., touch-friendly). This too has problems, though, as it appears they default to displayed if javascript is blocked, meaning they cover up parts of nearby text.

I guess in short, while I'm not sure what the code My1 posted above results in exactly, it may be the best solution. Tiddlywinks (talk) 16:17, 1 May 2015 (UTC)

http://pokewiki.de/Template:Tt here's the demo on the Pokewiki. in short everything is displayed in brackets after the text, so if you have "Bisasam", it would display as "Bisasam (Bulbasaur)". My1 18:38, 1 May 2015 (UTC)

Replacing this template is simply impossible. There are countless legitimate uses of the template, which cannot be replaced. In regards to Ruby text, I suggested it, but it doesn't work correctly in Firefox so it is not going to be implemented. --SnorlaxMonster 07:26, 2 May 2015 (UTC)

Sorry to barge in the discussion, but I seen that Template:Ruby isn't protected yet. I know it is not used anymore, but old or unused templates must be protected, right? And yes, I also disagree with the deletion. I more often use my iPad than my computer, and my iPad supports Japanese text, while my computer not. --~~ThePokémonFanSince1995~~-- 08:11, 2 May 2015 (UTC)

Firefox was recently updated to support Ruby text so it being incompatible is no longer a valid reason against us using it. SatoMew2 (talk) 16:01, 13 May 2015 (UTC)

Nested spans, or ruby annotations?

Hi, it looks like this template is often used to put translations in a title attribute. That is, the span's content is a different language from surrounding content, and the span's title attribute is a different language from the span's content. The template doesn't have any way to generate lang attributes, however. This is discouraged; see W3C's lang attribute FAQ.

This can be fixed with nested spans, similar to W3C's example, but I noticed a few editors last year suggested switching to ruby annotations instead. That sounds like a good idea. Title attributes were popular in MediaWiki's early days, before iPhones and Android existed, but a third of web traffic (and growing) is on touchscreens now, and that part of MediaWiki is showing its age.

One snag, though: caniuse.com says Opera Mini doesn't support ruby. Are there any Opera Mini users around who can check ruby rendering? Do you at least get the rp fallback? ライケン(Rigel Kent) (talk) 12:29, 9 June 2016 (UTC)