#7479 closed enhancement (fixed)
Strings in readme.txt require constant localisation
Reported by: |
|
Owned by: |
|
---|---|---|---|
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)
Change History (6)
#4
@
7 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."_
7479.diff changes the Upgrade Notice and Changelog text in readme.txt so that new translations aren't required for each new BP release.