[SRU] Bring translations from launchpad
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-notifier (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
Kinetic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
In the last couple releases we have not updated the translations from Launchpad. We are bringing them to the source package in an effort to unblock this SRU release:
https:/
This is because the launchpad translations already have the "pro status" string properly translated.
Not only this will unblock this SRU, but it will make the package aligned with the launchpad translations.
[Test Case]
To test this change, we will need to verify if the message:
See https:/
Is correctly translated for the languages that have added support for this message.
[Regression Potential]
Since we are bringing the translations from launchpad, there could be translations done directly in the package that are now missed. Although this is unlikely, since the translations on Launchpad are better maintained them the ones in the package.
Note that update-notifier is not using language pack (reasons in https:/
[Other Info]
We have some gray areas regarding the verification of this bug. The target message:
See https:/
Is not translated into all Ubuntu releases, like Xenial. For those releases, we are then just updating the translations using the Launchpad
language packs.
Therefore, we might need future SRUs just to update the translation of new messages into these releases.
Additionally, we are still searching for a good way to just verify translation updates in the package.
description: | updated |
no longer affects: | update-notifier (Ubuntu Trusty) |
description: | updated |
I checked the sample string given in the test case, and only Focal and Jammy have that translated to *some* languages:
Xenial:
$ grep "sudo pro status" po/* | grep -v "or run:" | wc -l
0
This SRU for xenial:
$ grep "sudo pro status" po/* | grep -v "or run:" | wc -l
0
Bionic:
$ grep "sudo pro status" po/* | grep -v "or run:" | wc -l
0
This SRU for bionic:
$ grep "sudo pro status" po/* | grep -v "or run:" | wc -l
0
Focal:
$ grep "sudo pro status" po/* | grep -v "or run:" | wc -l
0
This SRU for focal:
$ grep "sudo pro status" po/* | grep -v "or run:" | wc -l
15
Jammy:
$ grep "sudo pro status" po/* | grep -v "or run:" | wc -l
0
This SRU for jammy:
$ grep "sudo pro status" po/* | grep -v "or run:" | wc -l
16
Kinetic:
$ grep "sudo pro status" po/* | grep -v "or run:" | wc -l
0
Lunar:
$ grep "sudo pro status" po/* | grep -v "or run:" | wc -l
0
Additionally, Kinetic and Lunar don't have that string translated, so it would be a regression from jammy. Is this how we want to proceed? Or is there another check I should do instead? I understand we won't get 100% translation coverage, but I picked the string that is in the test case. If the test case is followed, then this SRU will fail verification for X, B, F, and is missing in K and L.