Difference between revisions of "Template talk:Hat Nav"

From Team Fortress Wiki
Jump to: navigation, search
m
(Category: Hats: new section)
Line 8: Line 8:
 
: I have a copy of the HatNav with capitalisation.  All that's needed is the capitalised versions of all the hats to be moved to the non-capitalised ones before I implement it.  I see you're getting on with some of that now, I'll help you. --[[User:RJackson|RJackson]] 03:56, 1 July 2010 (UTC)
 
: I have a copy of the HatNav with capitalisation.  All that's needed is the capitalised versions of all the hats to be moved to the non-capitalised ones before I implement it.  I see you're getting on with some of that now, I'll help you. --[[User:RJackson|RJackson]] 03:56, 1 July 2010 (UTC)
 
::It seems consensus has been reach to change to proper capitalisation. Previously the policy was different to keep consistency. Feel free to update this template. -- [[User:Pilk|Pilk]] <sub>([[User talk:Pilk|talk]])</sub> 04:01, 1 July 2010 (UTC)
 
::It seems consensus has been reach to change to proper capitalisation. Previously the policy was different to keep consistency. Feel free to update this template. -- [[User:Pilk|Pilk]] <sub>([[User talk:Pilk|talk]])</sub> 04:01, 1 July 2010 (UTC)
 +
 +
== Category: Hats ==
 +
 +
Currently the template includes [[:Category:Hats]] on every page it is transcluded in. While this is, for the most part, a good thing, there are a number of miscellaneous items where including Cat:Hats is probably a bad thing, as they are not hats. It's been a while since I've used parserfunctions, and I'm a little rusty with them, but I believe something like the below would not include Cat:Hats if the parameter category was passed to the template args, and was not blank? I guess it could be expanded so that if the category parameter is passed then the value of the category parameter '''is''' the name of the category included, but I cant remember how the switch statements worked either.
 +
<pre>{{#if:{{{category|}}}|<includeonly>{{lang cat|Hats}}</includeonly>|}}</pre>
 +
 +
In other words, could someone a little more experienced check it over before I go causing havok? Cheers. [[User:Lamb|Lamb]] 22:08, 2 October 2010 (UTC)

Revision as of 22:08, 2 October 2010

Capitalization

Needs proper capitalization for names of hats. They're proper nouns. Words after the first one deserve a capital letter.

--Mhmm 03:40, 1 July 2010 (UTC)

No. -- Smashman... (ts) 03:47, 1 July 2010 (UTC)
I have a copy of the HatNav with capitalisation. All that's needed is the capitalised versions of all the hats to be moved to the non-capitalised ones before I implement it. I see you're getting on with some of that now, I'll help you. --RJackson 03:56, 1 July 2010 (UTC)
It seems consensus has been reach to change to proper capitalisation. Previously the policy was different to keep consistency. Feel free to update this template. -- Pilk (talk) 04:01, 1 July 2010 (UTC)

Category: Hats

Currently the template includes Category:Hats on every page it is transcluded in. While this is, for the most part, a good thing, there are a number of miscellaneous items where including Cat:Hats is probably a bad thing, as they are not hats. It's been a while since I've used parserfunctions, and I'm a little rusty with them, but I believe something like the below would not include Cat:Hats if the parameter category was passed to the template args, and was not blank? I guess it could be expanded so that if the category parameter is passed then the value of the category parameter is the name of the category included, but I cant remember how the switch statements worked either.

{{#if:{{{category|}}}|<includeonly>{{lang cat|Hats}}</includeonly>|}}

In other words, could someone a little more experienced check it over before I go causing havok? Cheers. Lamb 22:08, 2 October 2010 (UTC)