[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 dd32):

 1. All strings in GlotPress will be pulled automatically from the plugin
 files (so proper textdomain support is required), all pot/po/mo files in
 the plugin are ignored
 2. Plugins in the repository should not be "bloated" with extra premium-
 only strings, and are already not allowed to simply have premium-only code
 disabled, so that should extend to extra strings for that purpose
 3. If an author chooses to use their own external GlotPress install, they
 can continue to bundle the po/mo files, they simply don't get the benefit
 of Language packs
 4. External language pack sources will not be supported, just the same as
 we don't allow for external plugin update sources, but of course plugins
 can do anything they want (as long as they abide by all WordPress.org repo
 rules if hosted there)

 Since GlotPress does offer both an Export and Import functionality, it
 should be conceivable to build a work-flow around that, and I'm sure some
 automated tools will pop up to help with that as the larger plugins start
 using the system.

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