Skip to:
Content

BuddyPress.org

Opened 3 years ago

Closed 2 years ago

Last modified 2 years ago

#7479 closed enhancement (fixed)

Strings in readme.txt require constant localisation

Reported by: henry.wright Owned by: slaFFik
Milestone: 2.9 Priority: normal
Severity: normal Version:
Component: I18N Keywords: has-patch
Cc:

Description

Taken from readme.txt:

== Changelog ==

= 2.8.0 =
See: https://codex.buddypress.org/releases/version-2-8-0/

= 2.7.4 =
See: https://codex.buddypress.org/releases/version-2-7-4/

= 2.7.4 =
See: https://codex.buddypress.org/releases/version-2-7-4/

= 2.7.2 =
See: https://codex.buddypress.org/releases/version-2-7-2/

= 2.7.1 =
See: https://codex.buddypress.org/releases/version-2-7-1/

= 2.7.0 =
See: https://codex.buddypress.org/releases/version-2-7-0/

The problem with this approach is each new version of BuddyPress will need a new string translated. This makes achieving 100% localisation a continual battle.

May I suggest amending readme.txt to something like this:

== Changelog ==

For a curated list of changes see: https://codex.buddypress.org/changelog/

Of course a new Codex page would need to be published with a list of links such as:

https://codex.buddypress.org/releases/version-2-8-0/
https://codex.buddypress.org/releases/version-2.7.4/
...

Attachments (2)

Screenshot 2017-03-22 at 22.42.39.png (106.8 KB) - added by henry.wright 3 years ago.
7479.diff (2.2 KB) - added by henry.wright 2 years ago.

Download all attachments as: .zip

Change History (6)

@henry.wright
2 years ago

#1 @henry.wright
2 years ago

  • Keywords has-patch added; dev-feedback removed

7479.diff changes the Upgrade Notice and Changelog text in readme.txt so that new translations aren't required for each new BP release.

#2 @djpaul
2 years ago

  • Resolution set to fixed
  • Status changed from new to closed

In 11545:

readme.txt: trim Upgrade Notice and Changelog sections.

This change means that new translations aren't required for each new BP release (which can't be made until Glotpress updates from the final readme.txt).

It also removes a trivial change that package maintainers need to make each time a release is done.

Fixes #7479, props henry.wright

#3 @DJPaul
2 years ago

  • Milestone changed from Awaiting Review to 2.9

#4 @netweb
2 years ago

[11545] is still a good change to make :+1:, I'll also just point out the following, language packs are now generated when translations for "stable" reach 95% which allows a little more leeway:

https://make.wordpress.org/polyglots/handbook/frequently-asked-questions/#strings-are-validated-when-are-they-taken-into-account-for-download
_"If strings in stable are approved for at least 95% for a plugin/theme in a certain locale, language-pack generation happens 30 minutes after a translation has been updated. Then any local WordPress set to use that specific locale will download it in the next hours after the generation."_

Note: See TracTickets for help on using tickets.