Template talk:Sign

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


How to use

Sign design!

Sign design!

Sign design!

Sign design!

Sign design!

Speech bubble design!

Battle dialogue design!

Pokémon Diamond and Pearl
City sign design!

Twinleaf Town Sign Map.png

Pokémon Diamond and Pearl
City map sign design!

Pokémon Diamond and Pearl
Route sign design!

Pokémon Diamond and Pearl
Trainer tip sign design!

Pokémon Black and White
Sign design!

Pokémon Black and White
Building sign design!

First of all, since the sign designs differ from game to game, put the version:
RBY = Red, Blue and Yellow
GSC = Gold, Silver and Crystal
RS = Ruby and Sapphire
E = Emerald
FRLG = FireRed and LeafGreen
FRLGspeech = FireRed and LeafGreen speech bubble design
FRLGbattle = FireRed and LeafGreen battle dialogue design
DPcity = Diamond and Pearl city sign design (grey)
DPcitymap = Diamond and Pearl city map sign design (brown)
DProute = Diamond and Pearl route sign design (green)
DPtip = Diamond and Pearl Trainer Tip sign design (blue)
BW = Black and White
BWbuilding = Black and White buildings

{{sign| DPcitymap |

Then out of the following:

Header, always put this first:


For city/town signs with a map, include this next, providing only the full name of the city/town (eg. Twinleaf Town, with the space), and the image will be displayed if it exists (image name should then be NAME_Sign_Map.png):

{{sign|DPcitymap|map| full name of city/town (with capitals and any spaces) }}

Then comes the content, add the title parameter to put a bolded title:

{{sign|DPcitymap|title| put title here }}
{{sign|DPcitymap| put text here }}
{{sign|DPcitymap| put text here (will add a new line) }}
{{sign|DPcitymap| put text here (will add a new line) }}

After everything, close with footer:



A better way to present stuff written on signs, notices, and perhaps even Trainer Tips soon etc. Will be adding the designs for other versions later.

Please post here for suggestions or before changing it in any way.    -–<×vVvvv τλικ to ς1tHςι3r ^^vVv×>–- 15:09, 11 January 2009 (UTC)

What about fonts? ht14 03:06, 12 January 2009 (UTC)
If you mean displaying the sign text with the font used in the game, unfortunately that would depend on whether or not the font is installed on the server, and whether or not the browser used to view can read that font. In my opinion, it would be best to keep it to the default font for the moment. Though I did find a script collection of the fonts used in RSE and FRLG here.     -–<×vVvvv τλικ to ς1tHςι3r ^^vVv×>–- 05:28, 12 January 2009 (UTC)

New designs

Yessir, they have arrived. The sign designs for Emerald and FireRed/LeafGreen! They're as close to the real as I could get them. Also, map images are able to be added to the Diamond/Pearl city map signs. I will be personally uploading all the map images when I get to them, then adding them to the appropriate articles.     -–<×vVvvv τλικ to ς1tHςι3r ^^vVv×>–- 09:25, 13 January 2009 (UTC)

I added the RBY design. OK? I think we can't get the little Poké balls at the corners...

[Greets, mewX (TALK)] 21:03, 9 April 2009 (UTC) 

Japanese specific variants for Generation III text box

Would it be possible to add the Japanese variants of the text box from the Generation III games? It's because in the Japanese versions of RSEFRLG, the borders are wider and it would be nice to replicate that difference, IMO. One example of where it would be useful is the Faraway Island article. SatoMew 13:57, 11 April 2012 (UTC)


It is transcluded on over 250 pages. Probably should be protected. --Abcboy (talk) 23:01, 12 October 2012 (UTC)

FRLG speech bubble is causing vertical lines to appear along the page in Apple iPad Safari. --Abcboy (talk) 19:17, 2 November 2012 (UTC)

Protection and Request

Can someone please protect this template. Also, I would like to request to add signs for B2W2 and XY. --Cinday123 (Talk) 11:03, 14 March 2014 (UTC)

Aren't BW2 signs exactly the same as BW? Also, this page hasn't been vandalized so there doesn't seem to be a reason to protect it. Protected for autoconfirmed users is the best thing to do, if it gets protected at all. The reason I say this is because I highly doubt that the admins want to do all the signs, and most editors on this page aren't admins. I'd have to check the X and Y signs, but I believe they fade into the background near the edges, which could be a problem. I don't think MediaWiki supports translucency minus for shadows and images. Pikachu Bros. (talk) 17:19, 14 March 2014 (UTC)
I think it will be okay to leave this unprotected for now. If anyone knows how to make the XY signs, feel free to add them. If not, we can try to get it added in the near future. --Pokemaster97 21:18, 14 March 2014 (UTC)

Suggesting a replacement

The look of our HTML <pre> tag could be updated to something like this. This would replace this template altogether and allow for a consistent look of quotes from the games (and perhaps other texts). Doing this is particularly relevant given the mobile version of the site (in which this template is broken) and the lack of Generation VI designs.

This is how the <pre> tag looks right now here:
SatoMew 01:04, 3 January 2015 (UTC)

XYORAS signs

If this template isn't going to be replaced or deprecated anytime soon, we need Generation VI signs. Here are some I've made:

Pokémon X and Y
Speech bubble design!

Pokémon X and Y
Message design!

Pokémon Omega Ruby and Alpha Sapphire
Sign design!

Pokémon Omega Ruby and Alpha Sapphire
Speech bubble design!

Pokémon Omega Ruby and Alpha Sapphire
Message design!

Please tell me if anything breaks in any browser (particularly the shadow in in the XY speech bubble). Colors could also use some improvement, so if you have any suggestions, reply below. --Abcboy (talk) 04:35, 18 July 2015 (UTC)

Everything looks nice to me in Firefox, including the shadows.
On a bit of a tangent, I think the design of this template (both the code and the way it has to be used on articles) is so terrible that, even if this template isn't immediately deprecated, it would still be best (if at all possible) to put those Gen VI signs into a new template of their own instead of incorporating them here. That should be simple enough, but I've previously separated the signs for each Gen into individual templates such as User:Tiddlywinks/Sign/4 (as well as 1, 3, and 5; see also usage) if examples will help. Tiddlywinks (talk) 05:11, 18 July 2015 (UTC)
It would probably be better to have a separate template for each style of sign, rather then by generation. Also, I'm not sure as to the benefits of a title parameter if it could be manually bolded on the page anyways. Additionally, if you put <ab> tags around the generic text parameter, you won't have to manually enter <br> tags. --Abcboy (talk) 07:13, 18 July 2015 (UTC)
Do you mean there should be one template for each combination of generation+style, or there's one template for each style and a parameter dictates the generation? The latter would kind of be a weird idea. If the former, though, there are pros and cons either way. The main downside to separating each Gen by style as well is that oftentimes you'll end up duplicating code (which, I don't know, maybe shouldn't be a concern here).
With the "ab" tags, do you mean to use it within the template or in the template call ? (I feel like I've tried the former before and it didn't work like I hoped. I'm also aware of the latter, and probably was, but if so I couldn't tell you whether I had a good reason to use "br".)
As for the title, you're pretty much right, that's probably mostly personal preference/style for me. Tiddlywinks (talk) 07:45, 18 July 2015 (UTC)
One template for each of the weird random colorful signs. There's no real reason to have {{Sign/4|DPcitymap| if you could just as easily have {{Sign/DPcitymap. It's one less switch, and one less parameter.
It should work in the template itself. I'd have to try to see why it wouldn't. The most likely reason would probably be that it doesn't work in templates due to it being a weird extension, but I think it would be worth it to try it out. --Abcboy (talk) 17:15, 18 July 2015 (UTC)
I meant to look it up before but I forgot. Anyway, I did try it once upon a time here but I removed it, which should mean it didn't work. Though I didn't record it explicitly, I'm sure that I wanted to include it there if I could; but since I couldn't, I resolved to highlight "ab" tags in the documentation later. You're welcome of course to test it yourself. Tiddlywinks (talk) 17:56, 18 July 2015 (UTC)
The problem is that the miscellaneous parser hooks are parsed prior to the substitution of template parameters. That would certainly explain your above results, and why template parameters can't be fed to <ab>. Of course, you can still use <ab> when calling the template. --Abcboy (talk) 23:16, 18 July 2015 (UTC)
I've found a solution. If you use {{#tag: ab|blah}}, you get the same results as if you called it the normal way (<ab>blah</ab>). I've tested it here. --Abcboy (talk) 01:10, 29 July 2015 (UTC)