Difference between revisions of "Team Fortress Wiki:Discussion"
LiquidFire (talk | contribs) (→{{tl|Backpack item}} improvements (again)) |
(→{{tl|Backpack item}} improvements (again)) |
||
Line 60: | Line 60: | ||
:{{c|Support}} | It would be an extremely good addition to the wiki, if this were implemented. -[[User:NameUser|NameUser]] 22:28, 25 June 2012 (PDT) | :{{c|Support}} | It would be an extremely good addition to the wiki, if this were implemented. -[[User:NameUser|NameUser]] 22:28, 25 June 2012 (PDT) | ||
:{{c|Support}} I don't see why not. It's still perfectly readable and looks better --[[User:LiquidFire|<span style="color:#ff0000;font-weight:bold;">Liquid</span>]] [[User_talk:LiquidFire|<span style="color:#000000;font-weight:bold;">Fire</span>]] [[Special:Contributions/LiquidFire|<span style="color:#808080;font-weight:bold;">@H|H</span>]] 12:36, 26 June 2012 (PDT) | :{{c|Support}} I don't see why not. It's still perfectly readable and looks better --[[User:LiquidFire|<span style="color:#ff0000;font-weight:bold;">Liquid</span>]] [[User_talk:LiquidFire|<span style="color:#000000;font-weight:bold;">Fire</span>]] [[Special:Contributions/LiquidFire|<span style="color:#808080;font-weight:bold;">@H|H</span>]] 12:36, 26 June 2012 (PDT) | ||
+ | :{{c|Support}} This template is ''meant'' to be a reproduction of the in-game thingy (that's why it looks lik the in-game one), so why make a compromise on its fonts when we can make them the same? It's still readable, and it doesn't make any difference to the existing load on my server because all fonts are loaded all the time anyway. — [[User:WindPower|<span style="font-weight:bold;">Wind</span>]] 17:02, 26 June 2012 (PDT) | ||
== How should the "class" taunts pages be improved? == | == How should the "class" taunts pages be improved? == |
Revision as of 00:02, 27 June 2012
|
|
Template:Discussion archives/2012 Template:Discussion archives/2011 Template:Discussion archives/2010
Contents
- 1 Broken external links on Tf Wiki pages
- 2 {{Backpack item}} improvements (again)
- 3 How should the "class" taunts pages be improved?
- 4 Ad media
- 5 Seperate scoreboard page
- 6 Class article galleries are a mess
- 7 The other versions of the killicons
- 8 Paint Style Overlinking
- 9 Translating MediaWiki UI Strings
- 10 Missing images in some browsers
- 11 Those Archive links
Broken external links on Tf Wiki pages
- Everyone who desire to work with this list and fix broken links can do so--FreeXMan Talk | Cont 11:02, 28 May 2012 (PDT)
- What do you mean by fixing? --Enthers. (I find this work intriguing. How about yourself, sir?) 16:24, 7 June 2012 (PDT)
- Finding new versions of old pages, or removing the link if no current version exists. » Cooper Kid (blether) • (contreebs) 20:26, 7 June 2012 (PDT)
{{Backpack item}}
improvements (again)
Since only 4 people chimed in last time.
Old template:
"Le Swag"
Face-Melting Knife - Kills: 1337
Upon a successful backstab you rapidly disguise as your victim
Silent Killer: No attack noise from backstabs
Wearer cannot disguise
New template:
Upon a successful backstab you rapidly disguise as your victim
Silent Killer: No attack noise from backstabs
Wearer cannot disguise
New fonts, consistent colors and font size, blah blah blah. Putin your 2 cents, please. rZ 13:20, 28 May 2012 (PDT)
- Support I like the fact that it is the font and font colour from the game itself. Taser9001 01:16, 29 May 2012 (PDT)
- Snap! 02:28, 29 May 2012 (PDT)
- Against because it is: Better readable <or> More Original ; I think it is better to show it more cleary, instead of a 100% copy of every game aspect. Also in each resolution the size differs, f.e. in low resolutions the wiki also is not good readable... (this has nothing to do with the topic, but i wanted to mention it). TheDoctor 13:38, 31 May 2012 (PDT)
- Against It's not how the graphic looks in-game, so why change it? Also, this text is harder to read than the original. --Enthers. (I find this work intriguing. How about yourself, sir?) 18:59, 6 June 2012 (PDT)
- Actually it is a replica of the in-game appearance. Also it remains readable, which is all that matters. Not how much more- or less-readable it is compared to the old version. If that were the case we would be using White on Black and the Helvetica font to be absolutely maximum readable - however this is obviously not necessary as long as it remains above the baseline of legibility. 18:17, 7 June 2012 (PDT)
- Support I like it. —Moussekateer·talk 21:40, 8 June 2012 (PDT)
- Neutral Not as easy on the eye as I would expect, but I guess it'd be okay. Hm. – Epic Eric (T | C) 13:28, 11 June 2012 (PDT)
- Support It's nice. It synergises with the Wiki really well, as well as strengthening the link between the game and the Wiki itself. 12:18, 14 June 2012 (PDT)
- Neutral The TF2 font is fairly readable, however I'm not sure we should be copying every aspect from the game verbatim when the current font works just fine. As our goal is to communicate information clearly, why should we make it more difficult even if it is only slightly? We should probably get more user input from different TF2 communities as this is a site-wide change, before taking any action (official forums, Facepunch, reddit etc.), to see whether this change would be accepted. Also, as the fonts are hosted by Wind, we'll need his approval as this might increase the load on his server due to this being site-wide. i-ghost 09:28, 15 June 2012 (PDT)
- Support | It would be an extremely good addition to the wiki, if this were implemented. -NameUser 22:28, 25 June 2012 (PDT)
- Support I don't see why not. It's still perfectly readable and looks better --Liquid Fire @H|H 12:36, 26 June 2012 (PDT)
- Support This template is meant to be a reproduction of the in-game thingy (that's why it looks lik the in-game one), so why make a compromise on its fonts when we can make them the same? It's still readable, and it doesn't make any difference to the existing load on my server because all fonts are loaded all the time anyway. — Wind 17:02, 26 June 2012 (PDT)
How should the "class" taunts pages be improved?
So i just saw that the Soldier taunts page lists all taunts, but mostly a link is missing on how the taunts are performed. So i added myself one link to a demonstration video. (Look here) But i thought this way is not that perfect and we need a better way of doing it. Sooo we need a strategy. Suggestions pleaseee, because i have no idea about either a template adjustment to the videos of each taunts(sets) or if there should be seperated movies about it. TheDoctor 10:53, 1 June 2012 (PDT)
- I could conceivably make a script that will composite the frames from hlmv into a video file suitable for upload. I'll make it my next project after the quality database is finished. 10:54, 1 June 2012 (PDT)
- There's no need to have a video demonstration on the taunt pages; the images and text are sufficient for showing what happens during the taunt and the weapon demonstration project shows the taunts too. i-ghost 13:37, 11 June 2012 (PDT)
Ad media
whats with the ad media everywhere? a lot of things are highlighted with ad media. TubbyMonster 20:55, 4 June 2012 (PDT)
- What? The official wiki doesn't use ads, while www.tf2wiki.com (the unofficial one) does. Where are these ads you speak of? — Xenak (Talk|Contribs) 20:56, 4 June 2012 (PDT)
...ok maybe its just my computer but things are highlighted in green and it links me to ad media shananigans. TubbyMonster 21:04, 4 June 2012 (PDT)
- Hmm... That's weird. Is it your browser? I know of a couple that basically have built in ad machines. — Xenak (Talk|Contribs) 21:06, 4 June 2012 (PDT)
- Most likely you have something injecting ads into the webpage, be it a malicious browser extension or some adware program on your computer or your ISP itself injecting ads into the webapges you see (happens). This wiki has no advertisements on links, or banner ads, or pop-ups, or anything. — Wind 21:08, 4 June 2012 (PDT)
- Maybe run a scan on your computer to see what's going on? Have you ran any executables or been to any 'unusual' websites in the past few days? -NameUser 22:59, 25 June 2012 (PDT)
Class article galleries are a mess
I'd really like to clean up the class galleries. It's been on my list of things to do for awhile. Take the Engineer gallery for example. We have concept art, noteworthy class stills, and promo stuff. I don't think anything having to do with other games should be present on these galleries. All of those Worms images belong on the Worms: Reloaded article, all of the MNC and SMNC stuff belongs on those respective articles. I also think the "Class cards" should just be removed. They aren't cards, they're images of the classes. We have one of those at the top of the article. The class's default arsenals should either be removed to added to class infobox at the top of the article. Once the promos and "class cards" are gone, I think images should be sorted by age, oldest first. So, TF/TFC images first, then TF2 concept art, then trading cards, then any other TF2-age shots worth keeping. I believe these changes will make the galleries look much better, cleaner, as well as flesh out the promo articles a little. Opinions? --SilverHammer 13:19, 11 June 2012 (PDT)
They are actually cards.Oh wait, now I know what you mean. Yeah, those are unnecessary. 13:20, 11 June 2012 (PDT)
The other versions of the killicons
I have noticed throughout the wiki that pages which have killicons only have the versions that are seen when they apply to the player, and not the white-on-black ones when they don't. I believe we should use some CSS to make it so hovering over one of these killicons will show the white-on-black versions. This is of course easier said than done but I want to see whether everyone else thought it a good idea. rZ 14:51, 11 June 2012 (PDT)
- It's Beige-on-Brown/Brown-on-Beige but Support. 14:53, 11 June 2012 (PDT)
- This doesn't add anything of value to the page which isn't already communicated by the image already in place. i-ghost 15:01, 11 June 2012 (PDT)
Paint Style Overlinking
When looking at the team colored painted variants for an item (such as Flip-Flops), the text RED and BLU are linked for every paint. This is a case of overlinking, and can be fixed, but would cause a lot of updates. The fix lies in {{Dictionary/items}}
, wherein the team paints are all named (using RED and BLU links). By removing these links for all but the first paint (waterlogged lab coat IIRC) it would solve this problem. The catch lies in whether or not pages use this dictionary entry aside from via transclusion to {{Painted variants}}
. Ideas? User:Darkid/Sig 18:35, 15 June 2012 (PDT)
- Might I suggest that they don't need to be defined seperately or linked at all? Just replace (in the template) with a lookup for the base paint name and bolt on the team name, none of it linked... 06:15, 16 June 2012 (PDT)
- Not linked at all sounds great. I don't see how you could configure it to not be defined separately, though. User:Darkid/Sig 07:34, 16 June 2012 (PDT)
- It's been over a week since I said that, so I think that merits pushing this change. I'll wait a day or two if I hear anything against this in the next 2 hours... Darkid 12:23, 20 June 2012 (PDT)
- Disagree I don't know if I'd want to hunt around a table looking for the entry that holds the link. It's one thing to not link something more than once in a flowing paragraph, but in a table like this someone might be looking specifically for Cream Spirit, and not even notice that Waterlogged is the only one with a link Balladofwindfishes 12:26, 20 June 2012 (PDT)
- (am now holding off for 1 day) I have no trouble locating the links (they're in the Dictionary wrapper), and would (As per above) remove all the links. RED and BLU are linked to on any painted item's page in the navbox. I understand the sentiment, though, of hunt+peck through a table for a link. Darkid 12:32, 20 June 2012 (PDT)
- It's been over a week since I said that, so I think that merits pushing this change. I'll wait a day or two if I hear anything against this in the next 2 hours... Darkid 12:23, 20 June 2012 (PDT)
- Not linked at all sounds great. I don't see how you could configure it to not be defined separately, though. User:Darkid/Sig 07:34, 16 June 2012 (PDT)
Darkid, please realize that just because nobody has objected doesn't mean that everybody supported, and that it's not a legitimate reason to go ahead and make a change that will affect large amounts of the wiki. rZ 12:30, 20 June 2012 (PDT)
- Hence my wait. However, a week is sufficient time for someone to read the thread and comment. I can't be asked to petition around to see if the topic is passable (by say posting on every admin's talk page). Darkid 12:32, 20 June 2012 (PDT)
A quote from wikipedia's Manual of Style: Generally, a link should appear only once in an article, but if helpful for readers, links may be repeated in infoboxes, tables, image captions, footnotes, and at the first occurrence after the lead. I feel that this link set, while not *aggravating* per se, is a gross example of overlinking. Besides, the pages Red and Blue don't have that much to do with these paint colors, except that the paints look different when on these teams. That would indicate that a link to Paint Can would be more useful. The fix would not, as has been suggested, remove only a subsection of these links, it would instead remove all of them. Again, there is no need (and no need to assume) that people are going to have trouble/want to see the pages RED and BLU after/from this page. Darkid 16:04, 20 June 2012 (PDT)
Ahem. So, I see a few concerns:
- First, this change is hard to push. False: The strings are in a dictionary wrapper, and easy to change.
- Second, removing some of the links will cause an issue. True: Thus, all links will be removed.
- Third, removing all of the links will cause an issue. Debatable: However, it seems unlikely that A. People will want to read a page about sub-companies and merchandise for a fictional team after looking at paints for an item and B. People will have trouble finding these links if they want to do so.
- Fourth, removing these links will cause a massive update. Partially true: This change will update 182 hats (in all languages), and will update no more than that, as these strings are only used on paintable hat pages. The strings will be changed simultaneously, so that each page need update only once.
Feedback? Darkid 20:54, 21 June 2012 (PDT)
- I agree on all counts It's also going to be slightly more optimal to not have a dictionary entry throwing out links. 03:48, 22 June 2012 (PDT)
- Support There really isn't a big necessity of having those pages linked everywhere, so I guess it's okay to remove those links. Afterall, the two companies are already in the index, on the Main Page. And the RED and BLU pages aren't really that important in the hat pages, such that if they are left out of those articles, it won't make much of a difference. Also, the pages will look a lot better. – Epic Eric (T | C) 16:56, 22 June 2012 (PDT)
- Agree Though, my suggestion is to simply remove all of the links for RED and BLU. It's rather obvious to anyone that has played the game for a few minutes that they're going to be team-colored. One thing that would also help this is to put both images for the team-colored previews in one column for each of the respective paints. The redundant names are also a bit of an eyesore. -- Lagg 20:28, 22 June 2012 (PDT)
- Liquidfire says (Via IRC): I Agree. In my opinion, they should only be showed once User:LiquidFire 15:43, 23 June 2012 (PDT)
- Agree Indeed, I prefer to have all the links removed. It will look far better than the sheer over-linking or the odd one-or-two links. At any rate, there are almost always links on every Hat's page that already link to the respective team pages. 15:51, 23 June 2012 (PDT)
- Agree Remove all links. Red and Blu are not important things to link to. Balladofwindfishes 16:04, 23 June 2012 (PDT)
- Failing insane thunderstorms, I'll push this change tomorrow. Brace yourselves :P Darkid 16:07, 23 June 2012 (PDT)
Translating MediaWiki UI Strings
Hello everybody (again) (Don't you ever get tired of mah discussorz?),
I've come to realize that using our {{lang}}
template, we can translate the MediaWiki UI with great ease. If we can get all of our translators together, we can contribute to translate most if not all of the UI.
For example, at the top of this page there is a header which says "Project page". This string is stored at MediaWiki:Nstab-project, which only admins can edit. If all the translators can meet together to translate these core UI strings, we can have a more localized UI for the other languages, which makes everything better. (For example, the Spanish version of Project page would be Página de proyecto (if I translated that correctly)).
Obviously, this would require admin approval, which in turn requires community approval. Please feel free to discuss, and add any additional pros or cons as you see fit. rZ 18:01, 22 June 2012 (PDT)
- Concern #1: Time. How bad is this on that?
- Concern #2: Ease of translation. Should be peachy.
- Concern #3: Necessity. Eh... if you found more of these, I'd be happy.
Darkid 18:31, 22 June 2012 (PDT)
Look around you. All of the tabs on the top of the page, the options to move, delete, and otherwise modify pages, the quick links at the top of the page (My talk, etc), the sidebar to the left, the options while editing a page... There are many, many UI strings that can and should be translated. rZ 03:06, 23 June 2012 (PDT)
- I am a russian translator and I have set 'russian language UI' in my wiki settings. Being logged in, instead of 'Project page' I see russian translation ('О проекте'). So guess UI is already localized. — Stormbird T│C 03:39, 23 June 2012 (PDT)
Missing images in some browsers
For some reason, The Scout's leaderboard class icon doesn't show up in Firefox. Nor do some achievement icons (forget which), or the Banana Peel's backpack icon. Why is this?Open Source Forever 17:22, 25 June 2012 (PDT)
- They work fine in my Firefox 17:23, 25 June 2012 (PDT)
- What version are you using? I have 13.0.1.Open Source Forever 17:33, 25 June 2012 (PDT)
Those Archive links
So I just noticed that 2010 and 2011 run January-December (Top-Bottom), while 2012 runs December-January (Top-Bottom). This should be fixed, and I'd quickly suggest to flip 2010 and 2011, since that way it would read Newest-Oldest (Top-Bottom). Darkid 18:23, 25 June 2012 (PDT)