[wp-meta] [Making WordPress.org] #1078: Enable community-translator

Making WordPress.org noreply at wordpress.org
Wed Jun 10 11:51:37 UTC 2015


#1078: Enable community-translator
------------------------+---------------------
Reporter:  yoavf        |      Owner:
    Type:  enhancement  |     Status:  new
Priority:  normal       |  Component:  General
Keywords:  has-patch    |
------------------------+---------------------
 The community translator is a tool that enables front-end translations of
 strings for projects that use GlotPress to store their translations. It
 consists of a few parts:

 1. A front end script that highlights translatable strings, provides the
 UI to translate them, and submits the translations
 2. A backend plugin that prepares translation data for the script (based
 on gettext filters, for example)
 3. A GlotPress plugin to extend the api (gihub link coming soon)

 Enabling it on WordPress.org would allow front end translations of
 rosetta, the plugin directory, the theme directory, etc.
 Demo: https://cloudup.com/iU6acgS9-x1


 Patches:
 - [attachment: translate-api-plugin.diff] contains the GlotPress plugin
 - [attachment: translator.diff] contains the translation backend plugin,
 and the front end script which is a minified build from
 https://github.com/Automattic/community-translator/
 - [attachment: jumpstart-plugins.diff] is the code to load the translator
 in the plugin directory
 - [attachment: jumpstart-rosetta-themes] is the code to load the
 translator in rosetta sites and the plugin directory

 TODOs:
 - Do we want this to load for all users? Only previously active
 translators? something else?
 - Fix URLs in the translator plugin for wporg cdn
 - Design adjustments
 -

 props akirk hew julesaus

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/1078>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list