Missing strings for translation
Dear all,
when translating the MuseScore 4 interface, it looks like some strings can't be found on Transifex. Attached screenshots are showing certain untranslated strings. Is it possible to add them for translation?
Of course I can be wrong and I missed these elements.
Thank you for reply.
| Attachment | Size |
|---|---|
| Missing strings 1.pdf | 175.97 KB |
Comments
Try downloading the latest Nightly (https://ftp.osuosl.org/pub/musescore-nightlies/ ) and update the translations
In reply to Try downloading the latest… by Shoichi
Thank you very much for fast reply. Indeed some things have bee solved by running latest version.
In previously sent attachment first two pages have been resolved and other two remained.
Sincerely
M
Hy,
I have encountered a few more instances, where it appears everything is translated in Transifex, but does not show in program:
- in setup wizard, when creating new document in second tab "Create from template" all options are in English
- in most dialog windows OK and Cancel are not translated, despite everything else is :)
Sincerely
M
In reply to Hy, I have encountered a few… by Mejdun
Ciao, I do not encounter the problem on page settings. Consider that templates are built into the program, and probably these issues should also be addressed on GitHub, see: https://musescore.org/en/nightly-builds
I also downloaded the version in use today:
OS: Linux Mint 20.3, Arch.: x86_64, MuseScore version (64-bit): 4.0.0-223310405, revision: 9c645ff
In reply to Hy, I have encountered a few… by Mejdun
The OK and Cancel in some dialog windows are provided by Qt libraries. MS3 is also showing the same OK and Cancel English text. This has been resolved for a couple of other languages that had the same issue. Think it would be best to log this as an issue in github to fix this.
Good spot on the "templates", don't see a reason why they should not be translated as they are in MS3. Not sure if this is intended or an oversight. The good news is that this has been logged as an issue in github: https://github.com/musescore/MuseScore/issues/14900 so hope this will be resolved soon.