Romanian translation

• Aug 24, 2009 - 16:34

Hello there,

I've been observing MuseScore for some time now and I feel like it starts to become a viable alternative to existing commercial software out there. As a musician (by background) and programmer (by daily job) I decided It'd by a shame not to give a hand to this project and provide it with a Romanian translation.

This is currently work in progress -- being a programmer I'd call it in "pre-alpha" state -- only a small subset of dialogs are translated, many typos and grammar errors here and there, things that should be rephrased and such.

I'll ask in this topic my questions on various strings that I couldn't find in the UI and that I am uncertain of what they could mean. I will also update the *.ts file and its state.

Note: for now, there is no "Romanian" option in the languages pop-up, you'll have to override a different language file in order to test it out.

Attachment Size
mscore_ro.ts 247.29 KB

Comments

• Aug 28, 2009 - 17:42

This version contains about three times as much dialogs translated as previous version did. Other than that, it's still in "pre-alpha" state.
Take care,
C

Attachment Size
mscore_ro.ts 247.17 KB

Reply

• Jan 30, 2010 - 20:47

However: it's not obvious to me when it works and when it doesn't. For instance, I translated "failed" a dozen times or more, and it still shows no star. Is matching limited to the same context? It probably shouldn't be...

Reply

• Jan 31, 2010 - 15:38

Hi ciacob,

The current suggestion implementation in the translation server is only meant to be used when a translator is not sure about the translation and wish to mark it as a suggestion rather than the definitive translation.

However, your request concerning the suggestion like it exists in QT Linguist does indeed not exist in the translation server. I agree it's a valuable feature. Since the translation server is an open source Drupal module (l10n_server), this can be implemented by anyone with some Drupal knowledge.

Reply

• Feb 24, 2010 - 09:58

Hi Ciabob,

I'm contacting you because David is making the pdf versions of the handbooks so they can be included in the upcoming 0.9.6 release. We would really like to add the Romanian handbook as well, but there are around 8 'book pages' which still need to be translated. Many of these pages are pretty short so it could go fast. Could you or Seseberg help us out and finish the translation?

Thanks in advance!

Reply

• Feb 24, 2010 - 10:30

Hi Thomas,

If I correctly read the second column, fully black squares are untranslated pages, right? However, when I click on one of them, I end up on a page which expects translated content to be input, but provides no English content.

So, yes, I would like to help with that, but give me a hand, will ya?

BTW, when do you plan to actually release version 9.06?

Thanks,
Claudius

Reply

• Feb 24, 2010 - 11:28

0.9.6 will be out when
- there are no critical bugs in the issue queue
- when all the translated handbooks are in the release (one of which is the Romanian one which is near to be finished)
- when there has been at least one Release Candidate

Reply

• Feb 28, 2010 - 19:39

Dear all,
Some strings I just translated from English to Romanian yesterday magically pop up again today, untranslated.

Now, I understand the common pitfalls, such as forgetting to add trailing punctuation or placeholders, which -- probably -- automatically invalidate a translated string at moderation time.

But, as I'm increasingly careful about not doing such silly mistakes, so that it practically isn't the case of me making formally invalid translations any longer, please tell me: are there any other hidden rules that I must follow in order to get a translated string pass moderation (and to have it make it into the build)? Is there something I might possibly do wrong?

Any help much appreciated, as always.
Claudius

Reply

• Feb 28, 2010 - 22:20

Hi Claudius,

I presume you are talking about the software translation at http://translate.musescore.org , right?
Do you happen to have an example of a string? Normally, there was no update of the strings anymore since the past 4 days. In case something popped up, could that be the same string in another context?

Thanks for your perseverance.

Reply

• Mar 1, 2010 - 12:00

Hi Thomas,
Indeed, I was referring to software translation rather than book translation. Actually, the fact that the same string might be redundantly found in several contexts was the first thing I thought of, but just wanted to make sure I'm not missing anything.

I don't have sample strings just now, but I'll write them down as they show up. .

Thanks,
Claudius

Reply

• Mar 1, 2010 - 17:15

...this time, regarding the translation of book/documentation chapters. I found this page: "http://musescore.org/musescore-094-available-download" as the only one left untranslated, so I actually went and translated it in Romanian.

Initially I thought that the version number (0.9.4) has accidentally been left unchanged in the English version, or maybe there's a script that searches and replaces it, or whatever. Now, after several hours of diving into that page's content, I'm not that sure any longer.

So the question is: was that an obsolete page? Have I worked in vain? :(

Please assist,
Claudius

Reply

• Mar 1, 2010 - 18:55

Somehow, a string that shows in the translator module (the one at "http://translate.musescore.org") as being part of the "LinePropertiesDialog" context gets in fact displayed on the "Configure Synthesizer" page in the application. A similar string does exist in the "SynthControl" context, but it is simply ignored.

I *need* those strings to be correctly picked up, as the same string in English has totally different Romanian meanings depending on the context.

A picture is worth a thousand words, please see the attached screenshot.

Thanks,
Claudius

Update: this is nightly build R.2795

Attachment Size
Bad_string_mapping.jpg 91.91 KB

Reply

• Mar 1, 2010 - 19:45

Hi Claudius,

You correctly identified a bug. The export of the translations did not take the context into account. Working on it to fix this. I'll keep you posted. Thanks again for the nice report and the screenshot!

Reply

• Mar 2, 2010 - 19:43

Hi Thomas, I need help with two issues now:

#1. Strings for the "files filter" field of the OS specific "Open File" dialog have been localized, but they don't seem to be picked up (see attachment). Those for the "Save As..." dialog show up just fine, and they are as old in the *.qm export as non-working ones are. Please take a look if it isn't going to eat too much of your time.

#2. I made a quick skimming trough the Romanian version of the Handbook and some things can be improved while others are plain wrong, as per music theory. *I do not know* how to contact the translators of the book. I tried to follow the link on the first page of the PDF file (it's Romanian, it essentially says "follow the link to register yourself as a contributor for the Handbook), but that lead me to nowhere. Would you please give me a hand? This is far more critical that #1.

Thanks, and good luck,
Claudius

Attachment Size
Mezer_03-02_21-13-11.png 79.25 KB

Reply

• Mar 2, 2010 - 19:54

#1 Ok, will look into it.

#2 You had already permissions to edit the Romanian handbook. The pdf handbook is compiled from the online one, so if you want to make changes, you need to make them online and David will then compile an updated pdf version. Does that answer your question?
BTW you can always see who worked on a handbook page by checking the revisions tab.

Reply

• Mar 2, 2010 - 19:58

#2 Yes, it looks that I can be unbelievably silly sometimes :))
#1 Update: the same seems to be true for strings showing up in the element inspector (and I mean translations not being picked up, not the above statement :) )

Reply

• Mar 2, 2010 - 22:18

Update: OK, #1 is officially an issue: lots of strings, from all over the UI, show in English while they *are* translated in the online translator (and presumably exported in the *.qm file as well, but I have no means of checking that).

Reply

• Mar 2, 2010 - 22:33

Hi Claudius,

I haven't had the time yet to jump into this problem, but could help me out to pinpoint some more strings? I just committed the mscore_ro.ts file to the repository, so if you could check out whether the translations are really available, we can rule out that it is a problem introduced by the translation server (or at least I hope so).

By pin pointing the strings that are not being translated, we may find a common reason why they don't show up.

Thanks again for the help!

Reply

• Mar 3, 2010 - 07:42

I understand the feeling. Just to say, I strongly believe if we fix one, it will fix all others as well. There is a conversion issue which slipped through along the way. And the more missing translations we will find, the easier it will be to identify the root of problem.

Reply

• Mar 3, 2010 - 23:12

Hi Thomas

First of all, sorry for the late reply. I had to review the Romanian handbook (the translator found my post and contacted me himself via e-mail) and the whole process took about 7 hours.

I compiled a list of strings that, while they are translated, they still show in English in the UI. The list is not exhaustive, there might be other strings as well: I did not specifically look for them, instead I actually played with the program, adjusting translation on the fly, and writing to this list as a side task.

I did not have the time to check out the source of the *qm file either, hope to do this tomorrow. Which is the SVN repo URI?

I also want to ask you:
- what is the "System Flag" string supposed to mean? I've seen the Portuguese translator asked the same thing but got no answer;
- I'd like to also translate the "instruments name" XML file; where do I commit / post that file once it is translated?

Thanks in advance
P.S.: sorry if I'm a little bit inarticulate, but I'm so tired (again). Good luck with bug fixing et all.

Attachment Size
strings not picked up.txt 554 bytes

Reply

• Mar 4, 2010 - 04:23

"System Flag" appears in the text properties dialog box. If you add Staff text then create parts it only exports to the single staff. Staff text has the "system flag" unmarked by default. If you add System text then create parts it exports to every instrument part. System text has the "system flag" marked by default.

To translate the instruments.xml file use a text editor that understand Linux line endings (I use Notepad on Windows). When you are finished attach the file to a post in this forum.

Reply

• Mar 23, 2010 - 15:23

Dear all,

There's been some time since I finished up translating the Muse Score's UI into Romanian. Feedback was scarce, so I just suppose everything was perfect :) (just kidding). I formally "sign off" the Romanian translation and wish that all Romanian users have a nice and pleasant experience using the localized interface.

Some notes:
1) As my projects started to eat up all of my time, I'm, therefore, in the position of "passing the baton" as it's customary in the Open Source projects world. Anyone who wishes to take ownership of the Romanian UI translation is welcomed to do so.
2) The Romanian handbook could still use improvements. I provided extended feedback, but it hasn't been incorporated to date. I suggest contacting Octavian Cudalbu for that.

Take care,
Claudius Tiberiu Iacob

Reply

• Mar 23, 2010 - 17:43

Hi ciacob,

Thanks a lot for leaving this notice. And of course thanks a lot for all your time and effort of translating MuseScore. Your efforts will result in more Romanian user and finally, someone will pop up to take over your work.

" I provided extended feedback, but it hasn't been incorporated to date". Your feedback is logged and will be incorporated. Currently, the focus is on releasing 0.9.6. After that, the translation server will get some coding love again.

Thanks!

Reply

Do you still have an unanswered question? Please log in first to post your question.