User talk:Pols12/Archive 1

Latest comment: 4 years ago by Alexis Jazz in topic Tech news

Afrikaans | العربية | অসমীয়া | asturianu | azərbaycanca | Boarisch | беларуская | беларуская (тарашкевіца) | български | ပအိုဝ်ႏဘာႏသာႏ | বাংলা | བོད་ཡིག | bosanski | català | کوردی | corsu | čeština | Cymraeg | dansk | Deutsch | Deutsch (Sie-Form) | Zazaki | ދިވެހިބަސް | Ελληνικά | emiliàn e rumagnòl | English | Esperanto | español | eesti | euskara | فارسی | suomi | français | Nordfriisk | Frysk | galego | Alemannisch | ગુજરાતી | עברית | हिन्दी | Fiji Hindi | hrvatski | magyar | հայերեն | interlingua | Bahasa Indonesia | Ido | íslenska | italiano | 日本語 | ქართული | ភាសាខ្មែរ | 한국어 | Qaraqalpaqsha | kar | kurdî | Limburgs | ລາວ | lietuvių | Minangkabau | македонски | മലയാളം | молдовеняскэ | Bahasa Melayu | မြန်မာဘာသာ | مازِرونی | Napulitano | नेपाली | Nederlands | norsk nynorsk | norsk | occitan | Kapampangan | Norfuk / Pitkern | polski | português | português do Brasil | پښتو | Runa Simi | română | русский | संस्कृतम् | sicilianu | سنڌي | Taclḥit | සිංහල | slovenčina | slovenščina | Soomaaliga | shqip | српски / srpski | svenska | ꠍꠤꠟꠐꠤ | ślůnski | தமிழ் | тоҷикӣ | ไทย | Türkmençe | Tagalog | Türkçe | татарча / tatarça | ⵜⴰⵎⴰⵣⵉⵖⵜ  | українська | اردو | oʻzbekcha / ўзбекча | vèneto | Tiếng Việt | 吴语 | 粵語 | 中文(简体) | 中文(繁體) | +/-

Welcome to Meta!

edit

Hello Pols12/Archive 1, and welcome to the Wikimedia Meta-Wiki! This website is for coordinating and discussing all Wikimedia projects. You may find it useful to read our policy page. If you are interested in doing translations, visit Meta:Babylon. You can also leave a note on Meta:Babel or Wikimedia Forum (please read the instructions at the top of the page before posting there). Happy editing!

-- 14:23, 4 May 2011 (UTC)

Tech News

edit

As the year, at least according to the calendar used by Tech News, is drawing to end, I wanted to say thanks for the Tech News translations – both as a person writing Tech News and a Wikimedia editor who cares about the movement. It’s difficult enough to keep track of what’s happening if one speaks English. I’m happy there’s one place to get a weekly update of what’s happening if one doesn’t. The one true international language is translation. Thank you. /Johan (WMF) (talk) 13:43, 16 December 2015 (UTC)Reply

Ready for translation: VisualEditor News #6—2015

edit
 

Hi! This is an invitation to join translators working on the last issue of the VisualEditor multilingual newsletter for 2015, which will be widely delivered on Thursday (end of the day in Europe). Despite being a bit shorter than usual, it does feature important announcements, like the one about the single edit tab system, which people can already test and give feedback about. Thanks a lot for your support, as usual! Elitre (WMF), 14:16, 21 December 2015 (UTC)Reply

PS: Here are some instructions. Please go to the translation page: your language should be available from the drop-down menu on the right. Once you've selected it, you'll see the document in English side by side with any translation work already done in your language. You can add new translations or modify existing ones. Please let us know about difficulties you experience with the translation memory system.

Thank you for your translation help!

edit
  The Translation Barnstar
Thank you very much for your help translating the 2016 Strategy Consultation pages! I am so grateful for the energy you and others have put into helping the consultation reach speakers of as many languages as possible. Kbrown (WMF) (talk) 17:36, 2 February 2016 (UTC)Reply

Ready for translation: VisualEditor News #1—2016

edit
 

Hi! This is an invitation to join translators working on the upcoming issue of the multilingual newsletter for the visual editor, which will be widely delivered as usual on Friday (end of the day in Europe). This time it features, among other things, updates about tables and about the single edit tab system (if you're looking for more translation opportunities, please consider the related overview). Thanks a lot for your support, as usual! Elitre (WMF), 21:37, 22 February 2016 (UTC)Reply

PS: Here are some instructions. Please go to the translation page: your language should be available from the drop-down menu on the right. Once you've selected it, you'll see the document in English side by side with any translation work already done in your language. You can add new translations or modify existing ones. Please let us know about difficulties you experience with the translation memory system.

Should FuzzyBot remove all potentially outdated translations?

edit

Hello, thanks for adding multiple new translations in your language here at Meta-Wiki in recent years. Please join the discussion with your opinion: Should FuzzyBot automatically remove all potentially outdated translations?. Nemo (talk) 12:01, 1 March 2016 (UTC)Reply

Ready for translation: VisualEditor News #2—2016

edit
 

Hi! This is an invitation to join translators working on the upcoming issue of the multilingual newsletter for the visual editor, which will be widely delivered this Sunday (end of the day in Europe). The "future changes" section is particularly interesting this time, and you're welcome to join and spread the word about the Community Taskforce. Thanks a lot for your support, as usual! Elitre (WMF), 10:53, 30 June 2016 (UTC)Reply

PS: Here are some instructions. Please go to the translation page: your language should be available from the drop-down menu on the right. Once you've selected it, you'll see the document in English side by side with any translation work already done in your language. You can add new translations or modify existing ones. Please let us know about difficulties you experience with the translation memory system.

Ready for translation: VisualEditor News #3—2016

edit
 

Hi! This is an invitation to join translators working on the upcoming issue of the multilingual newsletter for the visual editor, which will be widely delivered this weekend. The goal this time is getting translations in over 20 languages, maybe even 25! Thanks a lot for your support, as usual! Elitre (WMF), --08:55, 12 October 2016 (UTC)Reply

PS: Here are some instructions. Please go to the translation page: your language should be available from the drop-down menu on the right. Once you've selected it, you'll see the document in English side by side with any translation work already done in your language. You can add new translations or modify existing ones. Please let us know about difficulties you experience with the translation memory system.

Share your experience and feedback as a Wikimedian in this global survey

edit
  1. This survey is primarily meant to get feedback on the Wikimedia Foundation's current work, not long-term strategy.
  2. Legal stuff: No purchase necessary. Must be the age of majority to participate. Sponsored by the Wikimedia Foundation located at 149 New Montgomery, San Francisco, CA, USA, 94105. Ends January 31, 2017. Void where prohibited. Click here for contest rules.
 

Thanks for your participation during the Inspire Campaign focused on outreach to outside knowledge networks from February 2017. I'm interested in hearing your experience during the campaign, so if you're able, I invite you to complete this brief survey to describe how you contributed to the campaign and how you felt about participating. I want to improve how campaigns are run, so let me know if there's something that could be done better for next time.

Please feel free to let me know on my talk page if you have any questions about the campaign or the survey. Thanks! I JethroBT (WMF) (talk) 18:34, 31 March 2017 (UTC)Reply

(Opt-out instructions)

edit

Hi there, there was a error with the Inspire survey link that caused the survey to be shown as expired, but has now been fixed. The link in the above message should now bring you to the survey. Apologies, I JethroBT (WMF) 19:20, 31 March 2017 (UTC)Reply

Ready for translation: Editing News #1—2017

edit
 

Hi! This is an invitation to join translators working on the upcoming issue of the multilingual newsletter for the visual editor, which will be widely delivered when it's end of Friday in Central Europe, and that features, among other things, rumours about a much-desired syntax highlighting tool... Thanks for your help with this, it feels great to be back. --Elitre (WMF), 17:27, 8 May 2017 (UTC)Reply

PS: Here are some instructions. Please go to the translation page: your language should be available from the drop-down menu on the right. Once you've selected it, you'll see the document in English side by side with any translation work already done in your language. You can add new translations or modify existing ones. Please let us know about difficulties you experience with the translation memory system.

Translation request for New Readers Inspire Campaign-- and thanks!

edit
 

Hi there! I'm contacting you because you've volunteered your time in the past to help translate Inspire Campaigns, or you've expressed an interest about helping to translate. We have a new campaign starting soon about new readers, as we try to encourage contributors to develop ideas on how to inform and invite people to use Wikipedia, especially in places where folks are not aware of it. There are two pages that will need translation:

There will be one additional page for translation that includes the questions we will be asking idea creators when they submit ideas for the campaign. I will notify you when that prose is ready.

Finally, thank you for your support; it's very important to me that these campaigns are accessible to folks across non-English Wikimedia projects, and I wouldn't be able to do that without your time and effort. In appreciation, I'd like to send you a postcard from Chicago where I reside. If you'd like to receive a postcard from me, please e-mail me with an address I contact you at to my work e-mail, cschilling wikimedia.org. I realize this is private information, so if you would prefer not to receive a postcard, that is understandable. Your work to make our projects accessible to everyone is no less appreciated. Please let me know if you have any questions about the prose regarding translation. Thanks, I JethroBT (WMF) 20:33, 8 January 2018 (UTC)Reply

Ready for translation: Editing News #1—2018

edit
 

Hi! This is an invitation to join translators working on the upcoming issue of the multilingual newsletter for the visual editor, which will be widely delivered when it's end of Friday in Central Europe. Thanks in advance for your help with this: getting to interact with fellows so skilled like the translators are is among my favorite things about my job :) Best, Elitre (WMF) 10:29, 27 February 2018 (UTC)Reply

PS: Here are some instructions. Please go to the translation page: your language should be available from the drop-down menu on the right. Once you've selected it, you'll see the document in English side by side with any translation work already done in your language. You can add new translations or modify existing ones. Please let us know about difficulties you experience with the translation memory system.

Share your experience and feedback as a Wikimedian in this global survey

edit
WMF Surveys, 18:36, 29 March 2018 (UTC)Reply

Reminder: Share your feedback in this Wikimedia survey

edit
WMF Surveys, 01:34, 13 April 2018 (UTC)Reply

Your feedback matters: Final reminder to take the global Wikimedia survey

edit
WMF Surveys, 00:43, 20 April 2018 (UTC)Reply

Tech/News/2018/41/fr

edit

Bonjour,
Merci pour tes modifications concernant la Tech News. Vu que c'est la première fois que je traduis les Technews, j'en ai profité pour observer tes corrections. Et je prends note pour ça car en effet, c'était sur le nom des extensions que j'hésitais le plus  . Rome2 (talk) 15:09, 4 October 2018 (UTC)Reply

Bonjour Rome2 !
Oui, je me permets de corriger quelques éléments dans ta traduction. En fait, généralement on copie tous les éléments depuis la traduction de la semaine précédente. Là j’ai laissé quelques modifications que tu avais intégrées parce qu’elles me paraissent tout à fait correctes, mais j’ai quand même changé quelques trucs parce que je trouvais que la traduction habituelle était meilleure.
Pour le nom des extensions, l’idéal est de reprendre le nom traduit sur la page MediaWiki, mais dans notre cas ici, il n’y en a pas. En vérité, c’est toujours très compliqué, et on est jamais tous d’accords entre traducteurs (faut-il garder le nom anglais, traduire littéralement ou inventer un nom qui conserve la métaphore ?). En tout cas, il faut au moins garder la majuscule sur le premier mot du nom de l’extension, pour montrer qu’on a un nom propre. Sur les autres mots du nom de l’extension, il n’y a pas consensus, mais c’est moins important.
Je t’avouerais que dans la traduction, je m’énerve très souvent derrière mon ordinateur parce que je trouve illogique les traductions utilisées par d’autres, mais il faut savoir ranger son orgueil et accepter les modifications des autres. Sinon on a vite fait de tomber dans la guerre d’édition. Pour les termes récurrents, il est toujours possible de discuter sur la page de discussion (PDD) de là où se trouve le terme ou bien sur la PDD du glossaire sur méta ou du glossaire sur Translatewiki.
Allez, je vais terminer ma relecture…  Pols12 (talk) 15:26, 4 October 2018 (UTC)Reply
Il n'y a aucun soucis, c'est comme ça que j'apprends aussi à utiliser les traductions pour les technews en étant corriger et en observant ses corrections  . Donc je me baserai sur la traduction habituelle des autres semaines aussi, ce sera plus simple comme ça. Et c'est noté pour la traduction des extensions, en général, je préfère garder le nom d'origine de l'extension plutôt que traduire, mais c'est pareil si quelqu'un tenait à le traduire vraiment, je n'entrerai pas en guerre d'édition  .
Et merci pour les pages d'aide, je vais regarder tout ça et bonne relecture  .
Rome2 (talk) 15:39, 4 October 2018 (UTC)Reply

Translation: VisualEditor newsletter October 2018

edit

18:20, 24 October 2018 (UTC)

The Affiliate-selected Board seats process welcomes your support

edit
 

Hello. You are receiving this message because you are active in the field of translations <3 The movement needs you! The Nominations phase has started for the ongoing selection process of two Board members, and the timeline is quite tight.

A Translation Central is available to help translators figure out what's been covered and what's left to do. Over the course of the next few weeks, your attention on candidates' profiles is particularly welcome.

While there are four languages that are especially relevant for multiple affiliates (namely Arabic, French, Russian and Spanish), you can also add others. If you can't help: please see if you know anyone in your circle who could, and spread the word :) Thank you! Elitre (WMF) and Facilitators of ASBS 2019, 13:20, 18 April 2019 (UTC)Reply

Conflit de traduction dans les actualités techniques à propos du conseil technique

edit

Bonjour,

Je vois que nous sommes en désaccord sur la traduction du texte « During the meeting, volunteer developers can ask for advice », à propos de la réunion hebdomadaire de conseil technique sur IRC.

  • Ta traduction : « Cette réunion permet aux développeurs bénévoles de demander conseil. » (la première dans 2019/13)
  • Ma traduction à l’origine : « Cette réunion est destinée à permettre aux développeurs bénévoles d’être guidés dans leurs manœuvres. » (la première dans 2018/10)

Ma phrase peut sembler inutilement longue, cependant elle me semble plus appropriée. Il me semble évident qu’une réunion proposée comme actualité technique a pour but d’inviter à parler de technique, or en français :

  • le fait de permettre une chose ne signifie pas qu’on la recherche effectivement ;
  • les conseils et la demande de conseils peuvent s’appréhender en toute indépendance, je ne connais pas de règle qui permettrait d’être sûr·e que les conseils attendus doivent concerner le développement si on ne le répète pas explicitement (et je ne souhaite pas qu’existe une telle règle, je trouverais ça contraignant).

Par conséquent, je trouve que ma proposition est bien plus confortable, plus rassurante pour les lecteurs. Pour être plus précis, ta traduction me renvoie une image du style : « Oui, oui, allez-y, vous pouvez toujours demander conseil ! Vous verrez ce qu’on vous répondra ! » et cela n’offre guère de garanties que j’appellerais « contractuelles », qui permettent de penser qu’en posant une question on obtiendra effectivement une réponse intéressante (c’est le premier point), ni même que les organisateurs de la réunion ne reconnaitront avoir exécuté leurs obligations que si les conseils portent sur le développement (c’est le second point). Ma formule peut sembler insistante, mais plus que d’être oppressante, elle lève toute ambigüité, c’est pourquoi j’aimerais bien te forcer à l’adopter (au terme d’un débat loyal, bien sûr).

L’anglais n’est pas ma langue maternelle, aussi peut-être que ces ambigüités n’existent pas en anglais, ce qui permet aux anglophones d’écrire une phrase beaucoup plus courte. Néanmoins, d’après mon expérience du français, ta phrase demeure bien ambigüe. Il ne s’agit pas d’accuser les salariés de la fondation d’un manque de sérieux, seulement d’offrir aux pauvres bénévoles sans défense des « garanties contractuelles » définies par les mots pour faire face au personnel du géant Wikimedia. Mes mots rendent très clair que les développeurs bénévoles participant à la réunion auront droit à une assistance, et je pense qu’en tant que traducteurs on peut tout à fait se permettre de lever les ambigüités qui apparaitraient dans notre lecture du texte d’origine, au lieu de les reproduire au risque de les créer.

Qu’en penses-tu, toi ?

Aussi, je préfère parler d’être « guidé·e » que d’être conseillé·e, parce que d’après ma vilaine expérience encore (qu’est-ce qu’elle nous emmerde, celle-là), ce qui est un conseil pour une personne n’en est pas forcément pour une autre, et le fait de parler de « conseil » permet donc encore de « s’en sortir » en jouant sur la notion très subjective qu’est le conseil. Alors que s’il s’agit d’être guidé·e, toute personne se présentant dans le contexte dans lequel ce service est fourni et ne manifestant pas d’opposition à l’exécution de ce service ne peut être considérée comme satisfaite que si on l’a effectivement fait avancer dans l’une des trajectoires envisageables (désolé pour cette formule qui peut sembler pompeuse, cependant j’ai eu beau chercher, je n’ai jamais trouvé de meilleure manière de parler des choses). C’est pourquoi encore une fois, je pense que mon choix était susceptible de mettre les lecteurs bien plus à l’aise. Mais à la rigueur, continuer de dire « conseiller » me dérangerait moins (aussi j’ai laissé passer ce remplacement quand il a été introduit, dans 2018/26) ; néanmoins, cela mériterait quand même un petit débat.

Frigory (talk) 02:04, 3 June 2019 (UTC)Reply

@Frigory: Pas très envie de débattre et je n’ai de toutes façons aucune opposition formelle à ta formulation qui est correcte et compréhensible même si je la trouve un peu pompeuse.
Ta traduction est argumentée, mieux vaut s’y tenir pour éviter les éventuelles confusions chez les lecteurs que tu évoques.
D’une manière générale, j’apprécie beaucoup tes traductions que je trouve d’une grande qualité.
Donc, promis, je ne réintègrerai plus ma traduction pour ces annonces de réunions.  Pols12 (talk) 02:29, 3 June 2019 (UTC)Reply
Mais du coup, pourquoi avoir changé !   — merci pour l’adoption.
Ouais, je suis un sacré bâtard parce que non seulement mes formules sont pompeuses, mais en plus j’ai une foule d’arguments pour les justifier, je sais très bien en vanter les mérites ! C’est pas forcément facile à gérer. Il m’arrive cependant de commettre des erreurs, par inattention ou par non-connaissance.
De mon côté, il m’a aussi semblé que tu es le traducteur vers le français autre que moi qui est le plus actif sur la liste des traducteurs, et en même temps celui dont les traductions suscitaient le moins de critiques chez moi. (Il y a d’autres traductions qui se font dans les projets Wikimédia mais je n’ai guère analysé.)
Il ne s’agit pas de « confusions » mais bien d’« inconfort » ou d’insécurité. Imagine-toi à la place du bamboula qui a fait l’effort d’apprendre la langue du colonisateur, mais qui également connait celui-ci pour bien se moquer de lui en jouant sur les mots (cette comparaison est d’autant plus appropriée que la fondation Wikimedia intervient en Afrique). S’il lit une phrase superficielle, ambigüe comme celle que tu avais mise, il risque de ressentir cette insécurité et en conséquence de renoncer à passer à l’acte. S’il ose néanmoins y aller et qu’effectivement on se fout de sa gueule, alors il dira peut-être qu’il est confus pour éviter de froisser, mais la vérité c’est qu’il est oppressé par des Blancs qui font mine qu’ils vont lui proposer des services et qui en fait n’en ont rien à foutre. Tu vois, je pense que c’est le genre de questions qu’il est intéressant de se poser quand on est traducteur. Supposant que la fondation se foutrait effectivement de la gueule des bamboulas, on a ce pouvoir en tant que traducteurs de créer un langage qui va offrir une sécurité au peuple faible, et ses manifestations vaudront de l’or pour lui. Vois l’usage approprié du mot « bamboula », qui consiste à bien insister sur le fait qu’ils sont de toutes manières en position de faiblesse, et donc qu’on n’a pas à s’inquiéter de leur rendre des services ; on peut simplement le concevoir comme un épanouissement.
À plus. — Frigory (talk) 04:13, 3 June 2019 (UTC)Reply

Please translate the Editing newsletter

edit

Would you please translate VisualEditor/Newsletter/2019/July into your favorite language for me? I'd really appreciate it. Whatamidoing (WMF) (talk) 17:30, 19 July 2019 (UTC)Reply

Please

edit

Could you please translate Community Insights/Translation/2019/1-Invitation to program coordinators into French for me? Whatamidoing (WMF) (talk) 19:40, 26 August 2019 (UTC)Reply

Here you go!  Pols12 (talk) 21:29, 26 August 2019 (UTC)Reply
Thank you! (Only three languages to go on my "priority" list. Wish me luck!) Whatamidoing (WMF) (talk) 17:36, 27 August 2019 (UTC)Reply
  Thank you for your help with Community Insights/Translation#Requests for translations. It's really helpful for people to get this information in their language. Whatamidoing (WMF) (talk) 17:13, 19 September 2019 (UTC)Reply

Community Insights Survey

edit

RMaung (WMF) 14:34, 9 September 2019 (UTC)Reply

Reminder: Community Insights Survey

edit

RMaung (WMF) 19:14, 20 September 2019 (UTC)Reply

Thanks for your help

edit
 

Hi there, translator! Here's a little token of appreciation for a recent effort you contributed to. Surprised? Well, the best is yet to come.

  • We'd love to send you this badge as an actual sticker. If you want, you can use this Google Form to communicate your address so we can ship it to you. Note that we will close the form on October 13, 2019, and all data will be removed shortly afterwards. Details about this external site are provided at the top of the form.
  • We also have this badge waiting for you on Wikimedia Space. You can use the form linked above to let us know what your username is on this brand new hub, so that you can get the award there as well. If you don't have an account yet, just go ahead and enjoy joining via Wikimedia login in just a few clicks. (And in case you hadn't heard yet, you can join the community of translators there as well).

Again, thanks for everything you are doing to make this movement a better (and multilingual!) place: please do not hesitate to reach out if you have questions, and I hope to hear from you soon. --Elitre (WMF), 13:03, 28 September 2019 (UTC)Reply

Reminder: Community Insights Survey

edit

RMaung (WMF) 17:04, 4 October 2019 (UTC)Reply

Community Wishlist Survey 2020 needs translations

edit

Hello!

I'm contacting you because you've already translated some messages for the Community Wishlist Survey. We need more translations for the 2020 edition, to create a survey that would serve as many users as we know.

The list below shows our needs by order of importance (most important first):

  1. The invitation sent to communities. It summarizes the process. We plan to distribute it soon on this year target wikis. The more translations we have, the better!
  2. The form for non-English speakers. Anyone should be able to add their wish, no matter which language they speak. Translating this short form is very important to encourage diversity and equity.
  3. The survey itself, where the entire process is described.
  4. The preload form, that provides more context on existing wishes.

Some languages are already covered (maybe by you), but some messages have been updated, and there is always some room for reviewing and polishing messages.

Thank you in advance for your help! This survey can't be successful without your assistance. :)

Trizek (WMF), 14:43, 29 October 2019 (UTC)Reply

Translations:User:Trizek (WMF)/sandbox/WMF research/survey/15/fr

edit

Bonjour

Merci pour les traduction pour User:Trizek (WMF)/sandbox/WMF research/survey/fr. Je vois que tu as utilisé GENDER sur Translations:User:Trizek (WMF)/sandbox/WMF research/survey/15/fr. GENDER ne fonctionnera pas, car le sondage sera créé avec Google Forms. Penses-tu qu'une autre solution soit possible (point média, parenthèses ?

Merci, Trizek (WMF) (talk) 09:12, 15 January 2020 (UTC)Reply

Bonjour Trizek, J’ai reformulé les quelques messages dans lesquels j’avais utilisé GENDER pour qu’il n’y ait plus de problème d’accord (j’aime mieux faire comme ça plutôt que d’utiliser des parenthèses qui rendent difficile la lecture). —Pols12 (talk) 12:13, 15 January 2020 (UTC)Reply

Rollback

edit

Sorry I misclicked while doing RC patrol as my computer hangs at that point, apologies.--Camouflaged Mirage (talk) 13:13, 4 March 2020 (UTC)Reply

No problem, thank you for having posted these explanations.  Pols12 (talk) 13:17, 4 March 2020 (UTC)Reply

How to deal with very very long translation strings ?

edit

Pols12, hello, Thank you always to watch over translators, and how do handle a very large segments in one translation string? I wish to and has been supporting that page, but utterly sad with the present condition. The translation strings are too long, each ”update needed” means I struggle to work on tiny 2inch by 5 inch iPhone, where a batch of over 10 lines is not maneuvreable. Any advise you could point me to? Cheers, --Omotecho (talk) 20:03, 10 March 2020 (UTC)Reply

Hello Omotecho,
Indeed, a good practice is to add an empty line after each header to allow to translate it alone. But we should not use this trick for lists, because this will generate a set of one-item lists instead of a list of several items.
For lists and other kinds of big paragraph, the only solution is to split them introducing
</translate>
<translate>
where you want to split units.
However, we should avoid tweaking translate tags if the page has been already translated, to avoid translation fuzzying.
I hope I have answered to your question.   --Pols12 (talk) 00:00, 11 March 2020 (UTC)Reply

Re: SRG talk

edit

Hi. We know what we are managing. Don't be played. It would also be worthwhile having an understanding of the edits in the broader/32 and this amazing awareness by an IP editor of metawiki systems.

Since when do random IPs appear at the talk page of SRG and start making conversation about globally blocked IPs. If any user wants to be taken seriously at SRG then the user needs to have an account, and be reputable.  — billinghurst sDrewth 22:17, 21 June 2020 (UTC)Reply

Template:Mw

edit

Hi greetings, thank you so much for your helps at Babylon. I've a doubt regrading this template Template:Mw. Would you mind explaining how you upgraded or migrated those old style translations? Please help. Regards.--Path slopu (talk) 09:00, 20 July 2020 (UTC)Reply

Hi Path slopu!
Actually, before we use Translate extension, translators manually used to copy the whole page text into translation pages, replacing English phrases with translated ones. The {{languages}} template was added to access to all translation pages.
We can migrate them adding <translate> tags in source page (as you usually do it). Then, when a translation admin mark the page for translation, all translation are replaced with English source text. So, we have to update each translation thanks to previous page versions kept in page history.
A tool help translation admins to import translation from history: Special:PageMigration. It makes this operation much easier. You can find more information about this tool on MediaWiki wiki. --Pols12 (talk) 14:12, 20 July 2020 (UTC)Reply
Hi greetings, thank you so much for your help especially on migration. Thanks for considering my doubts. Hope you'll help in future also. Thank you. --Path slopu (talk) 15:46, 20 July 2020 (UTC)Reply

Segmentation

edit

Hi greetings, I've made some changes in these pages (Article validation and KML files) for making segmentation effective. I think section heading and content must be separated by a empty line. So I did so. I'm a little worried about whether it will affect the markers. Kindly please check it. Please also mark it for translation. Please help. Regards.--Path slopu (talk) 09:28, 20 July 2020 (UTC)Reply

Hi Path slopu,
Actually, each empty new line makes a new translation unit. Recommendations ask to make translation unit short to translate them easier, but this is not mandatory. It is also recommended to isolate titles to allow translators to translate all titles first, however this is not a technical requirement either. The only goal is to facilitate translator work.
So, since there was not many translations of Article validation, I have marked your changes for translation and updated previous translations, but I have reverted your changes on KML files because several translations were already fully done. (Besides, replacing an empty newline with </translate><translate> is useless since empty new lines already create a new unit.) Regards, --Pols12 (talk) 22:39, 20 July 2020 (UTC)Reply
Hi greetings, thank you very much for your advice and help. Also thank you for considering my request. I'll follow your recommendations in my future edits. Thank you.--Path slopu (talk) 03:53, 21 July 2020 (UTC)Reply

A barnstar for you!

edit
  The Translation Barnstar
This is for your hard works on creating and maintaining translations in Meta wiki. I appreciate your efforts. Keep it up this good work. Thank you. Path slopu (talk) 10:04, 20 July 2020 (UTC)Reply

Discussion

edit

Hi greetings, I've started a discussion regarding tech news delivery at Talk:Tech/News. I humbly request you to participate in it. Thank you.--Path slopu (talk) 04:24, 21 July 2020 (UTC)Reply

Doubt about translation

edit

Hi greetings, I'd like to ask you a doubt about translation in this page Standard archival system/ml. I have translated all the content to Malayalam. But the extension shows there is some outdated translation. I've checked that segment, but there is no problem. I had translated all the content in that segment. Kindly please check this page. Hope you'll help. Regards.--Path slopu (talk) 10:38, 22 July 2020 (UTC)Reply

Hi, thank you so much for fixing the problem. Also, sorry for my silly mistake. Thank you.--Path slopu (talk) 10:43, 22 July 2020 (UTC)Reply
You’re welcome   --Pols12 (talk) 10:45, 22 July 2020 (UTC)Reply

Please help

edit

Hi greetings, I've marked this page for translation (Indic Wikisource Proofreadthon/Message). I added some variables, "Special:MyLanguage"s, etc. Would you mind reviewing my edit? Kindly please help. Thank you.--Path slopu (talk) 06:02, 28 July 2020 (UTC)Reply

Page migration

edit

Hi greetings, I have migrated a page to goings-on/pt. I request you to review my work. I removed some duplicated markups and replaced with English version. Portuguese version seems okay. But I couldn't migrate other language pages to new destinations (Goings-on/vi, Goings-on/pl). The migration tool attempt to create redirect (since they were redirects to Thời sự and Co słychać). What should I do? Kindly please help. Regards. --Path slopu (talk) 07:56, 28 July 2020 (UTC)Reply

I think there is no solution. We should move previous translations to /lang-code subpage before marking the page for translation if we want to use Special:PageMigration to import their content. Now, I believe the only way is to copy and paste manually page contents. --Pols12 (talk) 23:07, 28 July 2020 (UTC)Reply
Hi greetings, thank you so much for your helps. I shall do as you suggested. Hope you'll help in future also. Again thank you for the helps. Regards.--Path slopu (talk) 10:09, 29 July 2020 (UTC)Reply

Page Preparation

edit

Hi greetings, I tried to prepare a page with Special:PagePreparation. But it didn't work. It didn't do anything even after I clicked publish. Kindly please help. Regards--Path slopu (talk) 08:14, 28 July 2020 (UTC)Reply

Withdrawing my statement; now its work properly. It may have been a bug. Sorry for the post.--Path slopu (talk) 11:55, 28 July 2020 (UTC)Reply

SALT

edit

If you want to start using {{SALT}}, a hint: I find it quickest to copy "{{subst:SALT}}" and paste it into every recurring section of the translation. After that I translate the non-recurring sections. My workflow has gotten significantly faster. — Alexis Jazz (talk or ping me) 02:18, 12 October 2020 (UTC)Reply

A request for translation

edit

Hey, thank you for your help with the translation of this message. Could you also take a look at the other messages about the Community Wishlist Survey? Just a few are pending. Thank you! SGrabarczuk (WMF) (talk) 23:29, 13 November 2020 (UTC)Reply

SGrabarczuk (WMF)

18:25, 20 November 2020 (UTC)

Tech news

edit

Just noticed Tech/News/2020/50/fr hasn't been completed yet. I understand if you're busy, but here's a reminder on the off chance you just forgot. In case you were wondering: yes, I used SALT for the last few weeks to minimize the needed effort for translation. Only takes me a minute anyway. — Alexis Jazz (talk or ping me) 23:56, 6 December 2020 (UTC)Reply

SGrabarczuk (WMF)

16:09, 11 December 2020 (UTC)

Return to the user page of "Pols12/Archive 1".