While all strings have been translated and previous text in the Page-settings dialog has been 100% in dutch, now English text is appearing for Printable area and Staff space.
Yes I did update the translation. In fact this issue started to appear after updating the translation.
I think it is related with some text being English in Staff properties as well due to changes/new functionality in the master branch.
Same using German settings in MuseScore 2.0.2, OK before update translations, wrong after, same for the latest nightly build from master.
In that latest nightly in Dutch and German settings the issue can be seen only partly ("Staff space (sp):" being untranslated, "Printable area" having been removed from the dialog)
The lasted build from 2.0.3 has it right after updating translations, so I think we can close this issue as being fixed.
I think it can be closed for v2.0.3, however it still leaves an issue in v2.0.2. Not sure if this is desired or not, guess that depends how long it will take before 2.0.3 is released.
Comments
Did you update the translations? See https://musescore.org/en/handbook/language-settings-and-translation-upd…
Yes I did update the translation. In fact this issue started to appear after updating the translation.
I think it is related with some text being English in Staff properties as well due to changes/new functionality in the master branch.
See https://musescore.org/en/node/96096
Same using German settings in MuseScore 2.0.2, OK before update translations, wrong after, same for the latest nightly build from master.
In that latest nightly in Dutch and German settings the issue can be seen only partly ("Staff space (sp):" being untranslated, "Printable area" having been removed from the dialog)
The lasted build from 2.0.3 has it right after updating translations, so I think we can close this issue as being fixed.
I think it can be closed for v2.0.3, however it still leaves an issue in v2.0.2. Not sure if this is desired or not, guess that depends how long it will take before 2.0.3 is released.
Shouldn't take too long, considering that the work in the releasnotes has just begun:
https://musescore.org/en/developers-handbook/release-notes/release-note…
Automatically closed -- issue fixed for 2 weeks with no activity.