Resource Manager fails
Trying to download any updated translation via the Resource Manager fails repeatedly with "Failed, try again".
The corresponding files do get downloaded though, I see them in "%LOCALAPPDATA%\MuseScore\MuseScoreDevelopment\locale\"
Factory reset doesn't help
Windows 7 Enterprise 64bit, 8d8b6cc
Comments
Copying the downloaded .qm files to overwrite the ones that are part of the nightly build results in the translations to be visible, but doesn't change the "Failed, try again" issue.
Copying the downloaded .qm files to overwrite the ones that are part of the nightly build results in the translations to be visible
It's not the first time that you write something like this, and I'm not sure I understand. You should not have to modify the installation of the nightlies. Actually on some system like OSX, it will not be possible with the release, because of the signing.
Do you think there is a bug in the way we load the translation? Put aside problems with the palette tooltips, translations loaded via the resource manager should override the translations from the nightlies, actually the most recent of the two should be loaded. Is it the case? If not it's a bug and we need to address it separately.
There are 2 issues, this here talks about the error you get when trying to download a new translation via the Resource manager.
The other issue is that these translation don't override the ones from the nightly build, and I reported this earlier, not in the issue tracker though, http://musescore.org/node/22982#comment-89387. Guess I should make it an issue then
Edit: see #23544: New translations loaded via Resource Manager don't override existing ones
Strange, in 55c0026 I don't get that error (but have to run MuseScore in debug mode, see #23513: MuseScore-55c0026 doesn't start at all)
And now I can't reproduce it in 8d8b6cc either
I added Mongolian language. It was on transifex but it was missing in the code. It may have fix it.
Ah, well possible, the problem started around that time
Automatically closed -- issue fixed for 2 weeks with no activity.