In order to post to this site, you will need to log in with your wordpress.org account. Your first post may take a while to show up, as it is moderated. Please follow our tag policy when posting.
There have been small changes to several of the core/meta projects lately. A convenient way to check if you need to catch up on a few strings for WordPress core, Browse Happy, Plugin and Theme directory, etc. is to visit https://translate.wordpress.org/stats
Remember to regularly check if you’ve got any pending editor requests. As always, you can find them here (replace YOUR_LOCALE with your locale slug): https://make.wordpress.org/polyglots/tag/YOUR_LOCALE/?resolved=unresolved
Also remember to enable notifications for mentions of your locale on https://profiles.wordpress.org/YOUR-ORG-USERNAME/profile/notifications/
String freeze for WordPress 4.8.1. The release should have happened yesterday, but was postponed by one day. Many locales are already at 100% on the dev project, but quite a few still need to catch up. There are only some 10 strings new, so if you released 4.8, then this is a relatively quick task. Make sure that your locale is at 100%!
Global WordPress Translation Day 3: Call for speakers is open! Time to start planing your local translation event! Welcome to take part in the preparation work and planning. The next meeting for organizers will take place between the first and the second Polyglots weekly meeting Wednesday, August 2, 2017, 11:00 AM GMT+2 on #polyglots-events
It is happening again! On September 30th, international translation day, we’re inviting everyone who wants to help translate WordPress, themes, and plugins into their own language, to join us for a 24-hour global translation sprint!
What are we doing?
For everyone who’s new to the Translation Day events, here’s a summary of what we do during one:
Local translation contributor days – on site events in different cities around the world (last time we had more than 60, let’s beat that!)
Remote support for as many languages as possible to help contributors who would like to join from their home
Everyone who would like to learn how to translate WordPress in their language
New and experienced translation editors – the sessions will have useful tips and advice how to build and maintain a strong translation team
Developers who would like to find translators for their projects – the sessions will teach you how to work with the polyglots team and how to build a translation community around your products
Developers who would like to learn how to prepare their plugins and themes for localization
Everyone who would like to learn how translations work in WordPress and get a general idea of the work of the Polyglots team.
To encourage more translation contributors to get involved and expand the WordPress Polyglots team
To educate existing translation contributors and project translation editors to reduce the amount of waiting strings.
To improve the general understanding of how WordPress deals with translations among the development community
To create strong connections between the plugin and theme authors and the WordPress translation community
To educate translation editors to use the existing tools to improve the experience.
How can you join?
Translate – Just join us on September 30th in your own timezone and translate WordPress or your favorite plugins and themes to your language at http://translate.wordpress.org and perhaps even see your translation go live on your own WordPress site.
Please respond to your editor requests: there are 34 open editor requests. You can find them here (replace YOUR_LOCALE): https://make.wordpress.org/polyglots/tag/YOUR_LOCALE/?resolved=unresolved
String freeze for WordPress 4.8.1. There are a few new strings in WordPress that need to be translated before launch of WordPress 4.8.1. Make sure that your locale is at 100%!
Global WordPress Translation Day 3 Planning: The next meeting for organizers will take place between the first and the second Polyglots weekly meeting Wednesday 09:00 UTC on #polyglots-events
Please respond to your editor requests: there are 24 open editor requests. You can find them here (replace YOUR_LOCALE): https://make.wordpress.org/polyglots/tag/YOUR_LOCALE/?resolved=unresolved
Global WordPress Translation Day 3 Planning: The next meeting for organizers will take place between the first and the second Polyglots weekly meeting Wednesday 09:00 UTC on #polyglots-events – *NOTE, There is a new channel on wordpress.slack.com instead a separate Slack team!*
WordPress Translation Day is a remote conference combined with a global contributor day that happens for 24 hours in as many locations as possible around the world.
It has a 24 hour live streaming schedule with speakers and trainsers from the current Translation teams onboarding new contributors, sharing knowledge, and discussing important issues. One of the goals of the live streaming is to get to know each other and to introduce our teams to other teams across the globe working on the same projects.
The other really important part of WordPress translation Day are the local events – contributor days dedicated to translation, organised by volunteers.
What are the roles of the WordPress Translation Day organisers?
Communication (marketing) volunteers – tasks include event announcements, social media announcements, social media support during the event, spreading the word and helping people find information
Design volunteers – tasks include creating banners, posters and swag for the event
Outreach volunteers – a really important role – direct contact with potential local organisers is really important and our outreach volunteers get in touch with local WordPress event organisers and invite them to oraganise a local event during WordPress translation day. They also provide information and support and put organisers in touch with mentors.
Website/admin volunteers – we have a website we use to market the event wptranslationday.org – it needs content managers and admins to help communicate the event better, upload the schedule, post announcements and speakers, etc.
Live Streaming content volunteers – tasks include putting out call for speakers, speaker selection, finding and mentoring speakers, supporting speakers during the event
Local events mentors – an important role on the team. The local events mentors help event organisers structure and announce their events, get people to attend and advice them on resources they can use during the event
Who can join the team?
Anyone who would like to dedicate time and effort to organise WordPress Translation Day is welcome to join the team. If you have a couple of hours a week to spare, the Polyglots team would really appreciate your help. WordPress Translation Day has been essential for many local communities around the globe and each edition helps more people to understand us better, join us and become a part of the global family.
When is WordPress Translation Day going to be?
That depends on when a team forms. One suggestion is that WordPress Translation Day 3 is on September 30th, International Translation Day.
Further reading
Want to read more about previous Translation Days, watch video and learn how they were organised? Here are a few links:
As you all know, Global WordPress Translation Day 2 is coming on November 12th. We invite everyone involved with the Polyglots team to consider organising or taking a part in a small local meetup dedicated to translating. This is what we call “Local events” and in April we had more than 40 organised in different parts of the world.
I thought I could share some tips on how to organise your local event for those of you who feel hesitant or think it takes special knowledge or experience. It doesn’t really – you can just gather a couple of people with their laptops in a cafe for two hours and who them translate.wordpress.org – that will be enough 🙂
Here are a few more structured ideas:
Organise your local event:
Pick a place (it can be your office, a coffee shop with wifi connection or a co-working space – choose whichever is easiest)
Create a Facebook or a meetup.com event and invite people
Publish the information about your event on your Rosetta site (if you don’t have access, ping us in the comments and we’ll make sure we connect you to the right people). There is a template with an announcement you can use, you can find it here.
On the day of the event:
Start by introducing the Polyglots team and what we do. If you have a room with a projector, here is a sample presentation in English that you can translate to your language with the basics: Download.
Get everyone registered on WordPress.org
Get everyone on Slack and get them to join the #Polyglots channel
On the day, we will be using the website http://wptranslationday.org to show everything shared on Twitter with the hashtag #WPTranslationDay coming from around the world
We would love it if you got the people around you to tweet videos and images from your event – it will be a great way to feel you’re a part of the global initiative.
Once you decide you want to organise an event, please make sure you’ve gone through the following steps:
Tweet about it with the #WPTranslationDay hashtag and mention @translatewp so we can retweet/mention your tweet and let more people know your event is happening
If you have any questions at all, please don’t hesitate to ask them in the comments or on Slack.
Another release of the your favourite extension for your browser!
First of all sorry for the many bugs detected in these days after the release of 1.1.5 (https://make.wordpress.org/polyglots/2016/09/22/glotdict-1-1-5/) but with the implementation of the link of the Consistency tool and with specific glossaries can happen some problems.
So in 10 days I released 5 different release to fix the errors and I hope that this will be not happen anymore, but why?
The extension now validate the HTML that generate, so in the future there will be not anymore strange code in the strings
Now I have a static file with specific strings for test and I have only to switch the languages to test it (before I have to do manually on different glotpress pages)
Little optimizations in the code after the last releases
I hope that for the GWTD GlotDict will be bug free so in case of other bugs don’t hesitate to create a ticket on https://github.com/Mte90/GlotDict/issues with the link that generate issues and the language when happen.
In conclusion thanks to the many users that reported the problems and reported with tickets or by chat, you are amazing guys!
Releases: 162 locales. 69 (+4) locales up to date. 1 (-2) locale behind by minor versions. 8 (±0) locales behind by one major version. 18 (-1) locales behind more than one major version. 59 (±0) locales have a site but never released. 7 (-1) locales don’t have a site.
Translations: 162 (±0) locales. 65 (±0) locales at 100%. 5 (±0) locales have more than 95%. 5 (+1) locales have more than 90%. 26 (-1) locales have more than 50%. 54 (+1) locales have less than 50%. 81 locales have a language pack. 81 locales have no language pack. 7 (-1) locales don’t have a WP project.
(Values in parentheses indicate change against previous week.)
We currently have 8 unresolved editor requests and 9 unresolved locale requests.
Tech Updates
After setting up some first team sites with the O2-theme, Dominik (@ocean90) asks for feedback. One suggestion was to also announce the new team site locally so that everyone is aware it may officially be used. Please feel free to add more feedback in the comments.
The team sites don’t allow to run separate team pages. Users are encouraged to tag posts to makes it easier to distinguish teams.
Request for feedback on GlotPress shortcuts
Members of the Polyglots Team are kindly asked, to briefly give a feedback regarding Shortcuts for copying original strings in GlotPress, see GitHub issue https://github.com/GlotPress/GlotPress-WP/issues/554 .
Receiving contributions for translations
In the past couple of weeks several people asked Petya (@petya) if it’s ok to get paid to translate a plugin or a theme. She clarifies, that translating WordPress, including the free plugins and themes, is a contribution. There are a lot of people who get sponsored to contribute on the project, some people having all of their time covered. If someone would like to sponsor your time to work on a plugin or a theme, that’s perfectly ok. Refusing to translate the core software unless your time is covered would not be great, but also understandable. Not acceptable would be, if a General Translation Editor would refuse to work on a project unless sponsored while at the same time standing in the way of volunteers who would like to translate.
Global WordPress Translation Day 2 (November 12th) – video, website, official announcement, content, local events
If you are organising an event, please add it to the spreadsheet. New events will go into this map: https://drive.google.com/open?id=12Gni4JMfShyWHPqGNwh5-PMneMM&usp=sharing
Our website for the event will be again https://wptranslationday.org/. If anyone would like to help us out with the website, they should raise their hand – we’ll need content management and some tweaks here and there.
We also have our CrowdCast event set up and you can sign up. https://www.crowdcast.io/e/gwtd2
An official announcement for Global WordPress Translation Day 2 is planned for this week. It would be nice to see the announcement find its way to as many Rosetta sites as possible.
Reviving the Asia Pacific meeting
Petya (@petya) talked to Naoko (@nao) about reviving the Asia Pacific weekly Polyglots meeting. Meetings are scheduled for Wednesday, 6am UTC. The next meeting will also be announced via local Slack channels and with an extra post on the Polyglots blog.
Open Discussion
The question came up, how we deal with translations of Child Themes, if the Parent theme has been removed from the WordPress directory. As the theme still may be available through other sources, there are no reasons not to translate their Child Themes. It was considered to add a ticket on Trac for further discussion, if some information about should be displayed on translate.wordpress.org that contributors deal with a child theme.
The first Global WordPress Translation Day was so much fun and made a real difference for us as a global team. That’s why on November 12th, we’re doing it again and everyone can join!
What are we doing?
Local translation contributor days – as many as possible (last time we had more than 50, let’s beat that!)
Remote events for as many languages as possible to support contributors who would like to join from their home
New contributors who would like to learn how to translate WordPress in their language
New and experienced translation editors – the sessions will have useful tips and advice how to build and maintain a strong translation team
Developers who would like to find translators for their projects – the sessions will teach you how to work with the polyglots team and how to build a translation community around your products
Developers who would like to learn how to prepare their plugins and themes for localization
Everyone who would like to learn how translations work in WordPress and get a general idea of the work of the Polyglots team.
When is it happening?
On November 12th, 2016, starting at exactly 0:00 UTC.
To encourage more translation contributors to get involved and expand the WordPress Polyglots team
To improve the general understanding of how WordPress deals with translations among the development community
To create strong connections between the plugin and theme authors and the WordPress translation community
How can you join?
Translate – Just join us on November 12th in your own timezone and translate WordPress or your favourite plugins and themes to your language at http://translate.wordpress.org
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.
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
317 people watched the live streaming sessions
We had live video translation training for 12 languages – Japanese (in that language, by the GTE team) and a general one for all locales in English that I did in the beginning of the day.
There were 22 live sessions overall including development training and translation training, several videos from different WordCamps dedicated to i18n & L10n.
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! 🎈⭐️❤️
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.
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.
We have one slot left in the morning, at 05:00 UTC and considering the number of events in India (amazing!), it would be great if we could have 1 or 2 short training sessions for some of the Indian locales #hi_IN, #mr, #gu, #ml
@gounder@mbigul@gagan0123@gyan Would any of you (or maybe more than one) like to take on the 05:00 UTC slot and maybe do a live streaming session for the locale you’re managing?
From the most downloaded languages currently we’re missing #ar, #ru, #pt_PT, #pt_BR, #zh_CN#zh_TW. There is still time if any of the GTEs would like to get involved – we have a slides template you can use.
Sessions on general L10n, i18n & Polyglots processes
I’ve included several sessions that are not training in the schedule:
Introduction to the WordPress Polyglots team – what we do, how we work, roles, processes (basically the first part of the general template with the roles and capabilities handbook page content featured) – Petya
Joan Boluda: On I18n – Plugin Documentation and Support for the Whole World (Video recording from WCEU 2015)
Plugin/Theme authors: How to get your plugin or theme on translate.wordpress.org (needs a speaker, would you like to do it?)
Plugin/Theme Authors: How to find translators for your plugins and themes (needs a speaker, would you like to do it?)
Plugin/Theme Devs: Internationalisation for WordPress developers – the right way to prepare your themes and plugins for translation with John Blackbourn (John was kind enough to accept my invitation to do a live talk on the proper way to prepare your software for L10n)
Automatic updates or how WordPress updates translations around releases (hopefully Dominik could do that one)
GlotPress as a Plugin – current state and project roadmap (again, I’m hoping Dominik will have time to pick that one)
Remaining time slots – let’s think about how to fill them
We currently have three remaining 1-hour time slots in the schedule – 5am UTC (I’m hoping one of the Indian L10n teams will take that one), 9pm UTC and 10pm UTC.
There are several things we can do with them:
Play sessions from earlier for people in the later time zones (John’s session, the introduction to the Polyglots team session, How to get translators session)
Switch one of the video recordings to the late slots and do a panel with several GTEs talking about how we manage our local translation teams and comparing best practices.
Do something else – ideas welcome!
You’re up!
Feedback on the schedule, suggestions, comments, questions are much needed! If you see the words “needs a speaker, would you like to do it?” next to a session title, you can pick it up! Please raise your hand. I might be able to do all those, but I don’t want to do them all, there are so many of you that have that knowledge!
Thank you all in avance for your amazing work so far for this event. We have more than 920 people signed up on the site to participate in the initiative. Let’s make it worth their while and show the world what a fantastic job we’re doing.
Attention all of you who are taking part in Global WordPress Translation day, and especially those who have signed up to do a live session about translating to their language – this information is important for you.
Download the Slides from the “Slides Template EN” folder, open the slide deck and rename it to “TranslateWordPressIntro_localename” (Example: TranslateWordPressIntro_bg_BG). Slides are available as a keynote template and a pptx template as well.
Some of the slides include notes (at least in Keynote) that explain the content of the slide. Again, you can choose whether or not to make use of those
Translate the slides, modify them in any way you see fit (you don’t need to use them at all if you’d like to do your own), add the local content
Create a folder in the Live Session Slides folder, name it “Slides your_locale” (Example: Slides bg_BG and upload your slides there.
What are the Goals/requirements of the live streaming sessions?
Each session can be from 30min to 1h. If you need more than 1h, please let us know in the comments so we can plan for that in the schedule
Objectives:
Introduce the Polyglots team and the process of WordPress L10n
Introduce the local team and explain the hierarchy and how people get involved
Introduce to the translation tools
Introduce to the local glossary
Introduce to the local style guide
Give examples of several things that people often get wrong
Demo the process in action
Goal: Make it easier for people to understand the specifics of translating in your language.
Goal: Use the live streaming session video for easier onboarding of new contributors after April 24th
What if I haven’t signed up for a live session yet? Can I still do it?
Yes! You absolutely can – we have 10 more sessions to fill the 24 hours we have on April 24th. Here’s what you should do:
Sign your name in there and fill out the rest of the columns: timezone, preferred time for session, links to local resources (glossary, style guide) (@garyj, looking at you)
Choose whether or not to use the slide deck template and follow the steps in the first paragraph above.
