In 3.6 releases that update has simply been forgotten, in 3.6.1 an update had been done, but for some strange reasons didn't work (I suspect that either old translations got loaded or the build step didn't convert the updated .ts files into .qm files or the packaging step didn't pick those updated .qm files)
That PR was basically a test, with the added benefit that in the 3.x branch (AKA development builds) the translations are now up-to-date.
Once 3.6.2 gets released, this should be done again, to reflect the latest translation updates at release time (or as close as possible to that), but would be a much smaller change I guess.
Starting to understand.
But natural next question why is the inclusion of latest translations a "standard" commit instead of an automatic step in the release process?
Because downloading the latest.ts files from Transifex is not part of the build process and never was.
But actually a good question, it better should indeed.
Comments
Are you really sure? They had been updated, in 4ae6ab4
And if not it should be possible to update them the normal way, see https://musescore.org/en/handbook/3/language-translations-and-extension…
Confirmed. I'm at a complete loss for an explanation
See https://github.com/musescore/MuseScore/pull/7364
PR got merged, although there will probably another such update shortly before 3.6.2 gets released
In reply to PR got merged, although… by Jojo-Schmitz
Does it mean that translations are hard coded in the package?
? Not anymore that ever before. You can still update to later version if there is one.
Now the current versions of all translations (as of about an hours ago) are packaged along with MuseScore.
In reply to ? Not anymore that ever… by Jojo-Schmitz
Then why was a PR necessary, and why should this PR be refreshed just before 3.6.2 as specified in its comments ?
In 3.6 releases that update has simply been forgotten, in 3.6.1 an update had been done, but for some strange reasons didn't work (I suspect that either old translations got loaded or the build step didn't convert the updated .ts files into .qm files or the packaging step didn't pick those updated .qm files)
That PR was basically a test, with the added benefit that in the 3.x branch (AKA development builds) the translations are now up-to-date.
Once 3.6.2 gets released, this should be done again, to reflect the latest translation updates at release time (or as close as possible to that), but would be a much smaller change I guess.
In reply to That PR was basically a test… by Jojo-Schmitz
Starting to understand.
But natural next question why is the inclusion of latest translations a "standard" commit instead of an automatic step in the release process?
Because downloading the latest.ts files from Transifex is not part of the build process and never was.
But actually a good question, it better should indeed.
Automatically closed -- issue fixed for 2 weeks with no activity.