This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
@Liuxinyu970226: First of all, ask a translation administrator here to mark the /i18n page for translation. ;) The translation variables were not perfect: no linguistic content should be within them (in this case translation variable 2 was <tvar|2>{{{2|other uses}}}</>, where “other uses” should be made translatable), and translation variable 3 was unbalanced (it contained six {s and only three }s—in this case, the (disambiguation) text is not to be translated, as it’s part of a page name, which should be the same in all languages). Also, the documentation subpage should have value for the |name= parameter to make the translation button (and existing translations’ listing) work. And parameters should be passed to {{Autotranslate}}, as it cannot magically find them and pass them to the translated subpages. —Tacsipacsi (talk) 16:17, 10 March 2020 (UTC)
Hello, I would like to translate to Italian this page and some other pages. How do I set their translated pages...? I've looked around a bit and it seems different pages have different translation templates, etc, so I don't know how to do them. --Gambo7 (talk)
@Gambo7: I have marked the page for translation. Remember that if you consider that a page should be translated, you can mark it with <translate></translate> and a Translation Admin will see it. Kind regards. LeitoxxWork • Talk • Mail09:11, 16 April 2020 (UTC)
This section is resolved and can be archived. If you disagree, replace this template with your comment. 4nn1l2 (talk) 07:39, 22 April 2020 (UTC)
Proposal: machine translation as a starting point.
An idea came to me that when translating each section of an article, the extension could supply a machine translation to start with, right into the editable text area where we type the translation. The translator would need to just correct it. Maybe that would allow to complete the translations easier and faster, because the translator would not need to type everything from scratch.— Preceding unsigned comment added by Hermolaou (talk • contribs) Mazbel – 13:44, 23 April 2020 (UTC) (UTC)
@Hermolaou: The TranslateWiki extension provides a rather flawed machine translation, where you can work and translate. (See [1]) [1]. In some cases, some pages are updated every year and it is required to translate them again and the same extension keeps those translations, as you can see here ([2]) [2]- and in this, it requires less work when translating them. Mazbel – 14:04, 23 April 2020 (UTC)
The Template:Upload campaign header wle-de uses two translation methods for the same text at the same time. And I do not find how to fix this. The doc page links the /i18n/langcode translations but they are not used. Used are the /langcode translation but they do not use the translate extension. --GPSLeo (talk) 09:25, 2 May 2020 (UTC)
Hi GPSLeo, Thanks for reaching out! The template uses only one translation system, but as it was last year a last moment issue I needed to fix, I forgot to update some of the pages. In all the templates used for Wiki Loves Earth, the same translation method is used. Each year updates are needed, which I make sure they get all done, and with one system in place, the updating can take place easily. i18n makes the situation a lot more complicated when it comes also to technical changes to the infrastructure. Greetings - Romaine (talk) 10:59, 2 May 2020 (UTC)
Recently I made an edit on a page that should remove its translation subpages from a maintenace category. Could a translation admin please get this change propagated to one of the translations, and if it worked, the rest as well? --bdijkstra (overleg) 13:44, 15 May 2020 (UTC)
Great, it worked, thanks. There are about 6 more like this, I will soon fix them in the same way and list them here. --bdijkstra (overleg) 22:02, 15 May 2020 (UTC)
This section is resolved and can be archived. If you disagree, replace this template with your comment. Ameisenigel (talk) 21:54, 17 September 2020 (UTC)
Another page that has to be marked for translation: Commons:File types. I have created an own section for WebP file extension and moved one sentence from WebM (video) into it. — Speravir– 22:06, 21 June 2020 (UTC)
This section is resolved and can be archived. If you disagree, replace this template with your comment. Ameisenigel (talk) 08:34, 19 September 2020 (UTC)
I was wanting to add translations for captions provided in the Category:Media_from_Museo_Nazionale_della_Scienza_e_della_Tecnologia_(Milan) here on Commons, but can't figure out where or how to put them. In the past, so as to not modify the "|description=" field, I've used the "|notes=" section. Items in the Museo Nazionale category don't seem to accept the "notes" field... Is there some way to add a translated description to these items without ruining the template? Oaktree b (talk) 15:51, 8 March 2020 (UTC)
This has to be done with putting the text in the language. This is just {{langcode(e.g. en)|The Text}} I did this for the current English text on the page. --GPSLeo (talk) 09:59, 9 March 2020 (UTC)
This section is resolved and can be archived. If you disagree, replace this template with your comment. Ameisenigel (talk) 19:21, 20 September 2020 (UTC)
For two weeks, I think, I was seeing [[Special:MyLanguage/Commons:Welcome|Wikimedia Commons]] on the userbox and my userpage, and it was just on the English version of the userbox. i.e., the French version was okay. Thanks for the tip. 4nn1l2 (talk) 15:04, 3 November 2020 (UTC)
Oh, I see. The Translate extension went mad when all translations were updated using a server-side script (see also discussion on Meta). In this case deleting the /en page and marking for translation is probably the best workaround. (The two weeks seems to support this, as Nikerabbit’s first message on Meta was around two weeks ago.) —Tacsipacsi (talk) 23:08, 3 November 2020 (UTC)
This section is resolved and can be archived. If you disagree, replace this template with your comment. 4nn1l2 (talk) 16:07, 13 November 2020 (UTC)
@Beland: You can see the translations in the following list. Please note, that there are several cities that have the same name in german and in english, so I do not have listed them in my translations. You can keep their names just like they are.
Völkerkarte Mitteleuropas 1937: Ethnic map of Central Europe 1937
Nordsee: Nort Sea
Ostsee: Baltic Sea
Hannover: Hanover
Köln: Cologne
Luxemburg: Luxembourg
Diedenhofen: Thionville
Hagenau: Haguenau
Straßburg: Strasbourg
Mülhausen: Mulhouse
Luzern: Lucerne
Meran: Merano
Bozen: Bolzano
München: Munich
Tarvis: Tarvisio
Cilli: Celje
Ödenburg: Sopron
Wien: Vienna
Preßburg: Bratislava
Znaim: Znojmo
Krummau: Český Krumlov
Nürnberg: Nuremberg
Pilsen: Plzeň
Eger: Cheb
Aussig: Ústí nad Labem
Meißen: Meissen
Reichenberg: Liberec
Glatz: Kłodzko
Breslau: Wrocław
Liegnitz: Legnica
Fraustadt: Wschowa
Bomst: Babimost
Stettin: Szczecin
Schneidemühl: Piła
Pr. Friedland: Debrzno
Bromberg: Bydgoszcz
Kolberg: Kołobrzeg
Lauenburg: Lębork
Antwerpen: Antwerp
Brüssel: City of Brussels
Dünkrichen: Dunkirk
Lüttich: Liège
Lausan: Lausanne
Genf: Geneva
Fünfkirchen: Pécs
Temeschburg: Timișoara
Sathmar: Satu Mare
Hermannstadt: Sibiu
Kronstadt: Brașov
Schäßburg: Sighișoara
Kremnitz: Kremnica
Käsmark: Kežmarok
Brünn: Brno
Ölmütz: Olomouc
Iglau: Jihlava
Zwittau: Svitavy
Budweis: České Budějovice
Prag: Prague
Bielitz: Bielice
Gleiwitz: Gliwice
Kattowitz: Katowice
Oppeln: Opole
Lemberg: Lviv
Cholm: Kholm
Lodsch: Łódź
Warschau: Warsaw
Posen: Poznań
Gnesen: Gniezno
Kulm: Chełmno
Thorn: Toruń
Allenstein: Olsztyn
Marienburg: Malbork
Danzig: Gdańsk
Elbing: Elbląg
Tilsit: Sovetsk
Pogegen: Pagėgiai
Germanen: Germanic peoples
Deutsche: Germans
Niederländer, Flamen: Dutch and Flemish people
Friesen: Frisians
Engländer: English people
Dänen: Danes
Romanen: Romance peoples
Franzosen, Frankofone: French people
Wallonen: Walloons
Italiener: Italians
Rumänen: Romanians
Rätoromanen: Romansh people
Slawen: Slavs
Ostslawen: East Slavs
Großrussen: Great Russians
Weßrussen: Belarusians
Ukrainer, Ruthenen: Ukrainians, Ruthenians
Südslawen: South Slavs
Slowenen: Slovenes
Windische: Windish
Kroaten: Croats
Serben: Serbs
Bunjevacen: Bunjevci
Schokacen: Šokci
Westslawen: West Slavs
Polen, Goralen: Poles, Gorals
Kaschuben: Kashubians
Masuren: Masurians
Schlonsaken: Silesians
Sorben, Wenden:Sorbs, Wends
Hultschiner: People from Hlučín
Tschechen: Czechs
Slowaken: Slovaks
Balten: Balts
Litauer: Lithuanians
Finno-Ugrier: Finno-Ugric peoples
Magyaren, Szekler: Hungarians, Székelys
Anmerkungen: Notes
Diese Volksgruppen werden vielfach aufgrund der nahen sprachlichen Verwandtschaft zu den Polen gerechnet: These ethnic groups are often counted to the Poles due to their close linguistic relationship
Diese Volksgruppe wird vielfach aufgrund der nahen sprachlichen Verwandtschaft mit den Mähren zu den Tschechen gerechnet: These ethnic group is often counted among the Czechs due to the close linguistic relationship with the Moravians
Diese Volksgruppe wird vielfach aufgrund der nahen sprachlichen Verwandtschaft zu den Slowenen gerechnet: These ethnic group is often counted to the Slovenes due to the close linguistic relationship
Diese Völker werden vielfach aufgrund der nahen sprachlichen Verwandtschaft zur Großgruppe der Serbokroaten zusammengefasst: These groups are often combined to form the large group of Serbo-Croatians due to their close linguistic relationship
@Ameisenigel and Beland: In 1937 Danzig was still Danzig (Free City of Danzig), Breslau was still Breslau (part of Germany at that time), Allenstein was Allenstein (East Prussia), and so on, while Lemberg was Lwów (Poland). Please don’t use anachronic names. (By the way, the German name of Olomouc is Olmütz, with only one umlaut.) —Tacsipacsi (talk) 00:48, 16 November 2020 (UTC)
Tacsipacsi I'm the graphic worker using the translation and thank you for your deep knowledge on this. You write 'and so on', what do you mean? Are there any more names that are wrong in English in the list? I have zero knowledge on this and can only put in what people give me. Please ping me on replay, thanks. --Goran tek-en (talk) 18:39, 27 December 2020 (UTC)
This section is resolved and can be archived. If you disagree, replace this template with your comment. Ameisenigel (talk) 15:28, 3 January 2021 (UTC)
Please find errors - language detection - User:EatchaBot
This section is resolved and can be archived. If you disagree, replace this template with your comment. Ameisenigel (talk) 16:31, 21 March 2021 (UTC)
Wanting to start Greek and Russian translations of some pages.
Hi!
I'm working on some pages in the Category:Digitisation_help. Although the English versions aren't yet complete, I wish I could also start Greek and Russian translations to have in these languages at least what's now available in English. So, to work parallel on English, Russian and Greek versions of these technical guidelines.
These are pages in question:
Help:Converting
Help:Converting DjVu to PDF
Help:Converting PDF to DjVu
Help:Creating an outline for PDF and DjVu
Commons:Extracting images from PDF
Please tell me what's needed to get the permission for translation. Do I need to first completely finish the English versions?
P.S. there also seem to be other ways to make pages in other languages, like Meta:Language_select and {{Lang-NAME}} tag. I'm a bit confused.
@Hermolaou: There’s no such thing that “permission for translation”; rather, a translation administrator takes a technical step (mark for translation) to make the page translatable. I don’t know about any special prerequisites for this, but it’s generally a good thing to finish a page before making it translatable, as if you decide to change things, it makes extra work not only for you as a Russian and Greek translator, but also other translators of other languages.
The language select described at Meta is something like {{Multilingual description}}, another technique suitable for other namespaces like galleries categories etc.; it doesn’t fit well in Commons and Help namespaces. The {{Lang-NAME}} templates are a deprecated way of translating pages (it was invented before the modern translation system came into existence) and should be avoided on newly translated pages. —Tacsipacsi (talk) 10:56, 31 January 2020 (UTC)
The template Image extracted is now converted to iteration, which makes it much simpler and does not need anymore expansions for more files (in the last years it had been expanded several times). Because the template has 28 translations, this page may be the right one for requesting it.
There are yet examples for de, en, es that can be shown in the talk page.
Translation has to be done for the two lines (plural & singular) and for the link names (en: 'Image extraction process' & 'Extracted version'); the file only used for exampleExample i18n.svg is automatically translated. For an example all the parts are manually translated in the Image extracted/sandbox/i18n/ for de and es.
The task for changing comprises: after replacing the sample {{Image extracted/i18n}} by {{Image extracted/sandbox/i18n}},
replacing all translations by that translated from the new sample
As long as these two actions are in progress, the template won't be operable; therefore they should be well prepared and finished swiftly.
-- sarang♥사랑12:13, 21 December 2020 (UTC)
It is a long time since Xmas and I am not current with that template; but as far as I can follow you, you are right. Please care for the needed actions and finish what is necessary. Thank you -- sarang♥사랑16:58, 5 June 2021 (UTC)
I am working on Commons:Brück & Sohn. I see you already added some markings but with the current markings many syntax and links will be displayed for translation too. I will exclude them. The page Commons:WikiProject Postcards already has old style translations they have to become deleted for using the translation function. --GPSLeo (talk) 15:16, 15 July 2020 (UTC)
@GPSLeo: Thanks for your work. I translate the Brück & Sohn in german and send a request for cs. But one question. How can I change the english page as new version. Did I need a privileg as user? Or do I inform a Translation admin every time? -- sk (talk) 16:56, 15 July 2020 (UTC)
@GPSLeo: For the WikiProject Postcards you can delete the old de and fr version. This was only a little helper. -- sk (talk) 16:57, 15 July 2020 (UTC)
I will have a look on Commons:WikiProject Postcards, I never tried to override the old existing translations. Yes after every change the page has to become marked as new version for translation needing the rights. But I think as you are an experienced user and admin on dewiki you could just ask for the right on the Commons:Bureaucrats' noticeboard --GPSLeo (talk) 17:03, 15 July 2020 (UTC)
In COM:TOO I get in the moment more than 30 errors from references. I did a quick look and it seems to me that the transclusion from subpages is not always done correctly, e.g. <ref name="some-individual-string" /> is transcluded, but the actual reference with name="some-individual-string" is not. Could someone with more clues look at this? — Speravir– 19:35, 28 March 2020 (UTC)
@Ameisenigel: Unfortunately there isn't a great way to fix this problem in general. It's not really a translation-related problem, it's a problem with section transclusion and named references in general, so fixing it is really outside the scope of this fairly low-traffic noticeboard. If a named reference is used in a transcluded and non-transcluded section, it can be defined in the transcluded section and re-used elsewhere. If the ref is used in two different transcluded sections, it will have to be defined twice. Reference names in transcluded sections must be unique both on the source page and every page where the section is transcluded. Transclusion with #section-h doesn't work with includeonly/noinclude, so we can't use that. AntiCompositeNumber (talk) 16:48, 5 June 2021 (UTC)
Thank you. --Liuxinyu970226 (talk) 23:28, 10 March 2020 (UTC)
Done 4nn1l2 (talk) 07:39, 22 April 2020 (UTC)
This section is resolved and can be archived. If you disagree, replace this template with your comment. 4nn1l2 (talk) 07:39, 22 April 2020 (UTC) 
.png){kind=link}
