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

Making WordPress.org noreply at wordpress.org
Thu Feb 5 11:28:13 UTC 2015

#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:6 nacin]:
 > >  * `Dotorg_Plugins_Tracker::process_code_i18n()`: should we also have
 logic to use a plugin's own committed PO/MO files if any,
 [https://plugins.trac.wordpress.org/browser/jetpack/trunk/languages like
 Jetpack]? What if they don't have a committed POT file, and ours somehow
 doesn't match their PO/MO files (doubtful but possible)?
 > Nope, I don't think so. These will override language packs, but the goal
 should be to import them into GP and remove them from the plugin.

 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?

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

More information about the wp-meta mailing list