get sextants into cascadia code

[dankamongmen]

this is the default font for the new Microsoft Terminal, but it sadly lacks sextants. if it had them, maybe we could enable sextants for windows, and thus the NCBLIT_3x2.

[dankamongmen]

microsoft/cascadia-code#607 has been filed; let's see what happens

[j4james]

Just be aware that even if the font supported sextants, you're still not going to be able to use them in Windows Terminal because of the way astral plane characters are stored (they require two cell positions in the buffer). You can see the effect that has in the screenshot I did of the notcurses-info output here: #2117 (comment)

[dankamongmen]

@j4james always up in here pouring cold water on my dreams =]

[j4james]

Sorry. 😉 If it's any consolation, it will get fixed eventually, so it'll still be good to get those characters supported in Cascadia Code. I just wanted to make sure you were aware of the current Windows limitations, so you don't feel like you've wasted your time on this when it doesn't pan out.

[dankamongmen]

i assure you your comments are worth their weight in gold; please keep them coming. on this kind of thing, i see "we need both sextant glyphs and proper display thereof to enable NCBLIT_3x2". if i can assist in getting one half done, that means i can execute as soon as the other half is completed, and hopefully provides incentive for others to do the latter half.

[dankamongmen]

so yeah, i've filed a bug and volunteered to do the work over in their repo; there's not much more we can do here.