[wp-meta] [Making WordPress.org] #760: Plugins directory internationalization project

[Making WordPress.org]

#760: Plugins directory internationalization project
-----------------------+-------------------------------
  Reporter:  stephdau  |      Owner:  stephdau
      Type:  task      |     Status:  accepted
  Priority:  normal    |  Component:  Plugins Directory
Resolution:            |   Keywords:  has-patch
-----------------------+-------------------------------

Comment (by DavidAnderson):

 Replying to [comment:22 Otto42]:
 > Replying to [comment:21 DavidAnderson]:
 > > What are the implications of this, in terms of plugins that already
 have their own GlotPress install (or other system) elsewhere, that people
 already work on? And who want to keep on using it?
 >
 > None. If a plugin includes its own po/mo files, then those get used
 preferentially.

 I think what I'm really asking is, whether there'll be a way for plugin
 authors to provide their own PO/MO files such that they a) don't have to
 be included in the plugin zip download, and b) also don't have to use WP's
 GlotPress install to make translations, but can use their own.

 e.g. Something like, if a plugin author uploads his translations (which he
 gets from whatever source he prefers) to assets/translations/, then those
 translations can be delivered through the new "don't bloat the plugin
 download" mechanism, instead of plugin translators being required to use
 WP's GlotPress install as the place where they have to make translations.
 (Of course, GlotPress has an 'import' function... so perhaps my question
 is about whether importing can be automated through some mechanism like
 this, rather than having to go through the WP GlotPress website).

 Apologies if this is a silly question - I did some Googling to try to
 learn about the state of this project, but learnt almost nothing...

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