Enable community-translator

[yoavf]

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:

• translate-api-plugin.diff​ contains the GlotPress plugin
• translator.diff​ contains the translation backend plugin, and the front end script which is a minified build from ​https://github.com/Automattic/community-translator/
• jumpstart-plugins.diff​ is the code to load the translator in the plugin directory
• 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

[akirk]

This fixes a bug where the ngettext filter was not installed properly.

[dd32]

Milestone renamed

[dd32]

Milestone renamed

[dd32]

Just noting that I've started taking a look at this, and think I can get a variant of it up and running for some things sooner than later (although I have a few other tasks that take priority, so this is my on-the-side project right now)

I'm finding some limitations where strings don't get matched due to various content filters (​wptexturize() being the main culprit I think) but it seems that overall, this patch/code still works to a degree good enough that a POC works on the plugin directory, about pages, and DevHub to a degree.

Thanks @yoavf & @akirk for getting this started!

There's been quite a few changes to dotorg in the past 5 years, some of which make this easier, and some of which mean it would be beneficial to work on this again. I've also got some of my own thoughts on how to improve the interface & flow, so some of it is going to require some experimentation.

This ticket is the intention behind [10444] and [10446] (Well, actually [10442:10447] if you want the full story)

See https://meta.trac.wordpress.org/ticket/1078

This is a draft PR where I was playing with adding the community translator.

There are a number of changes made to the upstream community translator project, which increases the size of this PR significantly.

See https://meta.trac.wordpress.org/ticket/1078

This is a draft PR where I was playing with adding the community translator.

There are a number of changes made to the upstream community translator project, which increases the size of this PR significantly.

Replaces #27