Notes from the Polyglots chat on May 20th

LocaleLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in stats:

46 localesLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in are up to date.

5 locales are 100% translated but not yet released for 4.2.2:

  • ID is still at 4.1.1, @ekajogja can we help you in any way to release 4.2.2?
  • Welsh, Polish, Catalan and Chinese are still at 4.2 or 4.2.1 – @gwgan, @jimmyxu, @xavivars, @waclawjacek, @eclare Can we help in any way to release to 4.2.2?

Localized Plugins and Themes directories are here

@dd32 posted earlier today about Plugin and Theme repositories made available on local sites.

  • Theme Directory is available at /themes
  • The Plugins directory is also available at /plugins/
  • Both already have existing projects on The platform for contributing to the translation of WordPress core, themes and plugins. available for localizing
  • DeployDeploy Launching code from a local development environment to the production web server, so that it's available to visitors.  after translation should be requested the same you would do all other rosettaRosetta The code name of the theme for the local WordPress sites (eg. is a “Rosetta” site). All locale specific WordPress sites are referred to as “Rosetta sites.” The name was inspired from the ancient Rosetta Stone, which contained more or less the same text in three different languages. translations.
  • @chantal: Is there any timeframe when it will be possible to translate plugins/themes thru GlotPressGlotPress GlotPress is the translation management software that powers More information is available at
  • @dd32: No hard timeline, most of the groundwork is there for plugins and it’s just waiting for the floodgates to open after more testing, me or @ocean90 will be working on the Themes-in-Glotpress in the next few weeks I expect, not sure how long it’ll take to get that finalised but now that these directories are localised, we kind of want to finish the job

Also from @dd32 about what plugins are going to be available for translations first:
“The “official” plugins in is the start-list, we’ll expand from there, but no definite what we’ll include first. I suspect we’d start with the most popular ones and work the way down the list, biggest impact first. We might also do some smaller plugins first to get the feeling for the process, work out any bugs.. so no, not sure yet”

Localizing Documentation

  • There was a brief discussion around localizing the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the Plugin Directory or can be cost-based plugin from a third-party and theme handbooks and different approaches to that.
  • @dd32: “We’d love to have translations of resources such as that. I personally don’t know of any effort to get that working yet though”
  • The best solution would allow Translation EditorsTranslation Editor Translation editors can approve translations for projects. The GTE (General Translation Editor) and LM (Locale Manager) roles can add new users with the "Project Translation Editor" role that can approve translations for specific projects. There are two different Translation Editor roles: General Translation Editor and Project Translation Editor to easily get notified on changes in the documentation so that those could be applied to localised versions. This means there has to be a direct relation between the original documentation and all the local versions.
  • According to @ocean90 GlotPress is not the way to go for Documentation
  • @zodiac1978 shared a possible solution uses: “I am doing this for the support pages for 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 …”
  • Petya to post a separate post on the P2p2 "p2" is the name of the theme that blogs at use (and o2 is the accompanying plugin). When asked to post something "on the p2" by a member of the Polyglots team, that usually means you're asked to post on the team blog to discuss this with more people and bring it to the attention of the metai18n team.

Polyglots at #wceu

  • A lot of us will be at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe in Seville – raise your hand if you’re one.
  • Let’s discuss a more formal gathering with an agenda for Contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of There are many teams that people can participate in, each with a different focus., June 28
  • Let’s discuss organising a global translation sprint around WordCamp Europe’s contributor day including polyglots who’re not in Seville
  • Petya to post a separate discussion topic on make/polyglots about this

If anyone has anything to add to the notes, feel free to drop it in the comments.

Thanks everyone!


#weekly-meeting-notes, #weekly-meetings