Hi WP team, is it…

Hi WP team, is it possible to add the swiss french language in the next wp release ?
It’s basiclly the same as french (France) but would be really helpfull for SEO etc to be able to choose for fr-CH instead of fr-FR.

Thank you



Hello I have been regularly contributing in Urdu…

Hello! I have been regularly contributing in Urdu translation. I have more then 500 translations. and 493 are waiting for approval, I want to be editor for Urdu and wish to complete Urdu translation ASAP

#editor-requests, #locale-requests, #request, #translation, #urdu

Global WordPress Translation Day – recap & results

We did it 🏆 Last weekend was the first ever Global WordPress Translation Day and it happened just as planned and exceeded our expectation about the overall activity. It was a great first event of what I’m hoping we can turn into a regular series so we can get together more often, bring new people on board and improve our processes, documentation and, let’s face it… our contributing experience overall.

What we did

  1. 24 hours of live streaming sessions inspired by WordSesh but focused on translation training and developer training on i18n & L10n
  2. Local contributor days in as many cities in the world as we could get to commit solely focused on translating WordPress

How we organised it

Everything was organised in an open Google Spreadsheet that everyone had access to edit. The ultimate exercise in trust and initiative as everyone could jump on and add information/change/ask questions.

The Website

We are all extremely grateful to Scott Basgaard who allowed us to basically clone the last WordSesh site and change the content, so http://wptranslationday.org is basically WordSesh with our colours and content. The Website allowed us to have a real marketing campaign and in less than 3 weeks we got more than 1300 people to sign up to take part of the event.

24 hours of live streaming sessions

For the live streaming sessions, we used CrowdCast, which worked beautifully and I would highly recommend if we ever decide to do webinars or any online training.

All the videos from the sessions are here: https://www.crowdcast.io/e/wptranslationday/ and will stay available to watch (can also be downloaded). The developer sessions and the translation training will all go on WordPress.TV as well and will be used in various documentation parts of make.wordpress.org

We had several sessions aimed at plugin and theme developers whether it was to advise them on how to find translators for their themes and plugins or to teach them how to prepare them  for L10n

I also want to thank Danielle who jumped on the schedule last minute to wake us up and chat about his great browser extension GlotDict that helps translators get a global Glossary. You can watch the session here. here.

Local events – stand alone contributor days dedicated to translating WordPress


  • 39 local events on 4 continents 🌍🌎🌏
  • 11 remote events in different locations 💻
  • 448 people submitting translations 👏
  • 153 people got a polyglots badge, which means they submitted their first strings ever during that day! 🎈⭐️❤️

View the map 🗺

Results 🤘🏻

As of Monday morning, these are the final stats for the day that Dominik pulled from translate.w.org:

How much got translated 📈

A infographic by Raffaella Isidori

  • 40350 strings translated during the 24 hours
  • 597 projects on translate.wordpress.org had new strings submitted
  • 53 locales got updated with new translations (just for WordPress, not including plugins and themes)
  • 17 new translation editors were added across different locales
  • 15 locales got more than 1000 new strings translated

Who translated the most 🏆

55 locales got contributed to during the 24 hours of the sprint, with 15 locales getting more than 1000 strings in. A stunning 597 projects got new strings translated across all projects (WordPress, Plugins and themes). Here’s the data by locale:

English (Canada) en-ca default 4123
Thai th default 3494
Japanese ja default 2922
Turkish tr default 2899
German de default 2896
Bulgarian bg default 2655
French fr default 2315
Dutch nl default 2298
Spanish es default 2219
Italian it default 1961
German (Formal) de formal 1856
Slovak sk default 1738
Marathi mr default 1171
Malayalam ml default 901
Greek el default 782
Croatian hr default 671
Russian ru default 589
Tajik tg default 579
Dutch (Formal) nl formal 527
Venezuelan Spanish es-ve default 451
Afrikaans af default 342
Gujarati gu default 336
Polish pl default 304
Finnish fi default 286
Swedish sv default 255
Chilean Spanish es-cl default 248
Brazilian Portuguese pt-br default 192
Spanish (Mexico) es-mx default 188
Romanian ro default 180
Hindi hi default 148
Norwegian (Bokmål) nb default 130
Hebrew he default 112
Chinese (China) zh-cn default 97
Bengali bn default 80
Serbian sr default 75
Persian fa default 50
Lithuanian lt default 47
Hungarian hu default 34
Kannada kn default 33
Albanian sq default 30
Tibetan bo default 26
Portuguese (Portugal) pt default 20
Chinese (Taiwan) zh-tw default 18
Tamil ta default 15
Javanese jv default 12
Asturian ast default 8
Turkmen tuk default 8
English (UK) en-gb default 7
Ukrainian uk default 7
Emoji art-xemoji default 5
English (Australia) en-au default 5
Azerbaijani (Turkey) az-tr default 2
Vietnamese vi default 2
Czech cs default 1

What else did we improve during the day

  • We got a global list of glossaries and style guides going and it has a lot of resources already
  • We improved our getting started documentation based on feedback we got
  • Many teams got new project translation editors and potential General Translation Editors
  • People from different regions in the same country started talking
  • We raised awareness about our work across the globe


The Buzz

During the day, the hashtag got updates from 202 accounts, 500 posts were sent that generated 945,251 impressions. See all the pictures and all the buss on the official hashtag #WPTranslationDay. Here’s just a small selection of photos.

This slideshow requires JavaScript.

Thank you!

I like to thank several people who made this event possible.

Scott Baasgard, for providing the WordSesh site infrastructure and all the WordSesh know-how for our live streaming sessions. Thank you, Scott, this couldn’t have happened without you. A big thank you to SiteGround, who donated the hosting and domain and provided solid support during the event.

Chantal and Nao, who helped me so much with the site and the communication across teams providing tech support, copy for the internal blog posts and constantly had my back when I needed it.

To each and every one of you who submitted a video for our great promo video and helped spread the word about the event after.

To Yana, who edited the video in one night, Hacko and Rob, who fixed bugs and helped me make sense of the different screencast options.

To all of you wonderful GTEs who committed your time to creating a presentation for the day, we’re paving the way to better documentation and more openness in the team, thank you. To all our other wonderful speakers, John, Nikolay, Claudio, Danielle, who did the technical sessions for theme and plugin developers.

To everyone who jumped into the idea and organised a local or a remote event during the day – you were the backbone of this initiative and we couldn’t have done this without you. You are a true inspiration and I’m sure we’ll get even more events next time thanks to your work.

And to Sonja, who stayed up with me for 25 hours providing support, tea, laughs, taking over when needed and who also spend the whole 25 hours translating to German in between taking care of me.

I love how this event brought us all together and I hope you all agree that we should do it again and soon.

How did the day go for you?

Share your impressions. Would you like to do it again? What should we do differently next time? Let’s make it even better.



#global-wordpress-translation-day, #gwtd, #translation, #wptranslationday

I see the ‘te’ translation is far behind…

I see the ‘te’ translation is far behind, Can i get GTE rights myself, How can i do it because i translated some of words to telugu(te) 4days back but till now no one accepting that. It is always good to have more than 1 GTE for a locale

#locale, #request, #translation, #validator

Hello Polyglots I am the plugin author for…

Hello Polyglots!

I am the plugin author for WP Slimstat. We have a number of great translation editors who contribute .po files via email. Most of them don’t have accounts on WordPress.org. Please add me as translation editor for the following locales, so that I can act as an intermediary between our editors and translate.wp.org:

Thank you in advance!

#editor-requests, #request, #translation

Hi I’m the author of the plugin https…

Hi, I’m the author of the plugin https://wordpress.org/plugins/google-analytics-counter-widget/ and I would ask if anybody is interested in translating it in the following locales:

  • German
  • French
  • Greek
  • Spanish
  • Japanese
  • Russian

and any other you want.

Thank you!

#request, #translation

What are the formatting shortcuts replaced by in…

What are the formatting shortcuts replaced by in the string below? I can’t translate this with a zero object into our language, I must say what is going in its place. Anyone know?

The following formatting shortcuts are replaced when pressing Enter. Press Escape or the Undo button to undo.


#request, #translation

Guys I have done the translation to Chinese…

Guys, I have done the translation to Chinese for bp 2.3 recently, is it a way to merge that in?
there is no response from current chinese team unfortunately.

#chinese, #translation

Hello I write here to request a translation…


I write here to request a translation of WordPress to my local dialect.

I have a team ready and waiting for the request is accepted to start working.

Our goal is to translate WordPress completely before version 4.4.

I hope you accept my request


Locale: ar_MA
Country code: MA
Plural forms: nplurals=6; plural=(n==0 ? 0 : n==1 ? 1 : n==2 ? 2 : n%100>=3 && n%100=11 ? 4 : 5);
Language native name: العربية المغربية
Sub-domain: ar-ma.wordpress.org
Site Title: العربية المغربية
Site Description: ووردبريس بالعربية المغربية
Admin Username(s): sa3idho
Admin Email: contact[at]saidelbakkali.com

#locale, #moroccan-translation, #request, #translation

Request a new locale for Morocco Locale ar…

Request a new locale for Morocco

Locale: ar_MA
Country code: MA
Plural forms: nplurals=6; plural=(n==0 ? 0 : n==1 ? 1 : n==2 ? 2 : n%100>=3 && n%100=11 ? 4 : 5);
Language native name: العربية – المغرب
Sub-domain: ar-ma.wordpress.org
Site Title: المغرب
Site Description: ووردبريس المغرب
Admin Username(s): Anass Rahou
Admin Email: an.rahou[at]gmail.com

#international-sites, #locale, #translation

Wondering about Armenian translation implwmwntation The existing group…

Wondering about Armenian translation implwmwntation. The existing group has been created back in 2011, however, up to now they (consisting of 7 members) have translated 5% of the strings, and the translationquality is mostly awful. Only today I have added the translations for 560 strings in 4.2.x language file but then decided to stop and ask – what if they will approve my work in the same way they do their own translations? In such case I would highly appreciate to become a moderator to have the translation ready ASAP. Regards,

#armenian, #translation

Translating documentation

In last week’s Polyglots chat (logs) we briefly discussed translating documentation, how it was done in the past and how it should be done in the light of localizing the plugin and theme directories and making WordPress.org better fitted for non-English users.

How do we translate documentation now

In the past the Codex has been translated by simply creating new wiki pages and duplicating and translating the content of current pages manually.

The obvious downside of this is that there’s no version control and translators need to check all pages for changes to be able to bring those changes to the translated documents.

Now that Codex is on it’s way to be replaced by the Handbooks, it would be really handy to have those available locally.

So let’s discuss how we can make that happen.

Localizing the handbooks

A couple of options mentioned during the meeting:

“I agree, that it should be handled via WordPress itself, not GlotPress, because you can do quicker previews, add translated screenshots etc. We still can/should show the English text on the same page, maybe side by side so we could track out of date translations.”

  • Adding the handbooks plugin to the locale sites so editors can build there own handbooks – the easiest way to go, but would have no version control so will basically replicate the old way of copy pasting the Codex with no way to track changes in the original documents
  • Adding the handbooks plugin to the locale sites and including an “Import original content” with an active relation of each duplicate with the original. A way for the editors to pull changes from the original (doesn’t have to be automatic, can be done manually, just as long as editors don’t have to go check every page for changes).
  • One option is something @zodiac1978 pointed out is already being done on wordpress.com: “I am doing this for the support pages for wordpress.com. They use a plugin which send you an email for every change (with a revision diff view of the changes). Then we have to manually add these changes to our localised post/page. This could be one way. But much work …”

Let’s discuss the options above and see what ideas the #metai18n team will have too.


#documentation, #documentation-l10n, #translation

Words or characters the string 40480 in the…

Words or characters: the string 40480 in the dev project (change locale code in the slug to see your language) asks to type in “words” if your language’s word count is based on words, and “characters” if that’s what the wordcount is based on (the case of Japanese and Chinese, for example). “Words” or “characters” should NOT be translated from English.

After this question came up for Bengali (BN), I started spotchecking other locales, and took the liberty to fix this for AR, HU, PT-BR, KO, HE, NL, TR, ID, SV (where “words” was translated to the local languages). I did not check/research each language, so if you have a moment, please double-check the string for your locale.

A related question is whether such “developer” rather than “translator” strings should be part of a GlotPress project, or if there is a better way to handle them to minimize the confusion.


Hi Polygots Team I am Bigul from Kerala…

Hi Polygots Team,

I am Bigul from Kerala, India. We have a small WordPress community here in Cochin. We would like to translate WordPress in Malayalam(our mother tongue).

As an initial setup we have translated 2015 WordPress theme and almost completed the 1/4 translation of 2014 theme today( https://translate.wordpress.org/languages/ml ). Before that I have translated few strings of WordPress development and WordPress.com couple of months and still it is pending for approval. Couple of other guys also done the same in past and that is also still waiting for approval.

Therefore please consider me, Nithin and Nebu as Malayalam translation editors. Please note our profile links

https://profiles.wordpress.org/nitkr — Nithin

https://profiles.wordpress.org/nejwrks – Nebu

https://profiles.wordpress.org/mbigul — Myself

Thanks in Advance

With Regards


#malayalam, #malayalam-translation, #translation

Belarusian translation

Hello dear polyglots!

I finished translating https://translate.wordpress.org/projects/wp/dev/bel/default about a month ago, but there is still no response from current validator Agfare.
Is there any way to contact him other than https://bel.wordpress.org/contact/ ?

#belarusian, #translation