[wp-meta] [Making WordPress.org] #1691: Internationalisation

[Making WordPress.org]

#1691: Internationalisation
------------------------------+------------------
 Reporter:  dd32              |       Owner:
     Type:  task              |      Status:  new
 Priority:  high              |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------
Changes (by dd32):

 * priority:  normal => high


Old description:

> WordPress & WordPress.org are not just in American English, in order to
> fully bring the Plugin Directory to the masses we need to have a properly
> localised site and content.
>
> Part of this also hooks into #1496 & #1574 - We need to make the
> translated content available to Elastic Search.
> In order to do that, we need to store the translated plugin data into
> WordPress as well (Instead of translating-on-the-fly like the existing
> Plugin Directory does, and how the Themes Directory does it).

New description:

 WordPress & WordPress.org are not just in American English, in order to
 fully bring the Plugin Directory to the masses we need to have a properly
 localised site and content.

 Part of this also hooks into #1496 & #1574 - We need to make the
 translated content available to Elastic Search.
 In order to do that, we need to store the translated plugin data into
 WordPress as well (Instead of translating-on-the-fly like the existing
 Plugin Directory does, and how the Themes Directory does it).

 Tasks:
  * Have all directory strings marked for translation
  * Present Translated plugin data on views
  * Have that Translated plugin data available for seamless searching
  * Trigger the GlotPress code imports, which requires creating the .pot's
 for both the readme and plugin code.

--

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/1691#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org