FYI that following the release of WordPress 4.3, we’ve ran an import from translate.wordpress.org for all locales, for new translations. This only affects strings that weren’t previously translated on WordPress.com.
Let us know if you have any questions!
We’re announcing the launch of the Community Translator on en.blog.wordpress.com later today!
Thank you all for your help in testing it! We’re already planning our next iteration that will reflect more of your feedback and introduce new features.
We hope that today’s announcement will bring in quite a few new translators, and we’re confident that it will be a great step ahead for the translation of WordPress.com.
As always, if you notice any issues – please let us know!
Heads up – two step authentication will be required soon!
In order to improve the security of translation and validation on WordPress.com, we will soon require 2 step authentication to be active when using validator permissions. While you will still be able to use GlotPress and suggest translations without 2 step authentication, any advanced actions will no longer be possible.
To learn more about 2 step authentication and how to activate it, please visit our support page.
If you have any concerns or questions, please comment. Thanks!
Validation question – did you ever translate or approve a translation for an original where it made sense to add or change html tags in the translation?
Background: Right now, validators can approve translations where html tags are added, omitted, or changed. We’re considering changing this functionality, but before doing so – we’d like to know if it’s essential for your work.
We’ve set up a number of predefined views in the WordPress.com project at translate.wordpress.com.
Selecting one of the available views will filter the list and only show the relevant strings.
We’d love to get your feedback here:
1. Do you think this is something that you’re going to use?
2. Are there any other views that you’d like us to add?