User talk:Pols12

Archives

• 2011–2020

Thanks for translation work

Thank you for tweaking the internationalization of a page I had set up. Ad Huikeshoven (talk) 11:39, 21 January 2021 (UTC)

Partagez vos avis sur les améliorations OCR !

Bonjour à tous ! Nous (l'équipe responsable de Consultation des souhaits de la communauté) venons de lancer le projet d'amélioration de l'OCR ! Avec ce projet, nous visons à améliorer l'expérience d'utilisation des outils OCR sur Wikisource. Veuillez vous référer à notre page projet, qui fournit un résumé complet du projet et des principaux problèmes que nous avons identifiés.

Nous serions ravis que vous répondiez aux questions ci-dessous. Vos commentaires sont extrêmement importants pour nous et auront un impact direct sur les choix que nous faisons. Merci d'avance et nous avons hâte de lire vos commentaires ! SGrabarczuk (WMF) 17:20, 26 January 2021 (UTC)

Community Tech/OCR Improvements

Hello,

I translated to French texts of the Community Tech/OCR Improvements page.

The sentence "They also have problems with non-English characters and diacritics." should be "They also have problems with non-latin characters and diacritics."

I gave an alternative picture to c:File:Editlink wikisourcepage.png, but cannot for the other four pictures. Could you correct that ?

Regards,

Cantons-de-l'Est (talk) 13:07, 3 March 2021 (UTC)

Bonjour Cantons-de-l'Est, j’ai fait la correction et j’ai rendu une image régionalisable. Par contre les autres images étaient déjà régionalisables, donc si vous rencontrez encore un problème pour mettre une autre capture d’écran à la place de celles en anglais, redites-moi pour qu’on cherche d’où vient le problème…

PS: Pour info, l’omission de l’accent circonflexe (dans reconnaitre…) était volontaire, en application des rectifications de 1990. -- Pols12 (talk) 20:14, 3 March 2021 (UTC)

My work related to translation

Hi, I'll be more careful in the future. Thanks also for given page, it will mean a lot to me in my future work. Best regards, Kizule (talk) 15:30, 31 March 2021 (UTC)

Thank you for your translation work

Hi Pols12, thank you for your help with translation markup on Universal Code of Conduct meta pages. I really appreciate it, and I am learning a lot from you. I had been referring to this documentation and looking at how others have marked up various pages, but I have clearly not followed all best practices. I will be sure to refer to Meta:Internationalization guidelines going forward. It is very useful. All the best, BChoo (WMF) (talk) 21:31, 31 March 2021 (UTC)

Hi BChoo, I’m happy to read you consider my edits as useful and not as anoying. I sometimes nitpick a little, but most of my edits are to ensure wikitext will not be broken in translations (mainly because new syntax adds markers for every non-translated units). -- Pols12 (talk) 22:22, 31 March 2021 (UTC)

They're not annoying, only helpful. In fact, Xeno just asked me a question that I thought you might know the answer to. On Universal Code of Conduct/2021 consultations, there is a cross-wiki link to Foundation wiki version of the UCoC. It's currently [[<tvar|1>Foundation:Special:MyLanguage/Universal Code of Conduct</>|Universal Code of Conduct (UCoC)]]. This is a problem because most people do not have Foundation wiki accounts, which means Special:MyLanguage will not be relevant. So we do not want to put the link target inside tvar, but we do not know how to code this correctly. Do you know how to do this? BChoo (WMF) (talk) 00:16, 1 April 2021 (UTC)

Thanks from me too! My thought was to remove Special:MyLanguage, put add /en outside the tvar and translators can put their Lang code there during translate.

[[<tvar|1>Foundation:Universal Code of Conduct/</>en|Universal Code of Conduct (UCoC)]]

Would that work? Or is there such a template that you can transclude with Special:MyLanguage to give the lang code there? Xeno (WMF) (talk) 00:23, 1 April 2021 (UTC)

Actually, there is no ideal way to achieve this. {{#translation:}} returns /en with appropriate language code, but we can’t use this trick because Consultation page may be translated in a language which would not be recognized by Foundation page.

I think the only solution is to fully remove the tvar and to write a message in /qqq documentation asking translators to localize the link manually when possible.

Guessing language for logged-off users is a feature which is requested for years… -- Pols12 (talk) 01:03, 1 April 2021 (UTC)

Thank you for the tips and the phabricator link! BChoo (WMF) (talk) 20:58, 1 April 2021 (UTC)

• Pols12, would you mind taking a look at Special:Diff/21303090 and letting me know if this is a reasonable solution (marking for translation if so)? I suppose a failure would be where the consultations page exists but not the discussions page. This would be rare. Xeno (WMF) (talk) 23:52, 5 April 2021 (UTC)

  I've tried it anyhow. Is there a good way to internationalize that template call? Xeno (WMF) (talk) 00:46, 6 April 2021 (UTC)

  I have introduced an {{#ifexist}} hack, this should workaround the rare case you thought. Else, no special needs: I have just replaced obsolete {{PAGECONTENTLANGUAGE}} with {{PAGELANGUAGE}} magic word. Pols12 (talk) 01:18, 6 April 2021 (UTC)

  Beautiful! Thank you. A button will also appear here: Universal Code of Conduct/2021 consultations/Discussion. Xeno (WMF) (talk) 01:26, 6 April 2021 (UTC)

• I hope my questions aren't bothersome :) So this special:Diff/21305954 was not possible and I had to paste copies of T22 into T29: was there a better way to re-use T:22 here? Xeno (WMF) (talk) 20:18, 7 April 2021 (UTC)

  If it used many times, eventually on several pages, the best is to create a template. Else, don’t worry about duplicate content: translation memory would help translators. (I agree this could be a nice feature to reuse a same unit in several places, but surely not a development priority.) Pols12 (talk) 22:04, 7 April 2021 (UTC)

Issue with Hausa translation

Tracked in Phabricator:
task T279269

Tracked in Phabricator:
task T279252

Yes, thanks for the tips. We are still working through the possible solutions. Now we are running into an issue with the Hausa translation and I wondered if you ever came across something like this. When trying to publish the translation, it gives an error. SOyeyele (WMF) (talk · contribs) also tried and is getting the same error. What I noticed is their contributions are to a subpage like /ha-latn but I would have expected just /ha. Any insight? Xeno (WMF) (talk) 12:48, 3 April 2021 (UTC)

(I have moved your message in another section to track it easier.)

I just tried to translate to Hausa and I did not meet any error. What error did you encounter? What steps did you follow?

M-Mustapha and SOyeyele, how do you proceed to create this message or this one? The only probable way I have found to achieve this is to manually set uselang URL param to ha-latn which does not technically exist on Wikimedia wikis.

I would be happy to help you, but I have not enough information (exact error message…). --Pols12 (talk) 12:45, 4 April 2021 (UTC)

The error message is “change of state failed” when trying to review and publish. Xeno (WMF) (talk) 19:56, 4 April 2021 (UTC)

You probably manually typed a wrong URL.

1. Visit target page, e.g. Universal Code of Conduct/2021 consultations/Announcement
2. Click on “Translate this page” link which is right above language bar.
3. In top-right corner, you see “Translate to <English>” (<English> may be another language depending on your interface language). Click on “<English>” (or other language) word.
4. Then, in the popping language selector, look for Hausa language (or other one). You can type a language code, e.g. ha.
5. Click on target language.
6. Now, “Translate to Hausa” is written in top-right corner. You can safely translate messages; translations which will be automatically published (it rarely takes more than one minute to be published). Pols12 (talk) 20:12, 4 April 2021 (UTC)

Thanks Pols12 for the explanation, I can confirm you, that is what I have done and I finished the whole translation but it refused to published even when I try to change the state of the translation from Ready to Published it says change of state failed. That's why the contents of the page is still in English. M-Mustapha (talk) 20:28, 4 April 2021 (UTC)

Oh, that’s strange. Can you copy here the full URL which is displayed by your browser when you do these steps, please? Pols12 (talk) 20:39, 4 April 2021 (UTC)

Also, what default language have you configured in your preferences? Pols12 (talk) 21:46, 4 April 2021 (UTC)

Thanks! It worked now. But I didn't select the language through the top right corner option, I just bypass the URL and change the en to ha and it just did. Yes! My default language is English. M-Mustapha (talk) 22:01, 4 April 2021 (UTC)

Thank you M-Mustapha and Pols12 for your ongoing translation work, it is greatly appreciated! There does seem to be a bug report to be made here somewhere. Xeno (WMF) (talk) 00:54, 5 April 2021 (UTC)

I think this is a bug too, I have open two tasks: ULS should not displays prevented languages and TUX should not use a wrong uselang value as fallback, but I am not sure where the problem comes from. I hope Niklas could help. --Pols12 (talk) 13:04, 5 April 2021 (UTC)

Excellent - you described it much better than I would have =) I will follow the progress there. Xeno (WMF) (talk) 13:39, 5 April 2021 (UTC)

au sujet de la page rapport principal

Bonjour Pols12

Apres verification ve voudrais vous remercier pour cette modification, il s'avère quelle plus elégante que la mienne :)

merci d'avance.--Bachounda (WMF) (talk) 10:08, 5 April 2021 (UTC)

Peut-être plus élégante, mais surtout cela corrige l’affichage pour les pages non encore traduites. Par exemple, la traduction en russe n’affichait plus du tout les images. Cela vient du fait que, depuis quelques mois, Translate imbrique les parties non traduites dans des balises pour indiquer la langue. --Pols12 (talk) 13:04, 5 April 2021 (UTC)

Thank you

for your edit comment I have no need to write now as you read my mind ) — Preceding unsigned comment added by 85.238.102.83 (talk) 10 avril 2021 à 10:31 (UTC)

Thank you for fixing this navigation issue! --Pols12 (talk) 12:44, 10 April 2021 (UTC)

marquer des pages pour traduction

Cher Pols12, puis-je vous demander de marquer ces pages pour la traduction: Global Council , Movement Charter ou cela serait-il inconvenant ? Merci également pour votre travail =) et meilleures salutations --Christoph Jackel (WMDE) 11:15, 10 April 2021 (UTC)

Avec plaisir : c’est fait ! --Pols12 (talk) 12:44, 10 April 2021 (UTC)

Merci mille fois! :D --Christoph Jackel (WMDE) 15:47, 10 April 2021 (UTC)

Bonjour, j'en ai une autre : QW2021/Friendly Space. J'envisage moi-même de postuler pour un poste de traducteur. Je suppose que vous devez d'abord LIRE le MANUEL (!!!) et ensuite vous pourrez commencer. Me conseillez-vous de le faire? (Pardonnez mon français traduit par une machine, je ne sais que lire, pas écrire) Bien à vous --Christoph Jackel (WMDE) 17:22, 30 April 2021 (UTC)

Done Nous pouvons discuter en anglais si c’est plus facile pour vous, pour éviter les erreurs d’interprétation (je ne vous propose pas l’allemand, je n’aurais malheureusement pas le niveau ).

En effet, il faut lire le manuel qui est sur Mediawiki.org et les recommandations pour Meta-Wiki. Mais pas besoin d’être administrateur de traduction pour préparer une page (ajouter les balises) : ça permet de « s’entrainer » avant de demander le statut. Je vous conseille de préparer quelques pages (peut-être aurais-je dû vous laisser celle-là), je ferai la relecture avec plaisir. -- Pols12 (talk) 19:23, 30 April 2021 (UTC)

Templates to reduce translation workload

Can you help me understand how to use the {{int|}} template to reduce translation workload, especially on : Universal Code of Conduct/2021 consultations/Enforcementj. The team is hoping to translate this page shortly. BChoo (WMF) is also going to double-check my translation marks, and I have not yet marked for translation. Xeno (WMF) (talk) 16:57, 13 April 2021 (UTC)

Unfortunately, I don’t think {{int}} template can help here: it is used to transclude pages in MediaWiki: namespace, i.e. mainly software interface text. You first have to find interface message id; for this purpose, add ?uselang=qqx to URL where you see the message, then, instead of message in the page, you’ll see message id. You can now use the message id as first parameter of {{int}} template. You should exclude the int message from translation (outside of translate> tags, or in a <tvar>).

By the way, to easier prepare a page for translation, you can use Special:PagePreparation. It only works for pages which do not contain any translate markers. Note that this tool has many issues, so a human review is still needed after its use.

I’m reviewing some Enforcement pages, but I’m not sure to review them all. Pols12 (talk) 17:19, 13 April 2021 (UTC)

Finally, in Enforcement page, I have used {{int}} template twice: for Commons and Wikidata site names (since there translations are available in MediaWiki namespace). You can look at “Consultation insights” to see the code. I have also used {{#language}} magic word which allows to translate language names. -- Pols12 (talk) 20:25, 13 April 2021 (UTC)

I was studying those runes myself but I knew you’d have a head start on me! –xeno 20:27, 13 April 2021 (UTC)

Right, that's precisely the markup I was looking for, so people did not have to translate the names of those individual languages [will it be obvious to the translator if, e.g. the language template is missing an output?). Thank you again, I know the team was really happy to have your help today. I will try the Special: page, also. Xeno (WMF) (talk) 01:03, 14 April 2021 (UTC)

I was trying to deploy section transclusion here, hoping that this would display the questions en français, I was sad to see it did not. Is it because it's a talk page? Xeno (WMF) (talk) 02:13, 14 April 2021 (UTC)

I think you confuse {{#language}}, a feature which is a part of Translate extension, and {{int:lang}} which is a hack only available on Meta-Wiki.

• {{#language}} : it displays the page language code used as subpage name, with a slash before, (so /fr only if page name ends with /fr).
• {{int:lang}} displays the user interface language code (so uselang will change its value).

Besides, headings change for each translation, so we must use explicit <section> tags to ensure it works. -- Pols12 (talk) 14:27, 14 April 2021 (UTC)

Perfect, thank you for clarity. Now I want to transclude other portions of the page, but I think we need to mark those parts (they aren't full sections). Really appreciate your ongoing help. Xeno (WMF) (talk) 14:41, 14 April 2021 (UTC)

I guess transcluding section headings is not possible? Xeno (WMF) (talk) 17:34, 14 April 2021 (UTC)

(Special:Diff/21340105 <-- Thank you!) Please take a look at that page and let me know if it seems accessible for someone not familiar with written English, and if anything is missing. A quick logic check would be helpful as well. Xeno (WMF) (talk) 20:04, 14 April 2021 (UTC)

• About Discussion talk page: the frames at the top (nutshell and ombox) are not translated whereas they are the first thing we read. I think they can be removed if the introduction text is enough clear and short. Else this seems me approachable (the best would be to have directly headings translated, but I’m not sure it is feasible). Unfortunately, the whole page is really complex, even for English speakers, I think (because we have to edit each section individually to answers to several questions).
• About your edit in consultation page, that works, but if tags are well placed in transcluded page, the previous code should work too (and is much simpler).

--Pols12 (talk) 21:13, 14 April 2021 (UTC)

Hmm. Even as the page that is transcluded has to serve two separate pages (the parent, and the attendant talk page)? Xeno (WMF) (talk) 23:15, 14 April 2021 (UTC)

I made a change based on your comment. Could the headings be served by a translated template maybe? Or if the marks went inside the === markup on the source page? Xeno (WMF) (talk) 23:03, 14 April 2021 (UTC)

• You’re probably right for transcluded page (you needed a coffee, I need to sleep now ^^)
• Other minor issue: now Discussion page text, which was supposed to be copied, contains many ugly section tags.
  • Besides, I have tested: we indeed must use == {{...}} == syntax if we want both translated heading and editable section.
  • I have thought to another idea using translation units (not a conventional way, nor strong face to time, but it should works) {{User:Pols12/Sandbox/UCC Discussion template|community1}} would produce “How can the effectiveness of anti-harassment efforts be measured?”. Do you think it is interesting to extend and deploy this template?

-- Pols12 (talk) 01:11, 15 April 2021 (UTC)

Yes, precisely that was my thinking. So the TOC and questions would all be in int:lang. Xeno (WMF) (talk) 01:36, 15 April 2021 (UTC)

Nice, so we’re well connected. Pols12 (talk) 01:43, 15 April 2021 (UTC)

I like that solution, while it showed red links here: Special:PermanentLink/21345868. Not sure why. Xeno (WMF) (talk) 17:47, 15 April 2021 (UTC)

Also, I hesitated to replace some of the translation marks in this edit with the language magic when importing from Special:Diff/21334152, wondering if the translations of some language names existed only in that navbox's translations and not available from #languages / mw:Extension:CLDR, but perhaps that's a faulty premise. Xeno (WMF) (talk) 17:47, 15 April 2021 (UTC)

• Unfortunately, we can’t use the template for messages which contain tvars.
• I’m pretty sure there are much more translations available from #languages than here from translators, but they are better contextualized here (e.g. in French we don’t have capital letter for languages, whereas we would maybe add them anyway as list items…).

-- Pols12 (talk) 18:50, 15 April 2021 (UTC)

Translation template with generic re-usable phrases to aid in community engagement

Is there any kind of template solution, kind of like you came up with here, that would allow someone to very easily add common phrases that would be already translated into many languages? I guess this is kind of like what Abstract Wikipedia is trying to accomplish. Xeno (WMF) (talk) 12:18, 16 April 2021 (UTC)

I have already seen this kind of template, but I don’t achieve to find it. We can draft a new template, in a similar way than Template:Years or months ago I have designed yesterday, but it should have a well-defined scope. -- Pols12 (talk) 15:13, 16 April 2021 (UTC)

I guess it would have allowed a template call here: Special:Diff/21363238, to display the word for a stable concept in many languages rather than translating it every time. (I know you've spoken about "translation memory", so maybe this runs counter to that goal, however.)

I also envision it having some simple re-usable ("building block") phrases. Xeno (WMF) (talk) 13:01, 20 April 2021 (UTC)

Yes, I understand, but what is difficult is to find an appropriate template name. For given example (open/closed), I thought to Template:Campaign messages but it is maybe too long, what do you think?

Also, note I just gathered some existing templates inside Category:Common messages. -- Pols12 (talk) 13:55, 20 April 2021 (UTC)

What does Template:Translations do, and could it be adapted? [It does not seem to have any uses, but might be subst only?] "Template:Translated message"? Xeno (WMF) (talk) 14:12, 20 April 2021 (UTC)

{{Translations}} lists translations of an interface message (in MediaWiki namespace) in 22 languages after their language name and language code. It can’t help.

About {{Translated message}}, I am pretty hesitant about creating a general template which could become hudge and misemployed because a lack of context. An English term may have several translations in one language according to the context. But I think you can ask this question on Babylon talk page, or on translators list to have more feedbacks.

Also, note that the community do not reach an agreement about the technical way to create translatable modules (and I think this kind of database would be better handled by a module). -- Pols12 (talk) 14:43, 20 April 2021 (UTC)

Thank you for the pointers, I was sure someone would have tried this before. So are you saying the better to do, would be to have single-purpose templates like those in the category, for very simple and always-the-same words or phrases? ("Please comment below."; "Please contact me with any questions.", etc.) Xeno (WMF) (talk) 14:47, 20 April 2021 (UTC)

Yes, either single-purpose templates, or eventually by-thematics-grouped templates (e.g. a Contact template with “email: $1” “Facebook: $1”, “Mailing list: $1”… wich would be callable as {{contact|email|email{{@}}example.ex}}). Pols12 (talk) 14:55, 20 April 2021 (UTC)

Thank you

		WPWP Campaign Barnstar of Diligence
		Hi Pols12, Thank you so much for the translation support for the Wikipedia Pages Wanting Photos. This is greatly appreciated. T CellsTalk 19:54, 24 April 2021 (UTC)

Moving a translated page

Hello there. First of all, I would like to really thank you for looking after the Movement Strategy pages and helping with the technical fixes that I often miss. Secondly, I would like to either request or ask about moving a translated page. I would like to move Strategy/Wikimedia movement/2018-20/Transition/List of Initiatives, which has over 500 sub-pages, to Movement Strategy/List of Initiatives. Apparently, the move requires an admin, and the only place for move requests I was able to find is here, which seems more about proposals than requests. Should I just submit my request there anyway? --Abbad (WMF) (talk) 06:16, 6 May 2021 (UTC).

Dear Abbad, I have never needed to process this kind of issue, but I think you have to open a task on Phabricator with Wikimedia-Site-requests and Wikimedia-maintenance-script-run tags, because a shell access is needed. -- Pols12 (talk) 21:05, 6 May 2021 (UTC)

Thank you so much for this guidance. I have just created a ticket on Phabricator and will see how it goes from there --Abbad (WMF) (talk) 02:18, 9 May 2021 (UTC).