Open jmcwilliams403 opened 1 year ago
I have to say those "fused" ligatures are extremely hard to deal with.
These are going to be so messy with all those u/v/y variants lol
(though i guess ignoring them for now is also one way to do it, idk)
Anyhow, here's what Brill does for VY for reference (about the VY or W-with tail variation):
These are going to be so messy with all those u/v/y variants lol (though i guess ignoring them for now is also one way to do it, idk)
For what it's worth, lowercase ae and ao etc. are configured to always use double story 'a' anyway because italics would otherwise make them look identical to oe and oo. Always using a stable form of v and y etc. would be perfectly reasonable here.
Could we at least start with Ꜷ/ꜷ since it might be the easiest one?
Curious: what's the point of these? Looking at those Noto examples and guessing what letters I'm looking at, I mostly guess wrong.
In order, they look like:
@jmcwilliams403 Actually it is much harder than what people would think, because it requires blending shapes together.
@AndydeCleyre Looks like they're among 112 characters added to the Latin Extended-D block in Unicode 5.1^1 courtesy of MUFI, the Medieval Unicode Font Initiative. They're supposed to be useful for transcribing abbreviations in Medieval texts.
@ron-wolf Thanks for the explanation and context!
If Ꜹ
/ꜹ
is added then the range of combining Latin letters in Combining Diacritical Marks Supplement can finally be completed:
U+A376..U+A37D, U+A760..U+A761 Noto Sans Mono: Disclaimer: I put VY under regular Noto Sans here because I personally disagree with Noto Sans Mono's VY glyph.
It's technically not supposed to be based on a W, but then again W is also historically based on two V's anyway, so do whatever you want with that information.
For what it's worth, this is how Noto Sans Mono actually does it: Again, I'm only nitpicking here. You can handle this glyph in whichever way you prefer.