Howdy again! We’ve actually been meeting the last couple of weeks but someone (aka: me) has been bad about posting meeting notes. If you’re interested in helping with internationalization efforts on WordPress.org, join us on Tuesdays at 12:00 UTC (note the time change for DST).
Here’s a few things that happened in the i18n world over the last couple of weeks:
- Translate: A bunch of things have happened!
- @obenland swooped in with some updates to the project overview for plugins. Here’s an example. But I’ll save you a click: all four sub-projects are now represented on the page in a layout similar to the stats page. We hope to expand that page with other features in the future.
- Speaking of stats, @dd32 updated the Waiting column on the stats page to list waiting strings from all projects. Numbers grew substantially for many locales.
- Every time a plugin gets imported into translate.wordpress.org, the status is now displayed in the #meta-language-packs channel on Slack. Plugins that are already in translate.wordpress.org get re-imported every time there’s a commit in their SVN repository. In the future, initial plugin imports will also be shown in this channel.
- The above item was the last major step to enabling at-will plugin imports into translate.wordpress.org. @ocean90 has fixed a various bugs in the scripts and will be testing the feature (secretly) soon, to see if it will scale. Once he’s comfortable, it’ll roll out to a broader audience and eventually get announced to all plugin authors.
- One of the ways we can ensure it will scale is by setting up a job system and running all of our jobs through that. @dd32 has worked up some initial code for that, which we’re waiting on systems to deploy.
- But that’s not all! A filter UI is now available for larger groups of projects (like plugins and themes). You can see it for themes here.
- Additionally, Dion fixed the issue where themes with
\r\nin there strings were appearing incorrectly.
- Forums: More forum plugins are being ported! @nullbyte has signed up for a few plugins and the table has been updated.
Finally, at today’s chat we talked about #1388, #1044, and #1162, as well as related GlotPress tickets #100 and #494. Specifically, what is the best way to alert translators and translation editors of projects that strings are ready and available to translate?
There are a number of things we can do here, but for now the best course of action is adding a list of contributors/PTEs to the plugin overview (that’s #1388 for those following along). Adding this is a good first step towards future solutions.
While that’s being developed, it’s worth considering the best UX for notifying/contacting translators. The propose GlotPress method is notifications and a notification center, however our use case might be different than the norm – or perhaps we should work with the GlotPress developers on the ideal solution if our use case is normal.
Lots to think about and discuss with the polyglots team and propose to plugin/theme authors.