Team Fortress Wiki:Translators' noticeboard

This page can be used to discuss or announce any topics related to Team Fortress Wiki translation. Translators should this page to keep track of news or announcements (either by clicking or the tab at the top of the page).

You can also use this page to post questions or ask for help with translation. Note that most discussion related to a particular language should take place on its progress page.

See also

• Help:Language translation – guide to language translation
• Team Fortress Wiki:Translation progress – individual languages' progress so far
• Category:Team Fortress Wiki translation – other related pages

Resources

• Help:Translation switching – using {{lang}} to show multiple languages stored in a template
• Help:Editing – basic editing help

Other

• Team Fortress Wiki:Discussion – our main discussion page
• Official TF Wiki Translators Steam Group
• #tfwiki IRC channel (how to connect)

Discussion

Language forwards

I've been noticing a number of redirects to Romanian pages recently; specifically Ospitalitatea Sudica (forwards to Southern Hospitality/ro), Casca de Miner (forwards to Mining Light/ro), Craniul Cadavrului (forwards to Cadaver's Cranium/ro). What's the policy on this? I can see a bunch of problems appearing if we get an item called "The Stranger" (which would conflict with L'Etranger), or if a number of languages share the same name for an item ("Hatte" is Danish, Norwegian, and Swedish for "Hats"), which would require disambiguation pages, forwarding to each individual language page. The problem I'm seeing with this solution is a bunch of unmaintained and orphaned pages, leaving the Wiki in disrepair. ~ lhavelund ^{(talk ▪ contrib)} 09:25, 2 November 2010 (UTC)

I'm talking as Romanian Speaker. In Romanian these situations are not likly to happen. I can't be blamed for other languages similarities. And regarded as redirects, i saw others before started doing mine. -- Nightbox _{(t s)} 09:28, 2 November 2010 (UTC)

I understand that from our discussion in IRC, which is why I ask a standardised policy on the issue, so other translators know how to act. ~ lhavelund ^{(talk ▪ contrib)} 09:29, 2 November 2010 (UTC)

I don't see a problem with them as long as they are categorized properly (just made {{R lang}}) so they can be looked after easier. If, to take your example, Hatte is made as a redirect for the Danish Hats page first, then the other pages should just do Hatte which is what everyone has been doing so far. seb26 [talk] 09:32, 2 November 2010 (UTC)

The problem I see with this "solution" is that, say [[Hatte]] is made to forward to [[Hats/da]], and [[Flammekaster]] forwards to [[Flame thrower/sv]]. Then we have a serious consistency issue, which I think would be damaging to the integrity of the Wiki, and to the quality of it overall. ~ lhavelund ^{(talk ▪ contrib)} 09:35, 2 November 2010 (UTC)

Could you try and explain the problem better because I'm not seeing it. seb26 [talk] 09:40, 2 November 2010 (UTC)

OK. The terms for "Hats" in sv/no/da is "Hatte". The term for "Flamethrower" is "Flammekaster" in all three languages as well. Another case is with "Signalpistol", which, as far as I'm informed, means "Flare Gun" in all three languages too. [[Hatte]] forwards to [[Hats/da]], [[Flammekaster]] to [[Flamethrower/sv]], and [[Signalpistol]] forwards to [[Flare Gun/no]].

This creates serious consistency issues for the user. "If I put in 'Flamethrower' is it going to take me to a Norwegian, Danish, or Swedish article?"—I therefore suggest that we abolish the use of {{R lang}}, and only use $ENGLISHNAME/$lang for all of our pages, to avoid such confusion. ~ lhavelund ^{(talk ▪ contrib)} 12:24, 2 November 2010 (UTC)

I agree with Lhavelund. If languages share terms, then no language should take precedence over another - especially not if it's only because they created the page first. The only language that should take any sort of precedence is English, and even then only because that is the native language of the game. The simplest and fairest way is to just leave it as "English/lang". There would be a hell of a lot of maintenance if this did come to pass. The number of double redirects would likely increase, with editors linking to the localized titles rather than the proper "English/lang" pages. Also all conflicts would need to have a disambiguation page created which would need to be maintained. Actually, how would that work? Would the disambiguation page be in English? It would have to be since it would necessarily be linking to several languages at once. If the page is in English, it almost seems to defeat the purpose, doesn't it? It seems like more trouble than it's worth if you ask me... -- -- 12:42, 2 November 2010 (UTC)

The swedish words for flamethrower and hat(s) are NOT "Flammekaster" or "Hatte". This is false. The correct translations are: Hat = Hatt, Hats = Hattar, Flamethrowers = Eldkastare and Flamethrower = Eldkastare. CupcaknHell (talk) 06:54, 1 January 2016 (PST)

Google Translator

If you discover pages that have clearly been translated through Google Translator, please report them here. Be sure that the page has actually been translated this way (other signs include broken formatting, etc) and is not just lacking in grammar and punctuality. seb26 [talk] 08:23, 7 November 2010 (UTC)

Would it be possible to have a script automatically translate the original english article through Google Translate and check the similarities? Layzergun 13:48, 8 November 2010 (UTC)

I think I saw some articles in the Dutch section of the wiki... I'm translating them again if I find them. Goudvis 16:51, 19 November 2010 (UTC)

Speaking of Google Translator - Shotgun/pl. --Parseus ( | talk) 21:40, 14 November 2010 (UTC)

Found a recently danish translation that was translated using google translator Dueling_Mini-Game/da LiquidFire 08:53, 29 July 2011 (PDT)

L'Etranger/ja: In this moment, anything translated there is Google Translated character for character for all but the item's name. — C2Talon 10:55, 10 October 2011 (PDT)

User:Patrickq9 have been using google translate to translate these pages Wrangler/da, Killer_Exclusive/da LiquidFire 05:32, 14 October 2011 (PDT)

According to a message left by LiquidFire, User:G4me1000 has been translating Danish articles using Google Translate. Articles in question are: Baseball Bill's Sports Shine/da, Troublemaker's Tossle Cap/da, Scattergun/da. I'm not exactly sure which of them are Google Translate'd, so perhaps a Danish-speaking editor can shed some light on this (as I only speak English) 404: User Not Found ^(talk) 17:01, 16 October 2011 (PDT)

Any Danish editors here? Someone needs to look into G4me1000 and his newest contributions, find out if they're Google Translate'd or not. 404: User Not Found ^(talk) 12:10, 17 October 2011 (PDT)

October 28, 2011 Patch/no possible google translation by User:VAntoni seb26 12:30, 31 October 2011 (PDT)

Gold Rush/zh-hans this page is google translated,i'll try to re-translate it.240580420 23:18, 4 July 2012 (PDT)

User:gdfsgdfg has been translating pages using google translate. Arena/ro and Sawmill/ro. Proof:http://wiki.teamfortress.com/w/?diff=1204492 .There may be more. Ashes 03:54, 21 November 2012 (PST)

User:Shadowcon66 is using Google Translate to do minors edits on french pages. Exemples : Kong_King/fr, Smissmas_Caribou/fr and pretty everything in his contributions page. SillyPingwins (talk) 11:47, 6 January 2014 (PST)

Mannworks/zh-hans<- This pages "location" and "Gallery" section is confirmed 100% output by translation tool because the user didn't even change Chinese default fullwidth mark to halfwidth ,causing the loaction section a complete mess. The gallery section uses the word"生成室"(generation room) which is too obvious to be output by tool the correct word should be"重生点"or "出生点"(respawn , spawn), and btw the page is created and mostly edit by User:Eirin_Yagokoro Profiteer（奸商） (talk) 11:51, 17 April 2023 (UTC)

The Swedish wiki...

...has a lot of grammar/spelling problems. For instance, "dom" is used instead of "de" and "dem". Some pages, such as Heavy's, seem to be machine translated :(

I will attempt to fix this.--Alex IDV 13:20, 8 November 2010 (UTC)

More active spanish translators?

Half the pages are either google translated or just the english page with the trans-spanish tag. I don't see many spanish translators in here. --The preceding unsigned comment was added by Latin Geek (talk) • (contribs) 13:34, 8 November 2010

That's because they are lazy muffins... there are spanish translators that really translate, for example, me :3 -- Patofan 13:35, 8 November 2010 (UTC)

Or me... I translated all the pages I could to spanish danimart 09:42, 10 November 2010 (UTC)

Me too, and you are right, I see the Sticky Bomb launcher page i english. I will translate it when I can. Jagoba_RL 17:42, 1 December 2010 (UTC)

Just joined, I can help with the translation. I fixed the Sitckybomb page (and Scot Resistance). Got an English keyboard so I might leave out a couple tildes here and there though. WILDBEAST 04:45, 22 February 2011 (UTC)

I just like to say that I too just joined recently and I am hoping to help out as much as I can.

Currently I am making a list with all the pages that need translating so it is easier for us all to see what needs doing. This is a work in progress. Feel free to check it out at http://wiki.teamfortress.com/wiki/Team_Fortress_Wiki:Translation_progress/es/to-do Please don't edit this page as I am working on it.

Hope I can help the Spanish team :) BiBi 05:47, 26 March 2011 (UTC)

Hi,"just" joined too, i will be hanging around and i will try to translate as much articles as i can so...

Barracudastoyaface! 9:35, 5 May 2012 (UTC)

This is too old m8, I'm here - Maxijabase

A Chicken in every pot and a.... {{Languages}} on every update page?

That's the question I have, but yet, should every page have one? Newb editor->>>Vulturas 15:44, 9 November 2010 (UTC)

No, its kinda included in the sidebar. -- Nightbox _{(t s)} 17:51, 9 November 2010 (UTC)

It was a question for the higher ups :p They know 100% what to do here, but your answer is good, I will wait to see what they say tooVulturas 20:09, 9 November 2010 (UTC)

He pretty much answered the question. Is it not that noticeable in the sidebar, or are people still looking towards the bottom for the languages bar? seb26 [talk] 20:11, 9 November 2010 (UTC)

I thought it could ease translator's work :-/ you know, it could be noticed easier if a certain useful page in EN isn't in the X language if it has that language bar

PS: Edit, forgot to add the signature Vulturas 12:17, 10 November 2010 (UTC)

We still use the languages template on some pages, it's really up to personal preference now. We moved the links to the sidebar so navigation could be provided automatically and have the links appear on some pages where it wasn't possible with the template (e.g. the edit page view). But really it doesn't matter if a page uses both. seb26 [talk] 20:15, 10 November 2010 (UTC)

Most wanted translations for specific language?

Title is self-explanatory. Is there any way to check the most wanted translations for only one language (pt-br, in this case?) – Epic Eric (T | C) 23:56, 25 January 2011 (UTC)

When you click the "Most wanted translation" tab button above , set the page count to 500 , then hold the " ctrl + F " keys in your browser then type in the text box that appears "/pt-br" and be sure you selected the page first before doing that , now you can check the most wanted pages for only one language without the pain in the ass scrolling bar , i hope i helped you with that :D . --– Gin_Ginster _(talk) 15:18, 26 January 2011 (UTC)

I expected something more automatic, but it worked anyway. Danke! {{SUBST:User:EpicEric/Sig2}} 16:42, 26 January 2011 (UTC)

Translation Friendly/Friendlier Articles

I was wondering around the Wiki until I have found out that some articles are NOT that easy to translate with speed. For example ((=[ ; )=] here) we have ((headwear)) instead of ((Hats|headwear)). In consequence users will create a redirect reading ((headwear/lang)) for the above redirect, and thus they will end up with the ((headwear/lang|(headwear in their language))) instead of ((Hats/lang|(headwear in their language)). This is one of the issues I have noticed. Another issue that would make the translation process a bit easier is pre-adding the {{DISPLAYTITLE}} and the | name = (english name) in the article. This would be easier for users that lack some symbols. For example, the only way of getting the | symbol while I'm using the Romanian keyboard is to have it prepared to be pasted where needed. Another minor issue is the availability, the order should be Unlock, Drop, Craft, Purchase, Crate or so on all crates, makes the articles seem tidier and more professional. An example of what I do I want to mean is here. I hope that no one minds because the quality of the article hasn't been altered at all; the article would be somewhat of a Translation Friendlier/Friendly Article. I hope that I wasn't too unclear, making people confused.Vulturas 11:49, 30 January 2011 (UTC)

 Comment added a much more consistent example, weapon this time, here, and it should be noted that these changes would take place only in the English side of the Wiki.Vulturas 13:37, 30 January 2011 (UTC)

 Support I think this will be a good idea if it can help people translate better, plus it doesn't actually change the content of the English pages all that much anyway. ^Scatman _John (Talk | Contrib) 11:56, 30 January 2011 (UTC)

 Support I really like the idea of pre-adding the {{DISPLAYTITLE}}. It is very useful! VeKoB 12:07, 30 January 2011 (UTC)

 Comment And the name thing in the item infobox!Vulturas 12:47, 30 January 2011 (UTC)

Translating Attention

Hi, Im Ravecrib9t4 and i'm translating the norwegian parts around the Team Fortress Wikipedia. I have a feeling and i guess others would feel it too that when you are translating to your own language, you dont get alot of attention from others by doing so. I want to know what you think of this. The Noble Scout AKA Ravecrib9t4 16:03, 27 February 2011 (UTC)

Steam group & progress page update

I've started a new Steam group for all wiki translators to join – Official TF Wiki Translators. Please join and invite any other translators you may have on your friends list. Having this group will also make it easier to alert everyone to announcements, changes & whatnot related to the translation project.

The Team Fortress Wiki:Translation progress page has also been given an update. It includes new stats pages for each language that highlight progress in individual areas (such as hats, weapons, strategy, etc), and can show which areas have missing articles and need targeting.

seb26 09:18, 8 March 2011 (UTC)

The Dutch translations of (Vintage) , (Unusual), etcetera are incorrect.

Some items may be tagged as, for example, '(Vintage)' or '(Unusual)', like 'Flare Gun (Vintage)' or 'Haunted Metal Scrap (Unusual)'. Depending on the intended use of these tags, the translation of these tags in Dutch could be different from the current translations. If the tags are intended to be an adjective, as in 'a vintage hat', then the current translations are correct. However, if the tags are intended to represent the status of an item, as in 'this hat is vintage', then the currect translations are incorrect. Personally, I think the latter is the case, and thus the current translations of the tags are incorrect.

I believe they should be changed as following: Vintage: 'Klassieke' should become 'Klassiek'. Genuine: 'Authentieke' should become 'Authentiek'. Unusual: 'Ongewone' should become 'Ongewoon'.

The wiki agrees with me, as is seen here: [1]

Worse still, even entire words are different, for example 'Unusual' is translated as 'Bijzonder' on the wiki, and as 'Ongewone' in-game.

So, to conclude, I believe the in-game translations should be changed to match the ones on the wiki, for they appear to be correct. — The preceding unsigned comment was added by Jeroenvw (talk) • (contribs)

We follow the the official localization files and they add an 'e' as the idea is that the quality comes before the name, which creates the correct 'Klassieke <hat>'. Therefor, the e shall remain in place.

For the 'Bijzonder', I checked what is up with that; as it turns out, someone got overzealous and started adding new and altered names that have not yet been accepted into the game but that have appeared in the Steam Translation Server. Looks like I'll have to fix that.

Thirdly, we here at the Wiki are not responsible for in-game translations. The people over at the Steam Translation Server are. We merely document the game and thus if game and Wiki do not match, it's the Wiki that has to adapt, not the game. With other words, I need to get to work. Hefaistus - talk 11:01, 31 May 2011 (UTC)

Does the quality display incorrectly in the backpack item template on Dutch articles? I can fix that for you right now, if so. -- Pilk _(talk) 11:12, 31 May 2011 (UTC)

They appear behind the name instead of in front of it. So instead of 'Vintage Natascha', it says 'Natascha (Vintage)'. This appears to be the case for all translations. I must admit, by the way, I play TF2 in English, so I can't say for certain if this is also the case for the game itself, but I'd very much doubt that. If you'd want, I can go and check the Dutch version before you do anything? -- Hefaistus - talk 11:35, 31 May 2011 (UTC)

Ideally it should display the same way it does for a typical Dutch installation of the game. Let me know if the way it is currently displayed on the wiki is correct or if it needs to be chaged to display some other way. -- Pilk _(talk) 13:07, 31 May 2011 (UTC)

I stand corrected, item qualities do appear behind the name instead of in front of it. That means they appear correctly on the Wiki at the moment. I am quite surprised, to be honest. I always thought that there were no differences between languages. Anyhow, you won't have to change anything, Pilk, and I'll ask the mates over at the STS what they think about changing the grammar properties of the qualities. -- Hefaistus - talk 17:27, 31 May 2011 (UTC)

Notice for russian editors -- Викификатор

Notice for russian editors

Уважаемые редакторы русского раздела! Я портировал из русской википедии скрипт для автоматической викификации, позволяющий оформлять статью, расставляя правильные кавычки, тире и переносы. Приглашаю всех к тестированию. Для того, чтобы добавить скрипт к себе нужно отредактировать страницу Вашего персонального JS и добавить туда следующую строку: importScript("User:Daniil/wikify.js");. После этого на каждой странице редактирования статей появится такая кнопка.

Внимание: Викификатор предназначен для использования исключительно на страницах русского раздела вики.

Спасибо за внимание, надеюсь, скрипт окажется полезным для вас, Daniil 14:15, 13 June 2011 (UTC)

Wiki cap?

Just a quick question: how many pages must be created / translated in order to get a official wiki cap in-game? — The preceding unsigned comment was added by Hudsonm1a2 (talk) • (contribs) 22:32, 18 June 2011

It's not a matter of number of pages; it's a matter of whether or not the community considers your contributions valuable.  –  Epic Eric (T | C) 22:35, 18 June 2011 (UTC)

Ok, then I'll make sure to spend some days editing and translating pages. I'm looking forward to see the brazillian part of the wiki fully translated. Better if we can translate it fully before anyone else. I'm translating this page http://wiki.teamfortress.com/wiki/Community_2Fort_strategy/pt-br (which has not been created yet, but hopefully it'll be by this afternoon/evening). After this, I'll translate the other strategy guides for the other levels, since they are some of the priorities.

Also, no custom signature yet by me... :( -- 'HudsonM1A2'

Game localization files

Game localization files now have the latest changes appearing directly on the page so it is easier to view what names / strings / etc were updated in a particular patch. You can find all L10n files in Category:Text files. seb26 19:07, 22 July 2011 (PDT)

Awesome! Thanks a lot <3 SackZement 04:14, 24 July 2011 (PDT)

Class Update History

Each class has a VERY long update history, big job for anyone willing to do so, it needs to be done. For those languages that have most of this/ all of this done, each class has some missing notes filled in from the Uber updater and later on. Again, big job but needs doing. - Lexar - talk 04:36, 9 August 2011 (PDT)

Get more editors!

I will ask by the sections of Turkish, Danish, Hungarian and Portguese Wiki. Can anyone get more people who has a interest of editing/translating etc. on these parts? Would be good to get more people to do some improvements to these sections :< The Noble Scout _(T/C) 13:46, 10 August 2011 (PDT)

At the moment I'm the only one translating the Danish section. Freakie and Hachach19 have been translating a few pages as well. But they don't seem to be active anymore. So if anyone knows any danish people who would like to help, I would appreciate it. Since I haven't been able to find any people. LiquidFire 12:18, 13 August 2011 (PDT)

-Hello there everyone! I'm here to help aid the translation of the hungarian TF2 Wiki pages. Coming with clean, oriented, and not some cheap mirror-translation. Done this-and-that, soon we won't be stuck at 7%. - Endroo 1:52, 08.28.2011 (UTC+1) (I just realised I sounded a bit like Billy Mays. Oh well...)

Class

Hello, I'm not really a translator, but I've been working lately to try to improve the quality of the item infoboxes in all languages. It seems so far that some languages seem to just use the English name for each class, and some use the word for that class in its own respective language. I was wondering if we could try to be more consistent about this or not, because I do enjoy consistency. I hope this is clear enough, because I need to know what to do before carrying forward. Shane Alvarado 12:46, 22 September 2011 (PDT)

Class names are translated on Bulgarian, Greek, Hungarian, Italian, Japanese, Korean, Polish and Russian according to STS.  –  Cructo [T][C] 12:53, 22 September 2011 (PDT)

Thank you, sir. That helps a lot. Shane Alvarado 15:04, 22 September 2011 (PDT)

Trying to help get some more translators

I just put this advert up in my Steam Group. Hopefully we can get more Translators here! Let me know if you want me to add anything else to that announcement. 404: User Not Found ^(talk) 12:22, 17 October 2011 (PDT)

Attention all translators!

I have some tasks for you guys. Whenever you have some spare time, and don't know what to translate, feel free to take a whack at anything on this list:

• Translations are desperately needed on the TFC Custom Maps navbox. The only language it supports currently is English.

• Replace any instances of "Deathmatch" with "Custom" on your respective language's version of Boot Camp, Crossfire, Datacore, Frenzy, Gasworks, Lambda Bunker, Rapidcore, Snark Pit, Stalkyard, Subtransit, Undertow. Follow the way I've changed instances of "Deathmatch" with "Custom" on the English articles.
  • Done (as well as the point above) for the Russian versions of these maps. ShooterAndy 10:56, 7 July 2012 (PDT)

• Most of the translated versions of the Advanced Weaponiser article are horribly outdated, most notably the French Advanced Weaponiser article. I have recently revamped the English page and added a whole bunch of things.
  • Same goes for the Randomizer article. I'm not sure how up-to-date the translated articles are compared to the English article, but it wouldn't hurt to check.

• The TF2 Mods navbox is missing translations for a number of things.

I'd love to go through and do this stuff myself, but I only know English (I was good with French in high school but over summer break in grade 9 I kind-of forgot everything I learned about French and gave up on it. Still kicking myself for not re-learning French.) Any help with this stuff would be greatly appreciated. Keep up the great work, translators! 404: User Not Found ^(talk) 19:57, 30 October 2011 (PDT)

Patch Name

Just a new template to help translators. It uses the format {{Patch name|month#|day#|year#}}, and it automaticaly returns the patch name in your language.{{Patch name|10|28|2011}} generates October 28, 2011 Patch. I believe you can already start using it. GianAwesome 13:16, 2 November 2011 (PDT)

More languages

I think it's time for some more langauges.

May I start translating pages into Serbian, please? Damian0358 15:10, 5 November 2011 (PDT)

The process for adding new languages starts with the Steam Translation Server: STS -> official TF2 localization -> wiki. The wiki has so much content that an official loc file is really needed to keep everyone on the same page. We don't have STS-only languages either (there are grandfather exceptions) because namings, text, common words, etc change too frequently and can be approved/denied at any time (& there is no public viewing). Help:Language translation explains a few of these things. Serbian looks like it has an app ongoing for STS however [2], but the last I heard was that Torsten said they want to see how Greek / Bulgarian / Thai turn out before adding any new ones. seb26 19:20, 4 November 2011 (PDT)

OK, thank you for explaining! Damian0358 15:10, 5 November 2011 (PDT)

UPDATE: Thai, Bulgarian and Greek are all now official Steam languages. More languages maybe this spring? Thebigone 14:05, 7 January 2012 (PST)

I would like to see Icelandic on the languages list. -The Dolphin

Template for monitoring source diff

Hey guys, I just created a template at User:BenMQ/translation progress. This template allows you to view the diff of the source since the last time you translated the article. You can see the example on User:BenMQ. I think this helps keep articles up-to-date. Another benefit is that in the future, we can have a bot to go through all pages with this template and see if the source has been updated. If so, the bot can tag the article as {{update trans}}. What do you think? If this is useful, I'll move it into the template namespace. BenMQ 18:47, 23 December 2011 (PST)

Item set crafting strings

The item set blueprint section of the item strings needs to be translated so it works with the new item set crafting blueprints (example). Please do test it before you implement it on articles; the "Set Name weapon" parts shouldn't be very long. rZ 15:01, 23 March 2012 (PDT) 12:52, 24 March 2012 (PDT)

Team Fort-Heb: TF2 wiki in Hebrew?

Hello Wikiwriters,

For a while now I wanted to rip off translate the wiki to Hebrew. I called this project "Team Fort-heb" and because of school and other events in my life, I never got to A. create an account or B. to acually ask premission or start it. You'd be suprised how many people play TF2 here in Israel (here is just an example of a well-known TF2 hebrew forum and for a few months the domain "tf2.co.il" was up and gave interesting forum posts and some strategies. And yes, it will work since Arabic and Hebrew are right-to-left.

So,  Yes or  No, should I start the offical TF2 hebrew wiki? (Or may I say, TF2 הויקי הרשמי של) Rocket Sticky Jumper Talk 08:06, 31 March 2012 (PDT)

Hebrew is currently not supported by Steam (and thus TF2), which, as far as I am aware, is a requirement for a language to be added to the Wiki as well. However, as you can see here, Hebrew is already a petitioning language and might join Steam at some point. Until that day though, it's doubtful that Hebrew will be added to the Wiki. -- Hefaistus - talk 08:17, 31 March 2012 (PDT)

Okay, so now I guess it's  Haulted? Rocket Sticky Jumper Talk 11:14, 31 March 2012 (PDT)

Add "Bahasa Melayu" In TF2Wiki?

Hello,it seems that there is no TF2Wiki in Bahasa Melayu,Bahasa Melayu is needed for Malaysian to understand in their own Language.Far_Red 02:35, 13 May 2012 (PDT)

Steam/TF2 currently does not support this language, which is a requirement for a language to be added to the official TF2 Wiki. So unfortunately this cannot and will not be done. Warlike 02:39, 13 May 2012 (PDT)

Oh I see,well that's a shame,hopefully they will addded Bahasa Melayu in the future.Far_Red 05:55, 13 May 2012 (PDT)

Tool list template

In case anybody wants to translate their own language's Tools article, I advise you to use the Tool list template. I believe it would help a lot. JerryPL ^Maggots! 11:06, 2 August 2012 (PDT)

'scripting/ko' has been translated.

I would get it done after a week at most. Dinir Nertan 18:20, 30 September 2012 (PDT)

Complete translating. I'll get to the bed today and check my translate again in next morning. So tired. Dinir Nertan 07:25, 1 October 2012 (PDT)

• Done* Dinir Nertan 18:34, 1 October 2012 (PDT)

TF2 wiki in icelandic?

Hey, I'm not really a translator, but I was wondering if anyone wanted TF2 wiki in Icelandic? I can translate from English to Icelandic, but I may or may not have time to, depending on if it is a wanted thing within the wiki. Edit this post saying so, if you think this is a good idea. thanks guys!

If you want a language to be supported, you'll have to contact valve. (Although the waiting game will begin) Right Wind? :D Ashes 17:25, 4 April 2013 (PDT)

The thing is, I don't want to contact valve, asking for a language that no one wants to be supported. I'm gonna need some others to help out here ._. -The Dolphin

Icelandic is currently a petitioning language. You can join the petition group here. -- Duddits 17:30, 4 April 2013 (PDT)

Similarly, if the wiki was to be translated in Icelandic, you would need a lot of help to translate a decent amount of it. There's a reason that existing translations are not finished, and it's not lack of editors or laziness — Wind 17:32, 4 April 2013 (PDT)

I have a few Icelandic / English speaking friends, and a motive.

I mean, who doesn't want the wiki cap? :D

-The Dolphin

Thai Translators needed

Hello guy I'm thai translator and would like to translate this wiki at the article that not translated

And I want some crew that help me translate this wiki please--THIS JUST GOT SIGNED BY SPIRALNUGGETS 01:24, 29 January 2014 (PST)

Your best bet would be to contact the Steam Thai STS group to look for more willing translators here: http://forums.steampowered.com/forums/showthread.php?t=1244344 Good luck! Warlike (talk) 02:11, 29 January 2014 (PST)

Team Fortress Classic localization files?

Did TFC has its own localization files for other languages? I want to get Simplified Chinese localizaion file (tfc_schinese) so that I can translate Classic contents with proper Simplified Chinese terms...

Kit LiuBei 97 (talk) 04:08, 12 February 2014 (PST)

WikiTranslator for automated, fast & consistent translations

I recently finished a script which automatically translates the majority of cosmetic item, item set and weapon articles. With it, it's possible to halve the translation time of these. It can be extended easily. Everything is explained on its own page:

WikiTranslator

Please take a look. It's worth it ;)
If you have any questions, just contact me via my talk page, email or Steam page.

~{ TidB | t | c }~ 09:37, 8 March 2014 (PST)

Until now, there were some updates with lots of functionality in them. The script now has a GUI with much more functions that can be customized and applied on the whole or a selected part of the text. Wikilinks and Wikipedia links are now fully automatically translated and it's checked if the sound file in the quote template has a localized counterpart. At first, the implementation of another language seems messy and complicated, but it's really not and I'm always there to help :)

~{ TidB | t | c }~ 09:55, 22 May 2014 (PDT)

ALL LANGUAGES ACHIEVEMENTS ARE NOT IN ORDER

It has been overlooked for a long time. In any language, EXCEPT the english one, are the achievements not in the alphabetical order. It is terrible for people to go through them or find specific achievements. So i propose either a massive template change or to not use the template. Example: Soldier_achievements & Soldier_achievements/de....only look at the first letter to see how terrible it is sorted... Magicalpony (talk) 08:24, 20 July 2014 (PDT)

Operation Cleanup

Because a name with "operation" in it sounds way cooler~

Hi there, Magicalpony/nevermindthx asked on the IRC once if I can write a script to check the item descriptions against the official descriptions from the localization files for all translated item articles. It'd be possible, since I already had the main parts written for another script. But when I'm already reviewing all translated articles, I can check them for more common mistakes.

I'll compile a list of all translated pages with mistakes in them soon. It'll take a while until I get to this and I don't know how fast I am. It may also be possible to write something to fix specific errors automatically, but again, this'll take some time
So, here's a list of the mistakes I could think of, divided into two sections. Please help me adding more ;)

 Error

These mistakes are definitely errors and most of them can be fixed automatically

• Usage of {{DISPLAYTITLE}} on item pages  Done
• Non-usage of {{DISPLAYTITLE}} on non-item pages  Done
• Usage of the name infobox parameter on item pages  Done
• Non-usage of the name infobox parameter on non-item pages  Done
• Usage of {{w}}  Done
• Wikilinks leading to the wrong language (Redirects would be resolved)  Done
• Links like this [[Page/lang]] instead of this [[Page/lang|Name]]  Done
• Usage of {{if lang}}  Done
• Fixing {{Quotation}}:
  • Usage of |en-sound=yes when no translated sound exists
  • Link to the correct localized sound

When we replace the english quote with the correct one we have an english quote (text) linked to a russian/french/german.. sound which is even worse I guess. So we only can replace sounds where the quote already has been translated. Which we cannot check with a bot except for when the quote on the english page is different from the one on the translated page. But then, the one on the translated page might just be from an earlier version; and I can't imagine we want to compare it to all previous quotes that were present on the english page. SackZement <Talk> 16:18, 9 August 2014 (PDT)

Fair enough. It actually would be possible to do the comparison on all revisions, but this would be an overkill. But may it be ok to inform the translators then? Or replace the quote when the it's updated on the English page? { TidB | t | c | wt } 06:24, 10 August 2014 (PDT)

When quotes are "translated", it's mostly just using the in-game audio translations. These audio files should be stored under a similar name (I believe there's a naming convention). It shouldn't be too much of a hassle to check against the current english version. If the translated page was translated from an earlier version, then it is out of date. Darkid (Talk | Contribs) 11:44, 18 October 2014 (PDT)

• Wrong links in {{Main}} and {{See also}}  Done
• Untranslated content inside links and templates (especially useful in "small" templates like ·{{tooltip}})
• Usage of [[Category:foo]] instead of [[Category:foo/lang]]  Done
• Usage of {{Template/lang}} instead of {{Template}} (with language switching)  Done
• Validation via the localization files:
  • Item description
  • Item flags
  • Item attributes
  • Random suggestion: Wouldn't it be possible to update the dictionary via a bot, too?
• Missing Wikipedia pages  Done

 Warning

These mistakes may be errors and thus cannot be fixed automatically

• Missing item infobox parameter loadout-name  Done
• External link without {{lang icon|en}}  Done
• No bold highlighting of the article name in the first few sentences
• Links like [[foobar]] are either english or redirects (but I guess there are some instances where we link to help pages etc. and can't just replace them)  Done
• Wikipedia links leading to the wrong language (this is actually a pretty tough topic, see the topic below)  Done

Added category/lang and template/lang errors SackZement <Talk> 02:26, 8 August 2014 (PDT)

Added {{if lang}} error. { TidB | t | c | wt } 11:22, 15 September 2015 (PDT)

Added missing Wikipedia pages error. { TidB | t | c | wt } 04:54, 5 December 2015 (PST)

UpdateHelper

And even more...
I think it's a good time to integrate something I'd though of for a while. It's a little helper that:

1. Gets the date of the latest non-bot revision of a translated article
2. Checks the last change made to the English article before this time
3. Returns the diff between the version at this time and the current one of the English article

I hope this is understandable ;)
This would easify article updates a bit since you see any changes directly in the diff instead of searching (and probably mising some) them.
At each page, there'd be a link to this specific diff.

Well then. I'm aware that posts on this page are known to be read rarely, but maybe there are people who respond to this ;)
{ TidB | t | c | wt } 01:57, 8 August 2014 (PDT)

1.Crafting & 2.Name check (common strings) & 3.NO dictionary bot update & 4. Availability & Attribute check

1.Most crafting in articles was done in the past this way:{{Blueprint | ingredient-1 = Wrap Assassin | ingredient-2 = Refined Metal | ingredient-2-amount = 4 | result = Big Elfin Deal | result-2 = Bootie Time }} And now it is just: {{Blueprint|autoresult=Santa's Little Accomplice}} The later is far more elegant and not so prone to errors or changes (miswriting...). I would like to see if you can implement that in general on crafting.

2. The common == "names" == (only which is stored in common string) should be checked against {{common string|"names"}}. If there are == "names" == which are not in the common strings it should maybe note that. Why? It is uncommon that there are "names" which are not there and most likely an error by another editor to not use the common "names".

3. No. Many language changes at new updates, which results in much "in change"/flux state. A Bot would most likely make something kaputt. I am not against bot work but the dictionary is the heart of the wiki and i dont trust bots enough for this task.

4. I would like to have the option to check "against" the english article. F.e. | availability = {{avail|crate36|drop|craft|purchase|unusual}} Most articles in other languages are outdated on this. Also | trade, gift parameters. This would help people to not just copy over the english article and adapt only the <code>| used-by [[Class/lang|Class]]</code> and the bottom item description. Magicalpony (talk) 06:07, 8 August 2014 (PDT)

Translation switching & comparing categories

1. Translation switching: It's possible to go through the templates in this category and check if there are missing entries left to translate.
2. Comparing categories: Maybe not directly related to this topic, but it'd also be possible to compare an English and a translated category so you can directly see which articles are missing.

{ TidB | t | c | wt } 05:26, 14 August 2014 (PDT)

Discussion

Just for seperating suggestions & discussion

 Soon... Hai, it may be possible I can compile the first lists in the next two weeks. But I can't promise anything ;) { TidB | t | c | wt } 03:58, 7 October 2014 (PDT)

Sadly, I don't have much time at the moment so I implemented just a few reviews, though it's easily extendable from now on. { TidB | t | c | wt } 06:12, 16 October 2014 (PDT)

Hoo boy that's a lot of suggestions. My comments in order of appearance in my mind:

1. Please make the code public. Please please please.
2. Checking against the localization files is already done, as I recall. If not, yes this is a useful idea.
3. Category:Foo/lang is not always wrong, please move it to warnings.
4. If you want a "last updated" then I suggest you look at mediawiki extensions.
5. Crafting templates should be up-to-date, if not I will fix.
6. I don't understand what you mean by =="names"==.
7. Availability should not include gifting and trading, they don't increase the quantity of the item, only allow redistribution.
8. Auto-copied availability is something that windbot could implement. I believe it already copies the steam contributors, e.g.
9. Category comparing exists, see TFW:Translation progress.

Darkid (Talk | Contribs) 13:28, 23 October 2014 (PDT)

1. Heh, yes, I know. Just let me clean up some things, and I'll do it later. For real ;)

2. I don't think it's done, I've never seen any corrections like that...

3. Alright.

6. I think Magicalpony meant that common headlines ("Blueprint", "Crafting", "Trivia", etc.) are present in the common strings so you can check if those headlines are correct.

9. Nevermind, I don't think we need that.

{ TidB | t | c | wt } 13:43, 23 October 2014 (PDT)

2. Sure, go for it.

6. Compare against what?

1. Soon. Darkid (Talk | Contribs) 13:45, 23 October 2014 (PDT)

Good ol' procrastination.

6. Well, if you have most of the common headlines for each value in the dictionary, you can check the headlines of the article if they match those present in the dictionary to determine if they're wrong. I don't think there'll be an easy solution as the headlines just couldn't be in the dictionary because, well, they aren't that common (just consider all those "Stage X, Control Point Y" combinations) or the pages are simply outdated. For know, I guess there's no stable solution. { TidB | t | c | wt } 13:59, 23 October 2014 (PDT)

There you go { TidB | t | c | wt } 08:05, 24 October 2014 (PDT)

Looking through the code, it really seems to me that most of these errors are immediately fixable. Displaytitle, name parameter, quotation, broken links, incorrect template style, and possibly localization file validation could all be fixed while parsing. Thus, I would suggest that these be turned into windbot filters, since the majority of them are small consistency issues. This would greatly reduce the number of things that require user input. Things like containing fully translated content or issues involving wikipedia pages should (and would) still be checked by actual users. Darkid (Talk | Contribs) 01:13, 25 October 2014 (PDT)

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘ Alright.

1. Removing of {{DISPLAYTITLE}} on special pages would be possible. On the other hand, adding this template to a template can't be done in most cases (except item sets).
2. The same applies to the name parameter.
3. Converting {{w}} templates would be possible, of course, though I find it's strange that WindBOT can convert Wikipedia URLs, but not those rather easy templates.
4. Wikipedialinks leading to the wrong language can't be fixed for now as it's not clear how to handle those if the Wikipedia article is not translated (see topic below).
5. Localized links that don't use captions/labels can't be fixed either. We could insert just the displaytitle instead, of course, but in most cases, this'll break the sentence structure.
6. Quotes could actually be fixed (link to correct sound if existing & usage of en-sound=yes; the untranslated text can be noted, see some sections beneath.
7. {{Main}} and {{See also}} could be fixed, too, using the displaytitle property.
8. Well, untranslated texts can't be fixed.
9. Categories and templates could be fixed automatically, too.
10. Validation via localization files: This leads to another topic, efficiency, that may not be that important, but it bothers me a bit. As far as I see, WindBOT applies its filters on one page at a time. As you can see, most of the reviews need requesting other pages (check if pages are English or language redirects, access English pages to compare text inside templates, check if Wikipedia articles are available in a specific language) that's done more efficiently when requesting multiple pages at once, which is up to ~5 times faster. This depends of course on the internet connection, whereas WindBOT's is definitely better than mine. But still, lots of pages would be requested unnecessarily often which would be really inefficient when it comes to the ~1MB localization files. To be honest, I haven't checked WindBOT's code too much and I don't know how fast he is at requesting pages, but this is more of a personal issue.

11. WindBOT doesn't check templates (yet), which is needed to check which translation switching-using templates are missing translations.

So you're right, some tasks could WindBOT indeed do.
{ TidB | t | c | wt } 10:29, 25 October 2014 (PDT)

1. "Adding this template to a template" what do you mean?

3. What other "easy" templates?

4. Wikipedia links *could* be handled by a bot, as SackZement was talking about below. As opposed to a template, a bot can follow a page link and see if it redlinks (and update).

5. I'm confused. I meant that if someone types Chapeux on a french page, we could change it to Chapeux for them. If they typed Weapons on a french page, we could change it to Weapons/fr.

8. Of course.

10. So I'm confused as to what you mean here about WindBOT's efficiency. If the bot reviews one page at a time, only per request, it may tak elonger to get through everything, but it prevents the bot from flooding the RC log, and allows us to catch issues before they propagate too much. You can always request a category to be checked here.

11. This is best suited for your style of algorithm. WindBOT is designed primarily for content pages.

Darkid (Talk | Contribs) 17:15, 25 October 2014 (PDT)

1. Sorry, I mispelled. I meant adding this template to a page (this can't be done).

3. By that I just meant the {{w}} templates. I mean, it's easier to process a nice little template than a URL.

4. The "(and update)" thingy is the problem. Before we can apply updates to Wikipedia links, we need to standardize the handling of Wikipedia links that don't exist in a specific language. And well, in this section are just two opinions...

5. I personally think [[Weapons]] --> [[Weapons/fr]] is an awkward solution and it's better to alert translators rather than fixing it like that (another awkward, but in my opinion better solution would be [[Weapons]] --> [[Weapons/fr|Weapons]]).

10. I didn't meant the efficiency in requesting the pages to review, but requesting the required pages for the link checking. And it's really more of a personal issue, but it's just faster to collect all page titles that need to be checked and then to request all pages at once and then to use all those information you got. I mean, just consider all those Wikipedia links on cosmetic pages and articles that make an excessive use of language redirects.

I hope this is clearer now .-.

{ TidB | t | c | wt } 18:00, 25 October 2014 (PDT)

1. Displaytitle works fine within templates, I still don't see why this is an issue.

4. Sure, I was just saying that having a bot makes this problem much easier to resolve. Many options become possible that wouldn't be otherwise.

5. I left it as Weapons/fr so that it would appear more wrong to translators, easier to spot. The page could definitely be put in a tracking category.

10. Again, just assign WindBOT Category:Cosmetic items and you'll do fine, right?

Darkid (Talk | Contribs) 18:04, 25 October 2014 (PDT)

1. I was referring to pages that require {{DISPLAYTITLE}}. Excluding some pages that can use templates like {{Update name}} to insert something like {{DISPLAYTITLE:{{Update name|Über Update}}}}, you can't do that on other pages (Like setting DISPLAYTITLE on a strategy page).

10. I'm still referring to the bundled request of pages that need to be requested for link checking. If you want to check if all Wikipedia links on all cosmetic item pages, it's much more efficient to 1. extract the Wikipedia article names 2. request all those articles at once to determine if they exist 3. do whatever you want to do with that information on all pages. WindBOT could not do it like this, as it would extract the Wikipedia links of just one page, request them and apply changes then, still on this on page. Well, not the most important topic and I don't know if it's worth discussing it with all those misunderstandings :P

{ TidB | t | c | wt } 18:39, 25 October 2014 (PDT)

10. Only if you write the code in an unintelligent way. The data on existent wikipedia pages could be cached, or stored in memory for each batch of updates. Also, although inefficiency is an issue, simplicity is worth it. Having fewer bots/more independent code is much more convenient. Darkid (Talk | Contribs) 18:43, 25 October 2014 (PDT)

10. Yeah, and that are the reasons why I called this only a personal issue I had with this. { TidB | t | c | wt } 18:46, 25 October 2014 (PDT)

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘ Here's a concept for the dispaytitle filter (I'll add more filters as well, of course). As stated on the page, I can't guerantee it's bug free because I haven't read WindBOT's and wikitools' code too much. Feel free to edit there. { TidB | t | c | wt } 13:53, 3 November 2014 (PST)

Actually, WindBOT does convert {{w}} templates, but the filter is set to low priority. Haven't noticed that. { TidB | t | c | wt } 00:45, 4 November 2014 (PST)

Generalikus Checkikus

I just realised something with the item infobox. Can you make it the way that it checks against the english article the "types" ;;;
Based on this edit.

{{Item infobox
| type = weapon
| image = Bat_Outta_Hell.png
| 3d-image-1 = Bat Outta Hell
| 3d-image-2 = Bat Outta Hell Scout
| 3d-image-4 = Bat Outta Hell Demoman
| 3d-image-6 = Bat Outta Hell Soldier
| 3d-button-1 = default
| 3d-button-2 = colored_pair
| 3d-button-4 = colored_pair
| 3d-button-6 = colored_pair
| 3d-viewname-1 = Universal
| 3d-viewname-2 = Scout
| 3d-viewname-4 = Demoman
| 3d-viewname-6 = Soldier
(circumflex) this would be nice and useful as first info ; NOT if the data after the = is correct but if the 3d-viewname-6 f.e. exists in the /de article. This would be an instant "item infobox is outdated" information. This could be autofixed IF all: | "types" are language switched...which they are not. Maybe this is somewhere already mentioned in this wall of text, but i wanted to point that out again. Dears forever in Love...;P Magicalpony (talk) 05:00, 24 October 2014 (PDT)

A non-english 'type' parameter will throw an error (place the page in Category:Item infobox ERROR). It is also language-switched. Darkid (Talk | Contribs) 01:02, 25 October 2014 (PDT)

Wikipedia link standardization

Hi there, I think it's time to think about the correct handling of Wikipedia links.
When an article in the needed language exists, it's pretty clear what to do. Something else happens when the W article doesn't exist in the appropriate language. There's some confusion about this; and everybody handles this differently. I think it'd be good to standardize this. Here are a few options how to handle these situations, together with my opinion:

1. Link to the non-existing page (This would correspond to the translation guide, but the link doesn't display as red, leading to confusion)
2. Link to the English page (This would collide with the translation guide and also lead to confusion for the reader. Everything's should be in one language)
3. Remove the link (I currently use this, as it wouldn't lead to confusion, though the reader probably misses some background info)

{ TidB | t | c | wt } 01:57, 8 August 2014 (PDT)

When we link to a non-existing page we actually invite the reader to waste his time by clicking a link for more information just to get nothing (same applies to an english wikipedia page if the reader barely speaks english). However, when we don't link at all, the wikipedia page might get translated the next day but we don't notice it until a few months after at random and fix the link. I think the latter is the lesser evil since the reader can visit wikipedia by himself if he really wants to and read the english article.

I propose a template: {{checkWikipediaLink|PAGE}} which just shows PAGE (without a link) on the translated tfwiki page but gives us a collection/category of wikilinks that need to be checked regularly. This can easily be done by a bot (at least checking whether the wikipedia page exists and then notify the editors or fix the link itself.) SackZement <Talk> 02:45, 8 August 2014 (PDT)

Adding languages to my typo-bot

I made a bot that finds typos, among others (Example Output). However, I only have a list of common misspellings for english, danish and german at the moment. If you want that I look at pages in your language, I need a list of common misspellings in that language first, more information how to help out can be found here. If you do not possess such a list but still want to help, tell me, so I can try to search one by myself and then have you proofread it. SackZement <Talk> 03:50, 1 September 2014 (PDT)

Automatic out-of-date template

I've mocked up a template at my sandbox which would add all translations to a category, specifically:

1. Each language gets its own category.
2. The category uses sort values (i.e. [[Category:Blah|Sort Value]]) to list the age of each translation. These could be language translated and selected however.

My questions are these: Would this template be useful to translators? What kind of age values are you interested in? 1 week, 1 month, 1 year would be a simple example. Is there anything else you would like this template to do? Darkid (Talk | Contribs) 13:26, 5 November 2014 (PST)

Would you all be interested in time since last revision or time between english and language revision? Maybe categories for both? Darkid (Talk | Contribs) 13:31, 5 November 2014 (PST)

It'd be very useful indeed.

Personally, I prefer age measurement in weeks.

I would like to have both categories, though I'll use the english-language-revision more.

Add zis pls { TidB | t | c | wt } 13:58, 5 November 2014 (PST)

 Support Would be helpful, week or month. SackZement <Talk> 15:53, 5 November 2014 (PST)

Alright, well the next question is how to distribute the template on to pages. As I recall, there is a global mediawiki notice at the head of every page, we could piggy-back on to it. Alternately, we can use the infobox, but that will only hit item pages. On the flip side, item pages are the ones that frequently need updates, so...

So listing in categories can only get 10 numbers, so how does 0-9 weeks old sound? Alternately, suggest other headers. Darkid (Talk | Contribs) 16:14, 5 November 2014 (PST)

On hold for 1-2 weeks to verify usefulness/potential harm. Darkid (Talk | Contribs) 20:16, 5 November 2014 (PST)

Duplicate file in Russian

Could a russian translator verify which of the two files 1 and 2 is better translated? Thanks. Darkid (Talk | Contribs) 21:04, 12 March 2015 (PDT)

If you still need this, the second one is more good-lookin' and right. «Gold rush» spelled in Russian like «Голд Раш» is more a slang rather than normal language. The second one uses «Gold Rush(Золотая Лихорадка)», and it's more... official?.. This fits the wiki nicely, I think.
May I have an original file? I'll check the full translation later, I can't see a thing on my phone. Sealed 14:31, 22 April 2015 (PDT)

Delete them all. RADIST 14:38, 22 April 2015 (PDT)

I  Agree, there are either grammar mistakes or too official language. Sealed 08:15, 23 April 2015 (PDT)

Duplicate page in Hungarian

Could a hungarian translator verify which of the two pages 1 or 2 is better translated? The best answer might be to combine the two pages. Darkid (Talk | Contribs) 21:04, 12 March 2015 (PDT)

In my opinion the second page is better than the first page. Spencer 05:00, 9 June 2015 (PDT)

Russian strings in the dictionary

Hi. Yes official translation Strange="странного типа", Unusual="необычного типа". As result, we repeat word "ТИПА". It is not right.

Your version: ... может быть странного типа или необычного типа.

My version: ... может быть странного или необычного типа.

In game: http://prntscr.com/8vm5ub

So why am I not right? :D RADIST | T | C 11:54, 26 October 2015 (PDT)

So to paraphrase, the dictionary seems to have типа on the end of every word like Strange, Unusual, etc. This makes it difficult to use these strings in a list. The options as I see it are:

1. Remove типа from the strings in the dictionary, and have translators add it to the end:

{{Item name|Strange}} или {{Item name|Unusual}} типа

2. Create a template to do the same as above:

{{Russian list|Strange|Unusual}}

3. Not use templates and have users copy strings by hand:

странного или необычного типа

I suggest option 1. Darkid (Talk | Contribs) 19:17, 26 October 2015 (PDT)

For RU Хочу начать с того, с чего и возникла эта дискуссия. Вот. Я не понимаю почему в шаблоне, использующем translation switching, нельзя использовать обычные ссылки? Хотя если посмотреть внимательно можно увидеть их даже в самом этот предложении. Выскажу свою точку зрения. Первый предложенный вариант. Согласно официальному переводу Strange переводится как "странного типа", а Unusual как "необычного типа". Русский язык богат правилами и всевозможными способами построения предложений (что, собственно, не могу сказать про англ.), поэтому в разговорной речи мы можем себе позволить "странного или необычного типа" вместо "странного типа или необычного типа". Что и сделали переводчики игры на сервере переводов. Это обычное «сочинительное сокращение». Если мы изменим в словаре строки "странного типа" и "необычного типа" на "странного" и "необычного" соответственно, то мы: потеряем официальный перевод и более чем 1000 страниц предметов (оружие и аксессуары) придут в негодность из-за изменения инфобоксов (ибо мы получим неверный перевод в списке качеств) - мы получим одну страницу (страница ящиков) с нормальным переводом и кучу с неверным. Изменится шаблон предварительного просмотра вещей странного типа: в названии будет не "Лопата странного типа", а "Лопата странного"... и многие другие шаблоны. Что не есть хорошо. Вообщем, этот вариант отпадает. Создавать шаблон для одной страницы с обычным перечислением однородных членов? Не вижу смысла. Из всех этих вариантов наиболее подходящим будет третий (ну или ссылки, которые я так и не понял почему нельзя:D).

For EN. It is part of Russian grammar -_-. If we remove типа from the strings in the dictionary, we get more than 1,000 pages with incorrect translation (pages using {{Item infobox}}, {{Backpack item}}, {{Strange item info}} and other templates).

e.g. Strange Shotgun:  Дробовик странного типа  Дробовик странного

I don't understand why we can't use links ("[[Strange/ru|странного]] или [[Unusual/ru|необычного типа]]") in template with translation switching?

I choose option 3 or links :D. RADIST | T | C 02:04, 27 October 2015 (PDT)

Ideally, the dictionary would contain the strings for every language. Given that the strings are in use, I don't mind that there are exceptions. Could you write странного или {{Item name|Unusual}}? Darkid (Talk | Contribs) 08:03, 27 October 2015 (PDT)

Notice about translating WebAPI pages

Please do not translate any of the WebAPI pages, or its sub-pages. They are filled with a fair amount of technical jargon, and because of this translations may end up losing the meaning or context. These pages are not really part of the main translation project in any case, as the goal of translating is to allow players in non-English speaking countries to learn about the game itself. Players don't really need to know about the WebAPI itself in detail, so translating those pages is largely wasted effort.

I have added a notice to the Missing Translations reports to this effect, so even if you see WebAPI pages in the list please refrain from translating them. In the meantime, I'll try to find a way to stop the pages from appearing in the reports page at all. -- LordKelvin 12:11, 3 December 2015 (PST)

Finished a "huge" pass of all the weapons templates for all the classes, translations needed

I just finished a big template pass for all the weapons on all the classes. If you have the time, go through and translate the weapon templates that need changing.

Thanks, || twolfe's page || twolfe's talk page 08:41, 5 December 2016 (PST)

Unusual effects will need updating

I'm going to be trying to get details of the new effects up, I'm also updating the weapon effects to say energy orb is no longer obtainable. IDGCaptainRussia (talk) 07:38, 28 October 2018 (UTC)

Serbian Language

I can translate to Serbian but that's the only thing I know, so I'll need some help, hmu — The preceding unsigned comment was added by Nolovedeepweb (talk) • (contribs) 20:06 CEST, 1 June 2020

First of all, please sign your comments using ~~~~.

Second of all, Serbain is not a supported language, sorry about that :( .
GrampaSwood (talk) 19:08, 1 June 2020 (UTC)

Why is Arabic Deprecated?

Why is Arabic Deprecated? What happend? And is there any way to make it undeprecated? Dix (talk) 06:29, 22 November 2022 (UTC)

Hi,

Mainly it is because Valve no longer supports the language, and this wiki being official, we need to stick to the official translations of certain articles, i.e cosmetic items.

Why did Valve decided not to support Arabic? I honestly don’t know, and I’m not sure that a public statement was made explaining why.

Yossef • Talk 08:37, 22 November 2022 (UTC)

Template translation request

Template:List of weapons unable to crit, specifically the Cow Mangler one. — Exaskliri _(they/them) (talk | contribs) 17:17, 10 October 2023 (UTC)