Commons:Translators' noticeboard

	SpBot archives all sections tagged with {{Section resolved\|1=~~~~}} after 2 days. For the archive overview, see Archive/. The latest archive is located at Archive/2024.

Translators' noticeboard

This is a noticeboard for all matters regarding translation of pages, and a meeting place for the translation administrators. Useful links: Documentation for the translation extension, Tutorial for translators. See also the sisterpage m:Meta talk:Babylon.

Start a new discussion

Shortcut: COM:TN

Templates

See https://commons.wikimedia.org/w/index.php?title=Commons_talk:Template_i18n&diff=prev&oldid=96699679 --Nemo 08:49, 22 May 2013 (UTC)[reply]

On overriding existing translations

Translation administrators should ensure existing translations don't get lost/hidden, or translators will be unhappy and we'll lose them. See the notes I left to Mono and Hazard-SJ. [1] --Nemo 13:06, 23 May 2013 (UTC)[reply]

When using !!FUZZY!! to mark translations we paste into the system as outdated, will it be visible inside the translated page? -- Rillke^(q?) 08:53, 24 May 2013 (UTC)[reply]

They used to be shown in any case, in pink, before bugzilla:44328 (blame Wikidata users). Now, if you add a translation directly with !!FUZZY!!, it's ignored (not reflected on the translation page, available only to translators); if you first save, and then add !!FUZZY!! with a second edit, the translation is marked as outdated but not removed from the translation page. There are many old translations to import and it's clear that translations can always be improved, so I'd recommend to fuzzy only those which are clearly wrong. --Nemo 10:30, 24 May 2013 (UTC)[reply]

Need help...

...for translating Help:SVG.

Do we need to move old translated pages (maybe in some "/old" subpages) without leaving redirects, before starting with the new system? --Ricordi samoa 15:46, 26 May 2013 (UTC)[reply]

Hello, Move the old supages (with laving redirect!) before "starting with the new system". --Steinsplitter (talk) 16:24, 26 May 2013 (UTC)[reply]

I see on Help:SVG is no page-move necessary--Steinsplitter (talk) 16:25, 26 May 2013 (UTC)[reply]

As far as I know FuzzyBot will overwrite the old translations when using the new system and all messages of the old translation must be copied and pasted by hand and optionally marked as !!FUZZY!! (see section above about what happens when). -- Rillke^(q?) 21:59, 26 May 2013 (UTC)[reply]

Help:Preparing a page for translation

Please review Help:Preparing a page for translation. Thanks in advance. -- Rillke^(q?) 23:53, 5 June 2013 (UTC)[reply]

and translation issues

Hi. User:Nemo bis has made several edit requests that fall under the realm of translation admin territory and they should be looked at.

I might be nulling the templates shortly since they are cluttering up the protected edit requests category. Killiondude (talk) 05:20, 3 July 2013 (UTC)[reply]

Todo

Help:Contents - Full historymerge is necessary.
Commons:Project scope - Older translation of als, bn, de and zh-hans are not migrated to new system.

I discouraged translation to both pages. If you find more which are problematic, don't hesitate to add here. Best regards. – Kwj2772 (msg) 10:12, 6 July 2013 (UTC)[reply]

Unordered lists

I've seen several unordered lists that were split just to get new translation units. Is this the desired way to go?

Example:

Before:

* This is how
* The list looked before

which produces the following HTML:

<ul>
<li>This is how</li>
<li>The list looked before</li>
</ul>

After translationadmin-treatment:

* This is how

* The list looked before

which produces the following HTML:

<ul>
<li>This is how</li>
</ul>
<ul>
<li>The list looked before</li>
</ul>

-- Rillke^(q?) 17:39, 10 July 2013 (UTC)[reply]

Categorization of translation

Some pages use the {{LangCat}} which produces subpages of categories (e.g. "Commons policies/de" for German translations of policy pages; contains 5 pages currently). We already have had conventional local category scheme named in local languages (e.g. "Commons Richtlinien" for Gernan; contains 15 pages). We should decide which category to be used in translations. We have three choices:

Keep {{LangCat}} and migrate to new category scheme.
Keep old category scheme by assigning one more translation unit for categorization.
Redirect one category to another.

Your opinion is appreciated. Thank you. – Kwj2772 (msg) 09:48, 19 August 2013 (UTC)[reply]

I

Support first option: we can't keep old category scheme by assigning one more translation unit for categorization because there are no the only way to translate a phrase - two translators will translate the same category name using two ways and you will get duplicates - that's not what we need. We can't forse translators to check if the category was translated somewhere (it seems to be very complicated) as well. Another way is to create monster-like template with switch for ALL cat's and their localized names but IMO that's a bad way which needs a lot of maintance. About redirects - are category redirects working now? AFAIK they were not. --BaseSat (talk) 20:10, 29 September 2013 (UTC)[reply]

License templates

Should we move to the Translate extension all the license templates, e.g. {{PD-RusEmpire}}?

If yes, I suggest a translating-templates-week for TAs and translators -- Ата ^(talk) 11:54, 28 September 2013 (UTC)[reply]

I'm sure that we definitely should move all translateble stuff to the extension. But I see no point in week - actually there is enough work for translating-templates-year but people who want to do the stuff just do it when they want :) But but there are still not all policies pages moved to the new system - IMO we should work on them first. --BaseSat (talk) 20:04, 29 September 2013 (UTC)[reply]

Feedback

Hi there! I tried to modify Commons:Translators' noticeboard/header to enable the translation of the button "Start a new discussion". It's the first time for me... did I work properly? Thanks, — TintoMeches, 22:08, 29 September 2013 (UTC)[reply]

reverted. the template was completely broken (in the extension). --Steinsplitter (talk) 13:58, 21 October 2013 (UTC)[reply]

Commons:Quality images

Hi. I'd like this page to be translatable but on my way to migration it to the new system I faced problems with two sysops. One seems to be a bit ignorant of translation system but showed that COM:LP should be changed slightly to cover exactly a short period of page's 'life' when migration actually happens (when it is renamed from Local name to English name/code but display title hasn't been set yet as TA is not as fast as it would be cool to be). The second pointed that it is one of the most visited pages so he is afraid of ~~Armageddon~~possibility that page might be broken after migration. So I call you all to solve the issue. I'm sure this page shall be translatable and pity outdated and incomplete state in which it's e.g. Ukrainian version is being in a the good illustration of it. It's much easier to translated just words instead of sinking in wiki-code in looking for a word to be translated (and not all translators are good in wiki-code enough to understand what actually shall and might be translated). I myself am one of translators who would never translate via old system. The page is already tagged so any of you may check if it's OK - but do not mark it until moves (on stage of which I was stopped) are done. If there are no objections then I continue my work and have a discussion to link to :) --BaseSat (talk) 14:35, 23 December 2013 (UTC)[reply]

But why translation is impossible without renaming?--Anatoliy (talk) 14:46, 23 December 2013 (UTC)[reply]

@Ahonc: Do not mix translation and marking for translation. The former has nothing to do with what we are discussing, the latter can be done without renaming but then Extension will generate new pages like English/code so history will be splitted between them and pages like Local name. And the problem is that unlike usual pages it would be not possible to merge history of pages like Local name with translation page (those with name like English/code) - the only thing you will be able to do is to redirect them but then you get exactly the same as the was we follow but with splitted history - I hope you understand that it's obviously better to keep history altogether. --BaseSat (talk) 14:58, 23 December 2013 (UTC)[reply]

Anatoliy, Commons:Preparing a page for translation lists the steps done by TAs and also why they do so. -- Rillke^(q?) 15:38, 23 December 2013 (UTC)[reply]

Well, I think it was enough time to object for anybody who wished that. So I'm to done moving today if I have time. --BaseSat (talk) 11:09, 29 December 2013 (UTC)[reply]