Team Fortress Wiki:Translators' noticeboard

From Team Fortress Wiki
Revision as of 10:15, 31 May 2011 by Jeroenvw (talk | contribs) (The Dutch translations of (Vintage) , (Unusual), etcetera are incorrect.: new section)
Jump to: navigation, search

This page can be used to discuss or announce any topics related to Team Fortress Wiki translation. Translators should watch this page to keep track of news or announcements (either by clicking this link 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

Resources

Other

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 (talkcontrib) 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 (talkcontrib) 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 (talkcontrib) 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 (talkcontrib) 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... -- Alex2539 -- 12:42, 2 November 2010 (UTC)

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)

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 --Healing Patofan Pew pew! 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)

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)

Pictogram comment.png 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)
Pictogram plus.png 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. User ScatmanJohn Logo.pngScatman JohnUser Scatmanjohn Jr bob dobbs.png (Talk | Contrib) 11:56, 30 January 2011 (UTC)
Pictogram plus.png Support I really like the idea of pre-adding the {{DISPLAYTITLE}}. It is very useful! VeKoB HauntedHalloweenGift.png 12:07, 30 January 2011 (UTC)
Pictogram comment.png 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.