You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the dozenal system, you would count 1, 2, … 9, ↊, ↋, 10
Some people use a and b or other glyphs. But the dozenal society of Great Britain suggests ↊ and ↋ and they have unicode slots: U+218A (↊)
and
U+218B (↋).
To include them, all that needs to be done, is to put a copy of 2 or 3 in the unicode slots and turn them 180°.
Would make this font much more complete for me!
Should I post this issue in source-sans too?
The text was updated successfully, but these errors were encountered:
Interesting – thanks for explaining these code points!
Would you have examples for other fonts including these glyphs? The only one I find on my machine is Everson Mono …
Real-world use examples are also welcome.
If you are interested in having these glyphs included in Source Sans/Source Code, please post an issue there as well. This issue can link back to here.
This is in deed a problem, most Fonts I have don't include these. That's why I often add them myself if I like a font. I even edited my computers keyboard layout in order to type them easily.
The glyphs are only there for the dozenal system so you don't have to use letters. The number 1↊7↋ looks much more like a number than 1a7b. They are called the Pitman digits, as Isaac Pitman suggested them. More about the dozenal system on wikipedia: https://en.wikipedia.org/wiki/Duodecimal
Missing turned digits 2 and 3 (↊ and ↋)
When using the dozenal system, you would count 1, 2, … 9, ↊, ↋, 10
Some people use a and b or other glyphs. But the dozenal society of Great Britain suggests ↊ and ↋ and they have unicode slots: U+218A (↊)
and
U+218B (↋).
To include them, all that needs to be done, is to put a copy of 2 or 3 in the unicode slots and turn them 180°.
Would make this font much more complete for me!
Should I post this issue in source-sans too?
The text was updated successfully, but these errors were encountered: