Howdy all you wonderful polyglots!
We’re getting very, very close to turning on translations for themes and plugins. Within the next few days (or weeks), we’ll start importing active themes and, shortly there after, plugins to translate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins..
The first import might be a bit… painful. There aren’t a lot of sorting options built-in to GlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org., so importing, say, 1500 themes will make it hard to see which theme is important. We’re working on that. After import, it will be important to use translate.wordpress.org and find “pain points” in the experience. Then… let us know! You can file a ticket on meta trac with an idea for improvement and we’ll work to improve things over time. Or, you can ping The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” me personally (sam on Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.) or even just leave a comment here.
For themes and plugins with their own, external translation sites, we’re recommending the author post here on make/polyglots with a list of their translation editors 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 and request that they be added to translate.wordpress.org with project-level permission. That means that they’ll only be able to approve translations for the specific theme or plugin 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 WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party, which they can already approve translations for on an external site.
That might sound a bit complicated, but I wrote up a handbook page with all of the details. Please read through and let us know if you have questions.
One thing I’m recommending to everyone is to follow a hashtag for your locale 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 https://make.wordpress.org/polyglots/teams/. For example, the Swiss German translation editors would follow #de-ch in their WordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ profile notifications. Any time, across WordPress.org, someone enters #de-ch, they’ll receive an email notification about it. It’s a great way for anyone “in the know” to ping translation editors and entire teams.
P.S. If you haven’t already, now is a great time to translate the theme and plugin directory interfaces.
Related posts: Meta team, Theme team