Every Rosetta site now gets a theme and plugin directory for free! This is a new feature that has been rolled out to all Rosetta sites and is part of the site setup process for new locales. There are a number of features that need to be added to these directories to make them more friendly to localized visitors (for example, prioritizing translated themes and plugins over English ones), but the process has started.
Translating all “meta” projects (Rosetta sites, etc) can be done from the Meta tab for your locale. You can track the progress of translating both the theme and plugin directories from their respective project pages. Once they’re translated, they will be deployed every 24 hours.
The eventual goal is to be able to translate any theme or plugin in the WordPress.org theme and plugin directories. There are still a few things left to get to that point, but we’re well on our way and expect to turn on this feature soon. Once turned on, you’ll be able to translate any active theme or plugin! At the same time, you’ll be able to translate every theme and plugin. This can be a daunting experience, but we’re working on improving it.
For starters, some themes and plugins have their own, existing communities that are not hosted on WordPress.org. If a theme or plugin developer requests it, we strongly recommend that the translation editor adds new, project-specific translation editors.
Example: if the author of the Twenty Fourteen theme (WordPress.org!) has an existing German translation editor in their community, they can request that the current German translation editors on WordPress.org (“Editors”) add their translation editor to the team, specifically for the Twenty Fourteen project.
Note: Want to understand how roles and permissions work? The Roles and Capabilities page walks through the different roles.
Translating 30,000+ plugins and 3,000+ themes is a very big task. Whenever possible, bringing in translation editors – for specific themes or plugins – is the ideal path and the polyglots team will work with Editors of all locales to make this happen.
Should a theme or plugin author wish to migrate their translation editors to translate.wordpress.org, they should create a post on make/polyglots with the details. We recommend one post per plugin author and covering all plugins they own. However, importing plugins will happen in stages so that duplicate posts may be needed. The post must include WordPress.org usernames.
For additional requests to add more translation editors, leave a comment to your own post instead of creating a new request.
Here’s a sample post that can be used to request new translation editors. Multiple plugins can be listed in the initial sentence. Please be sure to link to the plugin so that your authorship can be verified. The locale codes are available on the Translation Teams page, under the “WP Locale” column.
Hello Polyglots, I am the plugin author for [plugin-name and link to plugin directory]. We have a number of great translation editors that we’d like to be able to approve translation for our plugin(s). Please add the following WordPress.org users as translation editors for their respective locales:
#ar – @username
#bn_BD – @username, @username
#da_DK – @username
#de_CH – @username
If you have any questions, just comment here. Thank you!
Tip: On the Make WordPress sites (like make.wordpress.org/polyglots), you can put an “o” at the start of a line, and it will become a checkbox that anyone can check off as “completed,” as shown above.