Laurent Pugin

I must say that I am still not sure how you are going to evaluate if this is a printer specific thing when it is going to be highly subjective...

It his also desired when not all the notes are grace notes in the beam? See gracenote-021.mei (and 022)  I do not have a strong opinion on this

Verovio does not make the difference between cue size, grace note size, and does not support small fontsize. Whichever we pick, we need to decide what happens to the beam...

> Does a semi.open list in combination with a data type make sense? Why not? We already have this https://music-encoding.org/guidelines/dev/data-types/data.MODE.extended.html I leave the other questions to tablature experts.

It is done in the tablature customization

Aren't we looking at something like `@ploc/@oloc` and `@ploc2/@oloc2`? `@rotate` will work in some cases but not if you want to allow the horizontal spacing to change dynamically.

Here is a proposal that we discussed with @pe-ro, @kepper and @fujinaga: * We add a `@optimize.angle` boolean attribute that indicates that the slope for the haipin can be adjusted...

`@angle.optimize` is better Because we already have an`@opening` attribute we went for `@opening.vertical`

One other thing to put on that list are horizontal cross-staff beams which stems will quite likely have to be adjusted for the beams to remain horizontal.

> One suggestion would be to replace curvature_CURVEDIR_mixed by curvature_CURVEDIR_mixed_above_below and curvature_CURVEDIR_mixed_below_above. I am not happy with these long names, so feel free to propose better names. Maybe we want...