Opened 6 years ago
Closed 6 years ago
#3966 closed defect (bug) (invalid)
Vanishing translated strings and translation updates stuck.
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | Translate Site & Plugins | Keywords: | |
Cc: |
Description
Hi,
We have a situation on BuddyPress translation automatic updates, and more globally about the translation workflow in GlotPress. BuddyPress 4.0.0 was released on the 27th of november (2018) and since then BuddyPress users can't have their language packs updated.
Here's a chronology of events that brings me to this ticket.
- 2018-10-26: @DJPaul updated WP Plugins directory's trunk with BuddyPress 4.0.0-beta 1 > https://plugins.trac.wordpress.org/changeset/1963643
- 2018-11-22: I've translated all new strings in French into the Development version of the BuddyPress's GlotPress area > https://translate.wordpress.org/projects/wp-plugins/buddypress/dev/fr/default As there were a lot to translate, I was so proud of myself that I've tweeted about it : https://twitter.com/imath/status/1065546851150118912
- 2018-11-27 @boonebgorges released 4.0.0 on the WP Plugins directory > https://plugins.trac.wordpress.org/changeset/1981569
- 2018-11-27 (3 mins later) @boonebgorges made a small change, I guess to refresh the stable tag > https://plugins.trac.wordpress.org/changeset/1981570
- 2018-11-29 I've reverted this small change hoping it would fix the translation updates issue > https://plugins.trac.wordpress.org/changeset/1982789
It did not 😭. Moreover after checking the GlotPress Development version for BuddyPress fr_FR I had the surprise to see all the translating work I did just vanished 😱 😭😭
- Would it be possible to fix this translation automatic updates issue ?
- To avoid making translators lose their translated strings would it be possible to know what is the workflow we need to follow to make sure a Development (trunk) translated pot is successfully transformed into a Stable pot ?
- Would it be possible to have some docs to make sure we commit things in the right order ?
About 2 and 3, maybe I haven't searched enough, but I haven't found anything to help me in :
- https://make.wordpress.org/polyglots/handbook/tools/glotpress-translate-wordpress-org/ (by the way it should be updated as this section is leading to a ghostly GlotPress Trac
- https://developer.wordpress.org/plugins/internationalization/
- https://developer.wordpress.org/plugins/wordpress-org/
I really hope you can help us to have this issue fixed. Thanks a lot in advance.
Change History (3)
This ticket was mentioned in Slack in #buddypress by imath. View the logs.
6 years ago
#3
@
6 years ago
- Keywords needs-docs removed
- Resolution set to invalid
- Status changed from new to closed
The only thing that seems to be wrong is your way to tag/release new versions. You're adding the files instead of copying them from trunk which may result in strings being added to the stable project but not in dev project. Please read https://developer.wordpress.org/plugins/wordpress-org/how-to-use-subversion/#tagging-new-versions on how to tag new versions.
For example the string "Export Data" was part of https://plugins.trac.wordpress.org/changeset/1981569/buddypress which was committed to trunk _after_ the "tag" was created in https://plugins.trac.wordpress.org/changeset/1981559/buddypress.
Some observations: I've also noticed that the sync between trunk and stable sometimes simply does not happen. I haven't been able see any specific trigger for this behavior.
Advice on #meta-i18n was to "submit a whitespace commit", which definitely does not trigger the sync. Tagging a new stable version has (so far) done the trick when I've been hit by the bug.