Opened 5 years ago
Last modified 2 months ago
#1078 reviewing enhancement
Enable community-translator
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | Q1 | Priority: | normal |
Component: | Translate Site & Plugins | Keywords: | has-patch |
Cc: |
Description
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:
- A front end script that highlights translatable strings, provides the UI to translate them, and submits the translations
- A backend plugin that prepares translation data for the script (based on gettext filters, for example)
- 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
Attachments (5)
Change History (17)
This ticket was mentioned in Slack in #meta by iandunn. View the logs.
5 years ago
This ticket was mentioned in Slack in #meta by ocean90. View the logs.
5 years ago
This ticket was mentioned in Slack in #polyglots by ocean90. View the logs.
4 years ago
This ticket was mentioned in Slack in #polyglots by dd32. View the logs.
17 months ago
Note: See
TracTickets for help on using
tickets.
This fixes a bug where the
ngettext
filter was not installed properly.