@harkins2011IV, possible workaround:
in the attached example, I have two staff for the horns (Long instrument name 1,2 and 3,4);
I entered the text 'Horns' (Ctrl + T), by Inspector set it as Instrument name and adjusted the position.
If that's what you mean I'm not sure...
It will be tiresome to manually align them to the instrument names (all for every page). Furthermore, were the staves the extra text is in to be repositioned, it will cause an inconceivable disaster.
It can be done by editing the mscx file. wrap the superscript characters of the instrument name in <sup> and </sup>. For subscript, use <sub> and </sub>
I had hoped that this might work in the mscz file staff properties dialogue, much as 'faux' html tags can be inserted into headers and footers, but it doesn't appear to be the case. For most users, editing an mscx file is 'beyond the pale', so while this solution is functional, it isn't particularly practical.
I don't see a lot of use-cases for this option, but as a graphic designer, I DO think that more control over graphics is better than less. One never knows when one will need a particular graphic function. Perhaps this could be addressed by adding a 'format font' dialogue to the UI? Most WP programs contain something of this sort.
Is something like this possible given the current architecture of MuseScore?
As I recall, there were enough bugs with special characters like "&" being misinterpreted as attempts to create markup and thus resulting in invalid XML in the file - and thus unreadable scores - that these characters always get escaped now to prevent that. Not sure if there is a way around it other than editing the MSCX file.
Comments
Good question.
In reply to Good question. by Recorder485
@harkins2011IV, possible workaround:
in the attached example, I have two staff for the horns (Long instrument name 1,2 and 3,4);
I entered the text 'Horns' (Ctrl + T), by Inspector set it as Instrument name and adjusted the position.
If that's what you mean I'm not sure...
In reply to @harkins2011IV, possible by Shoichi
Oops - I meant to do something like these:
![SScript.png]( "SScript.png")
In reply to Oops - I meant to do by Ragokyo
Same steps, new attachment, if you settle ...
Buona musica!
In reply to Same steps, new attachment, by Shoichi
It will be tiresome to manually align them to the instrument names (all for every page). Furthermore, were the staves the extra text is in to be repositioned, it will cause an inconceivable disaster.
There is supposed to be a way to do this by mixing some kind of formatting code into the text. Does anybody know exactly how to do that?
In reply to There is supposed to be a way by Isaac Weiss
It can be done by editing the mscx file. wrap the superscript characters of the instrument name in
<sup>and</sup>. For subscript, use<sub>and</sub>In reply to It can be done by editing the by jeetee
I had hoped that this might work in the mscz file staff properties dialogue, much as 'faux' html tags can be inserted into headers and footers, but it doesn't appear to be the case. For most users, editing an mscx file is 'beyond the pale', so while this solution is functional, it isn't particularly practical.
I don't see a lot of use-cases for this option, but as a graphic designer, I DO think that more control over graphics is better than less. One never knows when one will need a particular graphic function. Perhaps this could be addressed by adding a 'format font' dialogue to the UI? Most WP programs contain something of this sort.
Is something like this possible given the current architecture of MuseScore?
In reply to I had hoped that this might by Recorder485
My bad—I thought it was the same as header/footers.
In reply to My bad—I thought it was the by Isaac Weiss
As I recall, there were enough bugs with special characters like "&" being misinterpreted as attempts to create markup and thus resulting in invalid XML in the file - and thus unreadable scores - that these characters always get escaped now to prevent that. Not sure if there is a way around it other than editing the MSCX file.
In reply to It can be done by editing the by jeetee
This works, thank you.
I've put up a PR for this for MU4, you'll be able to use
<sub> & <sup>in instrument names just as per<b> <i>etc.In reply to I've put up a PR for this… by Dylan Nicholson1
See #321924: Allow sub and sup tags in instrument/part names