[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:                    |
------------------------------+------------------

Comment (by dd32):

 > bbPress inits the SVN tracker.

 This is the major part of the system which hasn't yet been written, I've
 started a few things on this, but nothing solid that we can use.
 My current thoughts is that we should be building this upon a cron system
 like Cavalcade, which would make the process far simpler and reduce the
 reliance upon a single server to process plugin updates.

 However, I don't expect that's going to be an option for us to start with,
 so I expect we'll need to build a script similar to bbPress's which is
 called every minute and processes svn revs from `$last` to `HEAD`
 triggering plugin imports to the directory, ZIP Invalidation/rebuilding
 where needed, and finally triggering GlotPress imports via `.pot` files.

 > Store translated data in another post type:

 This is the direction I was initially going to suggest going with, or
 perhaps storing it in a sub-page. For example, `/plugin-name/` and
 `/plugin-name/de_DE/` would exist, the latter being in a different
 `post_type` - we'd transparently switch out the translated post with the
 main post object on the fly as needed.
 No matter what option is chosen, there's going to be a lot more data
 stored in the DB which isn't really an issue, the biggest issue is the
 searching, having some way to return the right information and not
 duplicating results between a specific locale & english, etc.

 @tellyworth has been looking at ways to get the translated data into
 search. Last I heard was that re-using the translate-on-the-fly that
 bbPress is currently doing is the easiest option for display, and then
 just pushing the translated data into ElasticSearch in other ways

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