Support for a underscore just below the baseline (v-underscore-mid)

[jfrankenau]

I am intrigued by the v-underscore-low variant. However the underscore sits a little bit too low for my taste. Therefore I'd like to propose a v-underscore-mid variant where the underscore is just below the baseline.

[be5invis]

Interesting. There's already glyph underscore.belowBaseline but it is not exported as a selector. Move into backlog since v3.0.0 is currently feature locked.

[AlsoScratch]

A mid-height underscore sounds nice! I hope you can work on it soon.

[be5invis]

@AlsoScratch Well one big problem is that I am running out of cv## tags... There's only cv99 left now!

[AlsoScratch]

You said you could use CVAA, CVAB, ..., CVZZ. That's an additional 676 variants.

[throwaway571]

The problem is that custom tags aren’t standard, and might not be supported even by OpenType-compliant applications.

One possibility is to remove the individual curly tags and unify all of those font variants under the ss20 tag, but that would break backwards compatibility, and remove some (admittedly minor) possibilities for customization. I don’t think anyone would want to mix and match straight and curly glyph shapes for A V W Y v w x y individually, for example.

But Iosevka already uses custom tags for ligation sets, so I don’t know which is better.

[AlsoScratch]

I know they work in VSCode at least.

[be5invis]

I'd like to do such a change:

• cv20 will be mapped to the underscore right below baseline.
• cv21 will be mapped to the underscore right above descender.
• cv99 will be added and maps to the old "high" underscore (right above baseline).

[be5invis]

Close as fixed.