I also made a little decimal to Cistercian translator once. The numerals aren't in Unicode, so the font I use has to make use of private code points, which was kind of fun to get working properly. <https://cistercian.micahrl.com>
However, it says:
> It is not clear that there is any current need for Unicode support. Western Michigan University’s Medieval Institute (Cistercian and Monastic Studies) has a digitization project of Cistercian mss, but as of end 2020 they have not expressed any desire for computer encoding of the numerals. This document is therefore background information so that work is not duplicated if a need arises later.
But at least they have the multiocular O, I guess.
Here's a demo of it in action on the author's blog: https://www.hsablonniere.com/a-clock-based-on-cistercian-num...
I ended up using that library to create a simple Cistercian clock screensaver. My hope was that I'd learn to read Cistercian numbers fluently though I'm still working on that.
D'ni numerals overlay two base-5 values in the same space, one horizontal & the other vertical, to represent 0–24. There's even a one-character numeral for 25, though it rarely comes up in-game. Different, of course, but I wouldn't be surprised if Cistercian was the inspiration.
https://en.wikipedia.org/wiki/Kaktovik_numerals
It's not a base-5 system exactly. It's base-20, where the rotated-and-superimposed digit is only one of the first three numerals. I guess you could call it a mixed-radix system, where the bases alternate like 4 5 ... 4 5 4 5 and where each group of 4 5 combines into a single symbol.
I feel like there's a missed symmetry here though and almost symmetrical things are like a wobbly tooth in my brain.
The right line appears at 6, but if you added that at 5 you could repeat the pattern you did for 1-4 for the horizontal lines, which it almost does. 7 and 8 are 6+1 and 6+2.
Change 3 to 2+1, 6 to 4+2.
8 takes the current 6, and 7 becomes 6+1, 9 becomes 8+1 (current 7). That also gives you hex digits to work with for free, each symbol could store up to FFFF.
It wouldn't change a lot, just removes the downstroke from 3. Of course, 4 bits is an arbitrary choice, one could keep the current 5 bit/segments as well, but not much is needed to normalize it to 4 bits, which is interesting in itself.
Show HN: A CLI tool to generate Cistercian numerals - https://news.ycombinator.com/item?id=27853033 - July 2021 (5 comments)
Cistercian Numerals - https://news.ycombinator.com/item?id=26523363 - March 2021 (66 comments)
For example, here’s a nifty Cistercian numeral generator: https://shelby.cool/#/sketch/cistercian-numerals
"Brittle" because you're peacefully sitting there at 9999 coins or whatever, and you earn another one, and suddenly you can't represent it. Arabic (Hindu) numerals just slap another digit to the left, but Cistercian numerals break.
(You could fix that by using an Arabic notation - two Cistercian numbers, with the left one meaning "multiply this by 10,000". At that point, Cistercian numbers become a compressed Arabic notation. Still harder to use for arithmetic, but that's true of many compressed formats.)
I wonder if these constraints are inate to the problem (inescapable trade-offs) or circumstantial to the particular choices of the Cistercian monks...
Any compressed format is hard(er) to use for arithmetic. Pretty much any grade-school kid can memorize the addition table, and can work it out on their fingers if they forget. But that table only has 100 entries. The addition tables for Cistercian numbers has 100,000,000 entries; nobody will memorize that.
But maybe I'm thinking wrong. Cistercian numbers really only have 0-9, in four possible orientations. So maybe you can just add them, going from units up through thousands, writing down each quadrant as you go. (Multiplying still looks like a mess, though...)
(I'm not the maker, I just noticed these last year on Tindie and picked up a couple.)
you can still email the author. he would love for someone to continue the research
* Each stroke were 1 bit, so the numerals would be just a more "compact" representation for binary numbers.
* Even better if they can be represented with a seven-segment display (or other similar displays).
(Though I can't blame them, since these two things didn't even exist back then.)
The 'obvious' answer is to have a second glyph (and third, etc.), but that's rather a boring answer.
Perhaps making a cross-shape so you have four-arms to work with (and can thus get to 10.000.000).
Or making a capital H shape would let you have the next four digits, which could then be extended out indefinitely; |-|-| etc.
Or, indeed, you could make an array out of them, making a super-glyph (kind of like a block matrix). Four blocks of four digits would get you to 10^4^4 = 10^16 so 100,00,00,00,00,00,00,00 (or 10000,0000,0000,0000, or 10,000,000,000,000,000 depending on your grouping), which is 10 Quadrillions in short- scale. Obviously grouping digits by blocks of 2 or 4 makes mor sense, since that's a row or a glyph.
Interesting discussion though, which is probably the goal here, rather than a good or bad reply: it allows you to see how the candidate thinks or approaches a problem.
I love it because it’s very open-ended and demonstrates problem solving. It’s a great conversation piece.
But the real answer to any "how would you...?" questions is to reply with "Who are the users and what are their needs?"