New translations loaded via Resource Manager don't override existing ones

• Nov 14, 2013 - 17:30
Type
Wording/Translation
Severity
S4 - Minor
Status
closed
Project
  1. Download a new nightly build
  2. unpack it
  3. start it
  4. go to menu->Help->Resource Manager
  5. download an updated translation
  6. make sure this is the language MuseScore is configured to use
  7. make a note of some untranslated terms that you know are translated on transifex
  8. restart MuseScore

Desired result: the new translations should be visible
Actual result: they are not

Wotrkaround; copy the files from %LOCALAPPDATA%\MuseScore\MuseScoreDevelopment\locale\ into the locale directory of your nightly build and restart MuseScore

Resetting to factory settings and deleteing the personal folders doesn't change the issue

Windows 7 Enterprise 64 bit, 8d8b6cc


Comments

The issue from #2 is still there with 36a4aad.
The initial issue can't get reproduced currently, as there are not updated translations, all the latest ones are now integrated into the nightly. Except for Russian, but I won't spot whether there is a difference ;-)
Correction: I can still reproduce, as I recently changed a single string in the German translation and don't see that change in MuseScore, regardless of having downloaded the update.

The alignment with mongolian has been fixed on the server which do the pull from transifex.

For the other, the only way I can reproduce is with the System locale. When this locale is composed of language and country, such as fr_FR, the files can't be found (since is mscore_fr.ts) and so the last modified date can't be compared. The installation file is then loaded. The loading is done by Qt and it can cope with fr_FR, it will find the right file but it will not report it :(

To fix it, I will try to replicate Qt loading algorithm in our simple case.

If you can reproduce the bug with another language than the system one, please give more details.

I'm indeed using the system language, with Windows being set to German, Germany. So it is well possible that MuseScore looks for a mscore_de_DE.qm and doesn't find one.

Status (old) active fixed

Forget about it, deleting the updated files and downloading them again and it works.
And thanks a lot for fixing it!