Help talk:Translation switching

From Team Fortress Wiki
Jump to: navigation, search

Policy on new content wrt {{lang}} ?

I am intending to add English text to an existing table. That table contains a mix of {{lang}} and {{common string}}. Is there a policy or convention on this? When I replace the {{common string}}, should I

1) just type in my text


2) do this:
| en = my text

The table has a lot of "unknown", but wherever {{lang}} is used, that template is well populated. Which way is best? Which will best prompt translators to do their translating? (I have some experience with wikipedia, but new to TF2 wiki, and can only make guesses at reading German or Spanish ) Mikado282 (talk) 09:19, 18 January 2014 (PST)

We use the common string template to localize strings that are used by many templates or in several different places in the wiki. These strings are pulled from the dictionary, so that it is easy to update all instances of the string across the wiki. Otherwise, if it's just a one off localized string you use the lang template. Hope that helps. User Moussekateer signature sprite.pngMoussekateer·talk 09:34, 18 January 2014 (PST)
Well, that much was easy to guess about the {{common string}}. I'm thinking if everywhere else on the table there is {{lang}} then maybe I should use {{lang}} even if I set in only one language and leave for others to translate what I'm adding? Mikado282 (talk) 20:58, 18 January 2014 (PST)
Yeah, if you don't have any translations just use {{lang}} and leave the en string in there. If the template's used enough, the translators will get the job done in time. » Cooper Kid (blether) • (contreebs) 03:52, 23 January 2014 (PST)

Order of {{lang}} strings

The current version of the article suggests to have the entries in alphabetical order, like | cs = ... | de = ... | en = ... | ru = .... I think this policy should be slightly altered to always put English en on top, so the order would be something like | en = ... | cs = ... | de = ... | ru = .... This is useful for translators as you don't have to hunt for the original en string and it would be consistent with the language sidebar which also lists English on top and everything else alphabetically. I think this method is already used in some templates already, but it'd be better if we have the proper documentation for it. In case this is implemented, we'd need to change the policy on this page, its example and the example on {{lang}} (and maybe add the policy there as well?) { TidB | t | c } 16:15, 13 August 2018 (UTC)

Since this isn't a particularly controversial change and there's been little activity over a month, I'll go ahead and adapt the guide accordingly { TidB | t | c } 06:56, 1 October 2018 (UTC)