Open oshaboy opened 7 months ago
i don't know either, but aside, can you show the font? it would be really cool to have
Yknow that feeling when you do a project and halfway through you're like "No wait I should do it that way"... well I got that with my font.
My font is incredibly basic anyway everything is just plain rectangles.
Turns out Becky was way ahead of me. They have been added into Fairfax at U+FF820-U+FF823F.
Though from my own experimentation I found it quite useful to group it into octets so maybe adding the "Combine digits" would be useful. Though I understand that Fairfax is a fixed width font so having such a thin digit won't work.
perhaps a different way would be using some "LUCILLA DIGIT BAR" and then "LUCILLA COMBINING DIGIT ZERO" and "LUCILLA COMBINING DIGIT ONE" to encode a given meta-radix, though this would take much more space without compression, and there's already a section of trimmed binary, quaternary and octal pieces.
as i was writing this i realized there's already a "LUCILLA OCTAL DIGIT ZERO" and so on, so this is an unneeded comment for the radix 16 and below.
so close issue or wait for UCSUR proposal?
my bad, i realize this is an unofficial UCSUR proposal already
The thing is I kinda found myself often combining the digits in groups of 6 or 8. So that would be quaturo-sexagesimal and I guess sex-quinquagint-duocentesimal.
I think having a flexible way to tie digits just like was proposed by Lucilla would be better though I understand it doesn't work well with the fixed width font. Also using 2 Private Use Plane codepoints for every bit isn't very efficient.
maybe a more efficient way would be adding some sort of "LUCILLA COMBINING DIGIT CONNECTOR" like tie bars to connect 2 hex bytes or octal bytes. it's still possible to group into any number, but should be much more efficient for many more groupings.
posting this multilingo keyboard layout, might be useful. it's my current layout, with Lucitone number forms (and one underlined ones because why not) on shift.
OK_Layout_Begin
Name:Lucilla
1234567890
qwertyuiopð[MC:ae]
[MC:th]asdfghjklö´
[MC:ng]zxcvbnm
[4D:[MC:] [MC:][MC:][MC:]][4D:[MC:][MC:][MC:][MC:][MC:]][4D:[MC:][MC:][MC:][MC:][MC:]][4D:[MC:][MC:][MC:][MC:][MC:]][4D:[MC:][MC:][MC:][MC:][MC:]][4D:[MC:][MC:][MC:][MC:][MC:]][4D:[MC:][MC:][MC:][MC:][MC:]][4D:[MC:][MC:][MC:][MC:][MC:]][4D:[MC:][MC:][MC:][MC:][MC:]][4D:[MC:][MC:][MC:] [MC:]]
QWERTYUIOPÐ[MC:AE]
[MC:TH]ASDFGHJKLÖ´
[MC:NG]ZXCVBNM
£¥€$₹^&*()№×÷±
~`{}%_-=|+§∷‡¶
@[]#/\'"«»—‐–✓
…<>!;:?‹›√∛
ˉˋˇ´¨˙˚¸﹐˛˘˜ˆ
―∑éə®†Ωœøπ•·¡
æß∂ðƒ©ªº∆≠℥∞¿
ʒΩ≈çþ∫ŋµ≤≥°
OK_Layout_End
Based on Lucitone's binary notation. On which the youtube video the best way to count by the best way to count is based.
I haven't selected codepoints yet. I am discussing it with an internet friend and we are in disagreement on what the codepoints should be.
The characters I want to propose are: Binary Figure Space - Space the width of a binary digit. The binary digits proposed are very thin so I feel like this might be useful. Binary Underline - Combining character to combine two binary digits. Radix Point - Self Explanatory. Rep Mark - proposed as a way to write repeating fractions. Also a combining character. Binary 0 - Short vertical line Binary 1 - Long vertical line.
I already made a basic font for these based on my own code points assignments and it works fine. How do I propose characters to the UCSUR?