Score information (Transifex)
See section left:
Maybe I have not found them (where to look for?)
Do you still have an unanswered question? Please log in first to post your question.
See section left:
Maybe I have not found them (where to look for?)
Do you still have an unanswered question? Please log in first to post your question.
Comments
Those are not translationable
In reply to Those are not translationable by Jojo-Schmitz
Grazie Jojo, it seemed to me, trying to translate the manual came the doubts.
Have a good day.
In reply to Grazie Jojo, it seemed to me, by Shoichi
Those may need a toolkit.
Has the Italian handbook been added to the Pdf generator?
In reply to Those may need a toolkit. Has by Jojo-Schmitz
No, I have not addressed the issue. I'm sorry but I can provide only "low manpower" and the work is far from being completed...
In reply to No, I have not addressed the by Shoichi
It's not you to address that... Would be Thomas or lasconic.
In reply to No, I have not addressed the by Shoichi
See #60921: Enroll Italian handbook for PDF export
In reply to Those are not translationable by Jojo-Schmitz
Hi Jo-jo,
What do you mean by it is not translationable? Everything is translationable :-)
The title of the Info window is already translatable, The MuseScore version string as well as the buttons. So why not the rest?
It would indeed be nice to have this tiny bit fixed when the rest of MuseScore is translated.
In reply to Hi Jo-jo, What do you mean by by Jwagner
These tags are directly read from the score, so they can't get translated, not automatically at least.
In reply to These tags are directly read by Jojo-Schmitz
I'm sorry for being persistent, but I assume it is written into the score by MuseScore, so it should be translatable? Am I missing a point here?
In reply to I'm sorry for being by Jwagner
Assume it is written into the score in German and you open it with Italian settings, it would still be in German.
You can invent your own tags and they will be taken as is, no translation will ever take place.
Similar BTW to custom text styles.
In reply to Assume it is written into the by Jojo-Schmitz
OK, but why save the tags? Today apparently they are saved in English. If they are kept that way couldn't MuseScore do a translation when opening the score? So you get it in German, and I get it in Danish?
I'm not sure if inventing my own tags will solve my problem as you would still not get them in German.
Is there a description on how to create your own tags available?
In reply to OK, but why save the tags? by Jwagner
I don't think the mention of creating your own tags was meant as a solution, but as an example of why full automatic translation is not possible in general. The set of tags is not some fixed set of known things; it's whatever you want it to be. If you create a tag called "project", there is no way MuseScore can translate that. I guess it might theoretically make sense to try to translate the "known" tags for display in the dialog and leave the unknown ones untranslated.
As for how to create your own tags, just press the "New" button in that dialog.
In reply to I don't think the mention of by Marc Sabatella
Although there are a bunch of tags MuseScore does create for every score.
Just like there are a bunch of text styles..., so it might be possible to translate those too, but I don't think this is a good idea, as they are to be used in their untranslated form in header/footer.
In reply to OK, but why save the tags? by Jwagner
@Jwagner
![Tag.png]( "Tag.png")
I was referring to the nomenclature, and since "I started it," I try again:
On the contents of the cells I have no doubts (and not even in your patience)
Regards.
In reply to @Jwagner I was referring to by Shoichi
And as I mentioned these names are to be used as they are ($:tagname:) in header/footer, so I don't think it to be a clever idea to translate them (just the ones that MuseScore adds by default, for others it would be plain impossible anyway). Those first 3 are not really tags, so they can get translated, but also not been used in header/footer...
Sheet music gets around the issue of translation by using a few standardised terms and simply not translating them (e.g. "allegro" is never translated from Italian, so now it is in the English dictionary). Perhaps a similar approach can be used here? Arguably it is being used already since they are in English ;)
The only alternatives I can see would be to give a list of commonly used tags in the "New" dialog and provide automatic translations for these (custom tags would not be translated), or to have a "language" tag that sets the language for the score itself and then all other tags would be hard-coded into the score in that language.