Indian PolyGlots’ Style Guide Initiative

A couple of polyglots here in India met today on a hangout to start working on creating Style Guides & Glossaries and improve the quality of translations in general, for Indian languages. The whole conversation was public and live and is available here:

It went on for 2 hours so I’m summarising our discussion here.

Who was present?
@fitehal, @adityakane, @gounder, @chandrapatel, @jaymanpandya, @prathameshp, @jitesh @tushonline, @patilswapnilv and @vivekjain. @jiteshpatil & @garv497 couldn’t connect due to technical reasons.

What was discussed?
How to get started with creating Style Guides?
During the discussion we realised that we need to work on two fronts:

  1. Native speaker outreach
    1. We realised that we need to reach out to more native language users of WordPress and take WordPress to potential local language users.
    2. We need to involve technical experts of local languages for guidance and direction for good style guides
  2. We need to start hacking a style guide alongside so that we have something to work on and improve.

For this to happen, we need demo WordPress websites so that non-technical users not adept at setting up WordPress can access and experience the dashboard in their language.

Users who write in local languages but use the dashboard in English (because the local version is not very usable) can also check things out and provide useful feedback.

With these demo sites, we can run outreach activities for writers, journalists, bloggers and academia of each language to get them involved in translations over the long run.

We’ll setup scripts and instructions for orienting new users, recording user tests (screencasts) and collecting useful actionable feedback. We intend to use these recordings to improve translations as well as get information for the style guide.

Since, there are a lot of tasks and activities to do, it was decided that we’ll proceed step by step and we decided to start with just two tasks:

1. Demo Sites for User Testing

  • Create a resource on where demo versions of WordPress will be installed and available for everyone to test WordPress in their language.
  • Initially (and since only polyglots from these languages committed), only Marathi (#mr_IN) , Gujarati (#gu_IN) & Hindi (#hi_IN) will be set up. Other languages can be setup on request.
  • These demos will be reset periodically to a clean install.
  • @gounder and @patilswapnilv will take the lead in getting this started.

2. Drafting a common style guide document in English

@adityakane & yours truly will make sure that all the discussions are communicated publicly and keep track of the progress.

Once we finish setting up the demo system and get going on the draft style guide, we’ll have another public hangout to discuss and plan the next steps.

Meanwhile, discussions will continue on the WPIndia slack team’s #polyglots channel (

What can you do?

  1. Get involved in one of the two activities (demo sites for user testing and draft style guides) directly by getting in touch with the leads mentioned above
  2. Join to join in the discussion and see if there’s something else that you’d rather do.

We need hosting

To set up periodically resetting demo sites, we need servers. It was discussed that we call for a sponsor for hosting and we only take it from a hosting company since we need a reliable and sustainable solution for the long run. Please let us know if someone would be happy to help us with that. Till that happens we’re going to host things on our personal servers.

Hi #polyglots I need help…

Hi #polyglots
I need help with Colombian Spanish translation (Learnpress plugin).


Notes from the WP Translation Day Chat on July 19

Below you can find a recap of the GWTD3 (Global WordPress Translation Day) meeting.


  • Global/Schedule
    • Defines goals for the event (GWTD1 : onboard translators and expand the team, GWTD2 : increase PTE and bridge between plugin authors and translators)
    • Review the outcome of community summit and contributor day goals as starting point to help with setting the schedule
    • Other proposals:
      • Streamline onboarding experience for new translators and PTE
      • Reduce the translation waiting list
      • Give the team a stronger presence
  • Website
    • First meeting was held and design started
    • The previous GWTD1 and GWTD2 websites will be archived so they can still be accessed later
  • Comms
    • An announcement post on make/polyglots is being drafted
    • Call for speakers poll needs review, check google docs or on the website. Should stay open until 1-Sept.
    • A handbook page for onboarding local events is being prepared
    • The TranslateWP Twitter account is now accessible by Comms
    • @petya will support comms for the content plan
  • Design
  • Livestream/speakers
    • Some speakers should be invited
    • The crowdcast account has been received

Next meeting

  • Wed 26 July, 09:00 UTC on the global (so just before the 2nd polyglots meeting)

Action items – New

  • @tobifjellner Collect all links to summaries and other useful information of the previous events. Add them in the handbook or on the site
  • @casiepa reachout to organizer that have a meetup on a different date (@casiepa)

Action items – Open from last week

  • @nao to find out about the ‘local mentors’
  • @casiepa to link with ‘Processing’ for live data during the event


#gwtd, #polyglots

Notes from the Polyglots Chat on May 17th

Locale Stats

Releases: 169 (±0) locale, 68 (±0) up to date, 27 (±0) behind by minor versions, 0 (±0) behind by one major version, 14 (±0) behind more than one major version, 51 (±0) have site but never released, 9 (±0) have no site.

Translations: 169 (±0) total, 65 (-1) at 100%, 7 (+2) over 95%, 4 (-1) over 90%, 27 (±0) over 50%, 58 (±0) below 50%, 105 (±0) have a language pack generated, 8 (±0) have no project.

Requests: There are 31 unresolved editor requests out of 776 (+16) total and 4 unresolved locale requests out of 48 (-1) total.

Translators: There are 402 (-4) GTE, 1 548 (+42) PTE and 13 255 (-874) translation contributors. (A account could have multiple roles over different locale)

Site language: 49,682% (+0,062%) of WordPress sites are running a translated WordPress site.

4.8 beta 1

4.7.5 Security and Maintenance Release

Get Involved banner and flyer

  • A page will be added in the WordCamp handbook linking to the templates like this English PDF or this half-page one.
  • A French version is on its way (for WCEU), but if you also want the docs in your own language, add the translation to and the Community Team will create the banners/flyers and share them from that page in the handbook.
  • The details on how to get the final Get-involved flyer will be posted in the community WordCamp handbook, @casiepa will crosspost it in #polyglots Slack for info. For now, let’s do the translation job on our side and when done, ‘ping’ in #community-team to ask for creating the PDFs.

Security White Paper Translation


  • The videos from GWTD2 with ‘acceptable sound quality’ have been published on
  • GWTD3 Call for leads: leads of the event itself and some of the areas of event organization are needed. Mark yourself on the “Team” tab here if you’re interested.

Open Discussion

  • @divyadeepsawhney asked about a way to integrate Google Translate with GlotPress.
    • Make sure not to use machine translation as it is (without manual review)
    • GP Machine Translate plugin (not for use on, external install only)
    • Poedit Pro (paid version) comes with machine translation suggestions, but the downside is that the locale glossary is not integrated since it’s outside of
  • @petya informed that 117 people signed up for WCEU Contributor Day (and 50 as second choice). The first 2 workshops (Intro and GlotPress) will be lead by resp. @glueckpress and @ocean90 . For the 3rd workshop on the glossaries the lead is still to be defined. Any GTE could do this.


#polyglots could you allow me…

#polyglots could you allow me as editor for my plugin

YouCruit Job Listings

for #sv_SE, #en #nb_NO



Notes from the Polyglots chats on January 25

Locale stats

Below stats are dated 2017-01-25 compared to 2017-01-18 (differences between brackets)

Releases: 164 (±0) locale, 68 (+3) up to date, 1 (-2) behind by minor versions, 12 (±0) behind by one major version, 16 (-1) behind more than one major version, 58 (±0) have site but never released, 9 (±0) have no site.
Translations: 164 (±0) total, 64 (±0) at 100%, 4 (±0) over 95%, 3 (±0) over 90%, 31 (±0) over 50%, 55 (±0) below 50%, 87 (±0) have a language pack generated, 7 (±0) have no project.

Requests: There are 21 unresolved editor requests out of 597 (+12) total and 10 unresolved locale requests out of 42 (+1) total.

Translators: There are 483 (±0) GTE, 1 261 (+10) PTE and 12 434 (+139) translation contributors.
(A account could have multiple roles over different locale)

Site language: 51,686% (-0,076%) of the WordPress sites are running in en_US (English (US)).

Outreach Campaign on Rosetta sites

  • See detailed notes on
  • Rosetta sites come very high in search results when people search for WordPress in a specific location and keeping those sites updated with both the localized WordPress important announcement (new versions, basically the content of and local content – events, discussions, etc, can be very beneficial
  • #gu locale manager and translators (@chandrapatel, @afzalmulatani, @mayur) & #ja locale manager (@naokomc) said they plan on posting more about meetups to the blog
  • #hi locale manager (@ankit-k-gupta) added a new editor (@juhise) to help with posting more news to the Rosetta site
  • You want to help us in this campaign ? Please let us know in a comment or on #polyglots

Open Discussion

  • WP for iOS app release is coming up soon, so please check Waiting translations for those locales with the app :
  • Italia (@lasacco) is organizing a PTE day to review pending strings. More info in the next weeks
  • The Greek WordPress Community (@dyrer) has redesigned the website



Agenda for the Polyglots chat on December 14th

Hello Polyglots,

Here’s the agenda for the chat today (please comment with items you’d like to be added in the comments below or bring them to the Open discussion)

  • Locale stats a week after the release
  • Tech update
  • Preparing some end of year stats and a recap
  • Setting up our goal for 2017
  • Changing the rules for inactive locales and GTEs
  • Open discussion

See you all in #polyglots!

  • Wednesday 06:00 UTC in #polyglots
  • Wednesday 11:00 UTC in #polyglots
  • #weekly-meeting-agenda

    #polyglots could you allow me…

    #polyglots could you allow me as editor for my plugin
    for #de_DE and #de_DE formal.


    WP Translation Day organisers FAQ

    Dear #WPTranslationDay event organisers,

    The event is coming this Saturday and on behalf of the whole team, I’d like to say thank you for doing this for the global community and for your local community too. WP Translation Day is our global contributor day, a chance to spend time together, get to know each other and give back to WordPress. It wouldn’t be possible without you all. You are amazing.

    Here is a list of useful tips and frequently asked questions for you. Read it carefully, it has information that’s important for you. If you want to ask anything else, please do it in the #Polyglots channel on Slack or in the #Event-organisers channel on the WPTranslationDay Slack.

    How should I start the day?

    Start your day by explaining to the people at your event how the Polyglots team runs. If you don’t have experience, this slide deck will give you all the information you need: View and download Presentation: Introduction to the WordPress Polyglots team

    Where can I look if I need information about the team?

    The Polyglots handbook is your best friend. You will find an answer to almost any question you have on

    What are the first things new contributors should do during the day?

    Here’s a list of things you need to help new contributors with:

    1. Register an account on
    2. Sign into Slack with their new account from and join the #Polyglots
    3. Login to, find their language and translate

    Check out the First steps and Getting started at contributor day handbook pages for more instruction.

    Which project should we translate?

    Start with WordPress 4.7 development strings and Twenty Seventeen. Our primary goal for this WP Translation Day is to prepare 4.7 for launch.

    When these are done, advise your attendees to start translating a plugin or a theme they are using – it’s always better for them to start with a project they’re familiar with

    Where is the Glossary/Style guide for my language?

    If your locale has a Glossary or Style guide published, it will be listed on this page: Glossaries and style guides per locale

    If your locale doesn’t have a glossary or a style guide, please refer to the General Expectations when translating: You can also look up glossaries of your language by other Open Source projects like GNU or Mozilla.

    Where can I find the WP TranslationDay Live streaming?

    There will be live sessions during translation day on i18n & L10n. The live streaming starts at 0:00 UTC. You can stream it live in your event and it would be lovely if you appeared in one of our community sessions and joined lived from your meetup. See the schedule at and contact us if you’d like to jump in during the live session.

    How can I share what’s going on during my event?

    We gather all the social buzz on so use the hashtag #WPTranslationDay for your pictures and tweets you share and they will appear on the page. We would love to see images, video and info from your local event. The page should aggregate content from all social networks.

    What is the hashtag again?


    Where should I ask if there’s something I don’t know?

    As an event organiser, we highly recommend for you to be in the #Polyglots Slack channel during the day. If you haven’t signed up for Slack yet, please do at

    Continue reading


    Agenda for the Polyglots chats on Nov 2nd

    Hey everyone,

    Here’s a short agenda for the Polyglots chats today:

    • Locale stats
    • 4.7 strings added for translation
    • Global WordPress Translation Day (10 days to go!)
    • Open discussion

    Here’s when the chats start for you:

    Polyglots at the first WordCamp Riga contributor day

    Hey lovelies,

    I thought I’d give a quick recap of the first WordCamp Riga contributor day and what it meant for the Polyglots team.

    It was a pleasure meeting @orvils, one of the Latvian GTEs, in person as well as many other new translation contributors who worked on plugin translations to Latvian, but also German 🙂

    Thank you, everyone, who participated. Here are a few things we did (besides teaching everyone how to translate and translating) and a few that remain on my ToDo list to follow up on:

    • We created a Latvian Team O2 🎉
    • We got the new contributors to join the WordPress Slack team (thanks @ocean90 with your help there, Slack was not keen to send many invites today)
    • We planned adding the Latvian glossary to the Handbook page (attention @mte90, you might want to add it to GlotDict)
    • We planned to add the Latvian Slack team to the Local Slacks handbook page once they change their name and url from WordCampRiga to WordPressLatvia (attn @kristianastala)
    • We talked about the Latvian team potentially organising a meetup for WP Translation Day

    Apart from the Riga related tasks, a few more things I managed to do today:


    This slideshow requires JavaScript.

    Thanks everyone who joined, really loved working with you today <3

    @orvils @edzuss99 @frankleusing @kristianastala @muxahuk1214 @unigunde @frankleusing @armandsdz @peteris and everyone else!


    #contributor-day, #polyglots, #wordcampriga

    Hello Polyglots I am the plugin author for…

    Hello Polyglots!

    I am the plugin author for Timeline Express ( We have a number of great translation editors that we’d like to be able to approve translation for our plugin(s). A few of our users have gone through the plugin, and made the necessary translations – and have been back in contact with me about getting them approved so they can begin to use them.

    Please add the following users as translation editors for their respective locales:

    If you have any questions, just comment here. Thank you!

    #localization, #plugin, #polyglots, #translations

    After the Int’l Polyglots meeting of last Wednesday…

    After the Int’l Polyglots meeting of last Wednesday, I had an interesting conversation with @Nao and @lasacco where we had the chance to illustrate our (the Italian Community) projects regarding Volunteer Mentoring and Glossary.

    Now let me tell you how (the Italian Community) have organized our work.

    First thing, we created Guidelines for the PTEs

    Italian slack

    On the Italian Slack we created four channels:

    #Polyglots per general discussion
    ✓ #live-polyglots for real-time requests for assistance and for periodical collaborative translation live-sessions
    ✓ #gtepte for the weekly meetings and for specific discussions about PTEs and GTEs
    ✓ #live-glossario (a temporary channel) dedicated to the Glossary project, which was
    kept open to the community for the initial, decision-making steps and is now closed as
    it became a “service” channel for the volunteers that are active on the project.

    The Volunteer Mentoring Project

    @lasacco is the lead of this project, which aims at vetting, educating and mentoring the Contributors, to assist them when needed, to supervise (and revise) their translation, with the final mission to bring them to PTE status in the shortest amount of time.

    Within the Mentoring Project lies the “Adopt a theme/plugin” initiative, where we encourage Community members to choose a theme or a plugin of their choice (maybe something they use and are familiar with) and translate it. This way, they begin translating something they feel close to. A GTE – and, in the future, our SuperPTEs – follows them step by step and helps them correct/revise eventual mistakes.

    The mentoring lasts the necessary time for the Contributor to absorb the guidelines and for the Mentor to verify congruity and consistency of translation quality. After that the Contributor becomes PTE for the adopted product.

    A PTE can choose to adopt all the projects (s)he wants: the only limit is the time that (s)he’s willing to dedicate to the task.

    The above motioned SuperPTEs are intermediary figures between GTEs and PTEs.

    They have longer experience and more expertise, are willing to take on the bigger responsibility of larger projects (say, all plugins, etc.), and are also committed to recruit new contributors and propose them the Mentoring Project.

    Basically we’re pulling a virtuous Ponzi scheme to Translate! ☺

    All these operations are managed through an open gDoc accessible by the entire community.

    Someone is always online on Slack and in the #live channel is always possible to get help to solve all doubts. Often the biggest obstacle is understanding correctly the translation’s context, as not always the same term is translated in the same way.

    (This in fact opens the opportunity, for the future, to strengthen the collaboration between Devs and translators: a well prepared document, with references and tags, is a lot easier – and a lot faster – to translate. The goal of having these parts work synergistically is, in our opinion, a healthy ambition)

    The Glossary Project

    Lead of this project is @zetaraffix, who is working at streamlining the procedure that feeds and nourishes the Glossary – which is at the heart of quality and fluidity for any locale – as well as at the evolution of our Rosetta page into the best possible reference for all Italian translators, experts and newbies (adding, for now, style indications, grammar references, tips, links to different resources, and a general Quick Reference Guide, based on @casiepa’s project).

    The decisional process was conducted openly on the dedicated channel, and now the team is working on implementing it.

    The procedure agreed upon will allow a constant and quality-monitored feed to GlotPress through the submission (through a gForm) of proposed terms which will periodically be discussed openly with the community, approved and fed to the GlotPress master, to assist all translator and to further smooth out the process (and the required time).

    Weekly meetings:

    The Italian Polyglots meet every week (Tuesday, 1-2 PM), at the moment these two projects alternate. Often, also, there are extemporaneous meetings on slack to address specific terminology issues.

    These open discussions benefit the entire community and facilitate the interaction with the Devs, who are often key to best understand a strings’ context.

    With our story – at this time – we wish to initiate a mutually beneficial conversation for all locales, to improve and help each other, to find common paths and to share knowledge and experience, and – ultimately – to enhance the process, the translator handbook and the tools available.

    We look forward to your feedback and suggestions. For now, happy translating to all!

    #gte, #italian-polyglots-meetings, #pte, #super-pte

    Hi all I have a couple questions about…

    Hi all, I have a couple questions about translating plugins. I hope this is the right place.

    1) I have a couple dozen or so translations shipping with my plugin. Is there any reason to keep those once translations have been completed at Is there a way to upload the files to make things quicker?

    2) Any idea why “Stable” and “Stable Readme” are greyed out and can’t be translated?

    Thank you,

    #polyglots, #request

    Topic discussions for the Community summit in Philly

    Hey everyone,

    The community summit in Philly is two weeks away and it would be good to create a list of topics we’d like to be discussed during the two days of the event.

    For those of you who don’t know about the summit, visit the website to learn about it and ask any questions you might have in the comments below.

    The community summit last year in San Francisco included 2 days of intense work and meetings, you can read the notes from some of the discussions – GlotPress, Leads, Rosetta.

    The current list of Polyglots for Philly confirmed by the organisers includes myself, @Nao, @tacoverdo, @atimmer, @francescamarano, @hiwhatsup, @rafaelfunchal, @stephdau and Rocio (@_dorsvenabili).

    The community summit is a good place for us to interact with the other make teams, especially the meta team and the core team, but also to collaborate with the docs team and plan the improvements we’d like to see in the year to follow.

    It would be amazing to have the most active of you on Slack during those two days so that you can at least partially participate in the discussions.

    Here’s what’s on my list. Please add the ideas you have and we can form discussion topics to suggest for the unconference days.

    Rosetta sites

    To Do

    • P2s for Rosetta sites for community and translation teams. There’s a pilot one on the site, but it’s time we bring that to the rest of the locale sites
    • Outreach campaign to encourage more people to get involved with updating their Rosetta sites. With the new user roles coming, there’s no reason more editors can’t be recruited so that the sites are always up to date with new information on the latest releases as well as community events information. See the Romanian and Italian sites as examples.

    Discussion topic suggestion:

    • Improving Rosetta sites – the tools we need

    Three main things as a focus here to discuss, get a status update on or plan:

    • Translation memory
    • Notifications for translation editors
    • Feedback to contributors (edit with feedback, reject with feedback)
    • Glossaries across projects

    Discussion topic suggestion:

    • Scaling – with 30k plugins in the repository, what can we do to help translation editors and new contributors?


    To Do

    • Improving documentation for plugin authors regarding their plugins on
    • Improving the Polyglots handbook – there are still pages that need expanding, more information, screenshots.

    Discussion topic suggestion:

    • Translating contributor handbooks – can we translate the handbooks to make it easier for new contributors? How?
    • Translating WordPress Documentation – tools, ways, etc.

    Please add your suggestions and comments.

    #community-summit, #discussion, #polyglots, #wcus