General Discussion

Shaggy said:
Also, was there a particular reason that {{edit}} requires the user to enter the template name? I tested out this code, and it didn't fail:
Code:
<div style="float:left;width:3.4em;text-align:left;padding:0 0 0 0.3em">[<span class="plainlinks">[{{fullurl:{{{1|{{FULLPAGENAMEE}}}}}|action=edit}} edit]</span>]</div>
but eh... It's too minor now.
Because it returns the URL of the page you are viewing, not the template it is located in.
 
Yeah, exactly: once the template got transposed, it all broke down since then it'd use whatever page it was on as the page name. I tried for quite a while to get it to automate properly, but in the end, manually adding the names was unavoidable.

Lakituthequick said:
Digging this up because there is a neat function in MediaWiki that may get this consistent; using "{{int:edit}}" in place of the word "edit" in {{Template:Edit}} will transclude the word in the language of the viewing user, just like how show/hide does.

int-edit.png


It does capitalize the word "edit" though, though consistency between languages tends to be funny. "text-transform: lowercase" could fix that though.

Whether you use this is up to you, it's there.
Very nifty: I'm all for adding that (with the "text-transform: lowercase").
 
Walkazo said:
Yeah, exactly: once the template got transposed, it all broke down since then it'd use whatever page it was on as the page name. I tried for quite a while to get it to automate properly, but in the end, manually adding the names was unavoidable.

Lakituthequick said:
Digging this up because there is a neat function in MediaWiki that may get this consistent; using "{{int:edit}}" in place of the word "edit" in {{Template:Edit}} will transclude the word in the language of the viewing user, just like how show/hide does.

int-edit.png


It does capitalize the word "edit" though, though consistency between languages tends to be funny. "text-transform: lowercase" could fix that though.

Whether you use this is up to you, it's there.
Very nifty: I'm all for adding that (with the "text-transform: lowercase").
Neat.

Also, the toggle switch is capitalized in every language except for English (because MediaWiki:Collapsible-collapse exists somewhy, original is at /en (MediaWiki:Collapsible-collapse/en)), you'll probably want to lowercase that as well (CSS class is "mw-collapsible-toggle").
 
Actually, some other languages have it lowercase already (e.g. French (including French-Canadian), Hungarian, Bokmål, Russian), while Canadian/British English weirdly have it uppercase "Expand"/"Collapse" instead of "show"/"hide".

Pretty weird, and a pain, but I don't want to have to change the classes of over 400 nav templates (plus dozens more infoboxes) for such a superfluous reason. Taking a simple measure to make the {{edit}} capitalization consistent with the majority of users' preferences, and with the capitalization of "edit" in the tabs and headers, makes sense, but for the toggle, I feel like most folks probably don't notice or care anyway, so it's not worth us bending over backwards for it (it helps that there's a lot of space and more writing between them, minimizing the impact, whereas if they were side-by-side, there'd probably be more attention given).
 
Walkazo said:
Actually, some other languages have it lowercase already (e.g. French (including French-Canadian), Hungarian, Bokmål, Russian), while Canadian/British English weirdly have it uppercase "Expand"/"Collapse" instead of "show"/"hide".
Oh hey, yeah, it is inconsistent. The Expand vs. show is explained by this page (MediaWiki:Collapsible-collapse), Porplemontage has edited it to say 'show' instead of 'Expand'.

Walkazo said:
Pretty weird, and a pain, but I don't want to have to change the classes of over 400 nav templates (plus dozens more infoboxes) for such a superfluous reason. Taking a simple measure to make the {{edit}} capitalization consistent with the majority of users' preferences, and with the capitalization of "edit" in the tabs and headers, makes sense, but for the toggle, I feel like most folks probably don't notice or care anyway, so it's not worth us bending over backwards for it (it helps that there's a lot of space and more writing between them, minimizing the impact, whereas if they were side-by-side, there'd probably be more attention given).
That's not what I meant at all, actually. What I mean is that the toggle has a CSS class of "mw-collapsible-toggle", which can be targeted at with the lowercase rule from CSS. The toggle is inserted via JavaScript anyway, so its code is not editable on any of the templates.
 
Niiue said:
Time Turner said:
Niiue said:
Can someone with one of the English SMW2/SMA3 guides tell me if this is mentioned at all?
Any ideas on which levels it appears in?

There's one at the end of Watch Out For Lakitu, right before the goal roulette.

There's also an underground area full of them in GO! GO! MARIO!!.
In those levels, neither guide mentions them in any capacity, not even with "a Shy Guy" or "that enemy". It also isn't listed in SMW2's comprehensive list of enemies (126 (File:SMW2 Guide 126.jpg), 127 (File:SMW2 Guide 127.jpg), 128 (File:SMW2 Guide 128.jpg)) as far as I can tell, though perhaps I glossed over it.