Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for the base twelve digits ↊ and ↋ #8

Open
bbuuffyy opened this issue Feb 14, 2024 · 3 comments
Open

Support for the base twelve digits ↊ and ↋ #8

bbuuffyy opened this issue Feb 14, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@bbuuffyy
Copy link

Hello, professional contrarian here. I'm a fan of the shavian alphabet, but I'm also a fan of base twelve. This is a bit of pain since there's plenty of good fonts that support one or the other, but almost none that support both. I was just looking for support for these two glyphs, since I already like this font a lot and would like to get more use out of it (also dont forget to make digit ten not stick out when its set it to text figures (even times new roman flubs this)).

@Shavian-info Shavian-info added the enhancement New feature or request label Mar 11, 2024
@Shavian-info
Copy link
Owner

Happy to add them. Do you happen to know how the turned 2 and turned 3 are treated in 'old-style figures', i.e. the numerals with ascenders and descenders? Does the turned 3 rise above the x-height like a capital letter, or sink below the baseline?

@bbuuffyy
Copy link
Author

I don't know of any standard for how these get stylized (not like much of anything is standard among dozenalists), but having them mirror the digits they're based on seems to work fine. Turned 2 is square and turned 3 has an ascender, like how 6 has an ascender versus 9's descender.

@bbuuffyy
Copy link
Author

bbuuffyy commented Mar 11, 2024

There's also the old American forms where digit ten is a stylized X (usually approximated as χ) and digit eleven always has a flat bottom, even if three doesn't have a flat top. The ↊ form is fairly different from the unicode character and I don't think it's unreasonable to leave it out, but the ↋ form would be a nice option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants