Template talk:Commons policies and guidelines

Latest comment: 26 days ago by Jarekt in topic 147 expensive parser functions
Ways to get help

template riddled with <translate>

edit

If you look at this template on various pages, it's full of translate garbage! Palosirkka (talk) 04:03, 24 May 2013 (UTC)Reply

Thats normal. Please use it on pages that have or can have translations via {{TNT}} (just change {{ to {{TNT|) and just add /en on pages where its not necessary to have translations e.g. on user pages. I doing it but its quite long to do. --BaseSat (talk) 04:52, 24 May 2013 (UTC)Reply
Perhaps you should ask a bot to do so, when you convert a template; or you could use autotranslate maybe? --Nemo 07:47, 24 May 2013 (UTC)Reply
Looks like done -- Ата (talk) 22:30, 24 May 2013 (UTC)Reply
i think autotranslate for navbox is bad idea. On pages that have defined language like translation pages should be placed a template in the same language as the page is in. Autotranslate is good to be used in templates on multilingual pages like forums, noticeboards, talk pages, request pages etc. where it should be like addition to the interface so should have the same language as the interface has rather than page content language. --BaseSat (talk) 22:50, 24 May 2013 (UTC)Reply
edit

This doesn't quite seem the right way to do it: {{Localized link|Commons:General disclaimer|<translate>General disclaimer</translate>}} would make more sense than <translate>{{Localized link|Commons:General disclaimer|General disclaimer}}</translate> IMHO. --Nemo 07:47, 24 May 2013 (UTC)Reply

It's rather useful for a translator to see that this part of text goes with a link on a page, isn't it? -- Ата (talk) 09:18, 24 May 2013 (UTC)Reply
I don't see why. If that's your purpose, by the way, using Special:MyLanguage/... directly would make more sense. --Nemo 22:24, 24 May 2013 (UTC)Reply
sense is in using redirect ll that is shorter but this name is holded here by another template. If we capture it then long "localized link" will be changed to short "ll". :) til that a template should be used to find then where to do change. Also it's common to use ll from meta, wd and other projects with the extension. Experienced translators know what it is, unexperienced ones should read template's doc when they see template that they dont know inside a unit. --BaseSat (talk) 22:42, 24 May 2013 (UTC)Reply

Replace {{Localized link}} with {{Pg}}

edit

If nobody objects, I propose to replace {{Localized link}} with {{Pg}} throughout. The difference is:

  • {{Localized link}} links to a target language version in the user's preferred language, if available, or else falls back on English
  • {{Pg}} links to a target language version in the current page language, then falls back in turn to the user's preferred language or finally to English.

With a lot of languages there are translated versions of many Commons pages, but only the section headings have actually been translated. In effect, most of the content is in English. A Ukrainian-speaking user may understand Russian but not English. If they are reading a Russian version of a page and click on a link in this template,

  • {{Localized link}} would take them to a (mostly English) Ukrainian translation if present, or failing that to the English version
  • {{Pg}} would take them to a Russian version if present, then to the (mostly English) Ukrainian translation if present, and as a last resort to the English version.

Bottom line is that with {{Pg}} users will tend to keep seeing pages in the language they have chosen to read, even if that is not their preferred language, until they choose to change languages. They will not keep being dragged back to English. Comments? Aymatth2 (talk) 17:41, 8 May 2019 (UTC)Reply

Since there were no objections, I have implemented the change. If you select a well-support language, but not your preferred language, you can now click around between versions of the different pages in that language using the template. The current page will be bolded in the template. Aymatth2 (talk) 18:11, 17 May 2019 (UTC)Reply

Commons:Picasa Web Albums files

edit

Hi, dear Wikimedians! How are you? I started translating this page into Belaruisan in Classical orthography (Commons:Picasa Web Albums files/be-tarask). But that image sharing web service had been discontinued in 2016. Is there a need for that licencing help page in this template then, almost 8 years later? Best wishes,--W (talk) 07:28, 22 January 2024 (UTC)Reply

@W: ,   Done I removed the link to Commons:Picasa Web Albums files.--Jarekt (talk) 11:49, 11 October 2024 (UTC)Reply

147 expensive parser functions

edit

This template in the current format adds between 71 and 147 expensive parser functions calls to any page that uses it and causing lua errors for the pages like Commons:Threshold of originality/be-tarask and Commons:Threshold of originality/pt-br. I n order to fix tis issue I am planning on replacing calls to {{Pg}} template with Special:MyLanguage calls. The prototype can be found at Template:Commons policies and guidelines/sandbox. Jarekt (talk) 20:27, 6 October 2024 (UTC)Reply

  Done --Jarekt (talk) 11:49, 11 October 2024 (UTC)Reply
Return to "Commons policies and guidelines" page.