Fix #338914: Add Medieval/Renaissance clefs

[Jojo-Schmitz]

Resolves: #338914
Resolves: #31554

[Jojo-Schmitz]

@rettinghaus anything more needed for MEI?
Esp. for import?

[XiaoMigros]

Like I mentioned in the linked issue, I think allowing custom symbols for clefs is a much more sensible fix than adding an endless list of clef types.

[Jojo-Schmitz]

Like I mentioned in the linked issue, I think allowing custom symbols for clefs is a much more sensible fix than adding an endless list of clef types.

But that'd be a much larger task. And pretty certainly none for me.

[XiaoMigros]

I'm not asking you specifically to implement it... but I don't think this PR is the right direction.

[Jojo-Schmitz]

I disagree, MuseScore needs to know which line a clef has to go to and what the pitch of that line is.

[XiaoMigros]

Yes, which is the same for these renaissance clefs as for existing ones...
StaffType's lineoffset as well as clef Y-offset exist as well.

[rettinghaus]

Further up in Convert::clefFromMEI there should be cases added to meiClef.GetGlyphName() for the new clefs.

[Jojo-Schmitz]

Like done now?

[Jojo-Schmitz]

Pardon?

[rpatters1]

I agree with @XiaoMigros that continually adding clef types is the road to perdition. But I also recognize that clefs probably need to be refactored a bit to allow for glyph substitution. We are demanding a lot of features from that one tiny enum value.