MuseScore 2.0.3 ready for translation
We are about to release MuseScore 2.0.3 but before we do, it would be great if you could check on the status of your language. The deadline for updating the translations is March 25th, so in exactly 10 days from now.
How to translate
* Go to https://www.transifex.com/musescore/musescore/
* Scroll down and seek for your language
* If your language is not 100% translated, log in or create an account on Transifex
* Next, click on your language and you will see all the available resources which can be translated
* The important ones for the 2.0.3 release are the MuseScore and Instruments resources
* If these are not at 100%, click on the resource
* Finally click on the green Translate button
Or check out this animation video
How to test your translation work in 2.0.3
* Go to https://musescore.org/en/download
* Choose your platform
* Start MuseScore and navigate to the menu Help > Resource Manager
* If an update is available for your language, download it, close and restart the software
Or check out this animation video
If you have questions, don't hesitate to leave a comment on this post.
Comments
And even if your language's translation is 100% complete, it is unlikely 100% correct ☺ and could well need some proof reading and corrections
In reply to And even if your language's by Jojo-Schmitz
Perhaps more than "some" and: copyright is still 2015?
(It was told in a forum but can not find where)
In reply to Perhaps more than "some" and: by Shoichi
Thanks for the hawk eyes Shoichi!
In reply to Thanks for the hawk eyes by Thomas
The (old) news is not my doing. Good job and a cordial greeting to all!
In reply to And even if your language's by Jojo-Schmitz
Hope there is plan for the Never Hide option in the staff-properties dialog. Would be nice if a fix is available before all translators have completed the update:)
In reply to Hope there is plan for the by Henk De Groot
Hello everyone, I guess it's normal in this way:
Tip: there are a lot of new strings that are the precise names of Unicode block character definitions, for example "Inscriptional Pathian" or simpler names like "Vertical Forms".
Though these strings are not marked for "literal translation", I recommend to keep the original string in the translation, because this is exactly how the Unicode block is named and can be found on for example wikipedia. You probably would create complete confusions with translations like "Vertikale vormen".
In some cases I added a translation behind the copied string between brackets, to give a clue, for example I have the translated string: "Arrows Extended (uitbreidingsset pijlen)".
You also can copy the string, and add "(Unicode block)" at the end, to try to make clear that it is a literal string for a very specific character set.
P.S.
All Dutch strings for the Musescore program have been translated and are reviewed now :-)
In reply to Tip: there are a lot of new by Ad.Stakenborg
Thanks, I had done it that way: https://musescore.org/it/node/93986
"...Most of the new strings are for languages and Unicode block (eg .: Combining diacritical Marks Extended see https://en.wikipedia.org/wiki/Combining_Diacritical_Marks_Extended ). I do not think there are more and correspondences in Italian, I left as in the original. ..."
(hope I have not done too much damage)
In reply to Tip: there are a lot of new by Ad.Stakenborg
Hi Ad, it has been only 8 weeks and 6 days ago since I posted a message in the dutch forum asking for suggestions to translate or not....had some discussion on this in the english forum as well and finally did the dutch translation. To me it does not make sense to have english text in the unicode blocks as dutch users (that don't use/know english) will not be seeking for the english text. A dutch text makes more sense in that as it is also listed in alphabetic order.
Anyway each solution has it's pro's and cons. So happy to leave it like it is. It can Always be revised when users start to complain about it.
Tip:
Several strings related to "compression" have to be "translated" in your local language
You can find a description of these terms on this wiki page: https://en.wikipedia.org/wiki/Dynamic_range_compression
For most compression settings I decided to literally copy the original "technical" string into Dutch, but I added a kind of short translation or clarification in the Dutch language between brackets after the string.
Best of both worlds...
In reply to Tip: Several strings related by Ad.Stakenborg
I tried to learn https://it.wikipedia.org/wiki/Compressione_del_livello_audio
my best :(
But I do not see a lot of complaints in the Italian forum ... well, it's not very crowded indeed
In reply to I tried to learn by Shoichi
Hi,
I changed just a couple of translations (Italian :)) on Transifex plus I commented on some more. Do I have to notify it somewhere?
Is there a "latest edited translations" on Transifex? I can't find it :(
You can make an issue of a comment if action is required.
Otherwise it is just for who looks at the specific string and opens the comment. Your comments will appear even when translating a different language, so comment in English ..
Everybody can search for translations changed after a specific date.
Changed translations affect the translated manuals (norification not automated), you can post a remark in the Italian forum.
In reply to You can make an issue of a by Ad.Stakenborg
server problems?
8bc614b (2.0.2 too)
In reply to server problems? by Shoichi
See https://musescore.org/en/node/102596#comment-458996
In reply to See by [DELETED] 5
Now the tab is completely empty
___edit now it work on 176a6d7