[wp-meta] [Making WordPress.org] #645: BuddyPress language pack upgrade "freshness"

Making WordPress.org noreply at wordpress.org
Wed Oct 8 20:02:52 UTC 2014

#645: BuddyPress language pack upgrade "freshness"
Reporter:  imath   |      Owner:
    Type:  defect  |     Status:  new
Priority:  high    |  Component:  translate.wordpress.org
Keywords:          |

 I'm a bit worried about the different messages i've read in forums or i've
 heard in some of my discussions with french people concerning the
 internationalization of BuddyPress since 2.1 (People are uninstalling 2.1
 to come back to 2.0.3).

 Since 2.1, BuddyPress rely on the language packs that are automatically
 updated. At first sight this seems to work fine as an update message is
 appearing in Dashboard and the "Update Plugin translations" shows, and a
 language pack (buddypress-fr_FR.mo in my case) is downloaded once the
 button is clicked on.

 So we get the po/mo files but strings are '''incompletely translated'''.
 For the french translation the dev version on translate.wordpress.org is
 at '''100%'''.

 So i've directly downloaded the french po file from the
 translate.wordpress.org and compared it to the one i get using the auto
 upgrade feature and i've compared them :


 As you can see the file you get using the auto upgrade feature has a
 revision date set to april 16th, although the one on
 translate.wordpress.org has a revision date set to october 4th.

 Now if i get the mo file from translate.wordpress.org and place it in
 {{{WP_LANG_DIR}}}/plugins/ to replace the one the auto upgrade is
 grabbing, then '''all strings''' are translated.

Ticket URL: <https://meta.trac.wordpress.org/ticket/645>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list