3 ms·
Only halfway related, but a long time ago I had an idea for a character encoding that was stroke based. In other words, based on minimal stroke primitives (lin
by crazygringo 4y ago
Only halfway related, but a long time ago I had an idea for a character encoding that was stroke based.
In other words, based on minimal stroke primitives (line, arc, circle, etc.) that were placed not with any exact coordinates, but simply in relation to each other conceptually and with crude size/position categories. E.g. "downward stroke, top to bottom" is a capital "I" while "downward stroke, middle to bottom, dot closely above first stroke" would be a lowercase "i". And then for matching forms with different meanings, there would be a final "family" selector, e.g. to distinguish an em-dash from the Chinese character for "one", or an en-dash ("punctuation" family) from a minus sign ("math symbol" family).
And then a suitably compressed bit encoding for the instructions. So in the end, something like "I" might just be 3-4 bits long, while a complex Chinese glyph might be 60 bits.
But the main feature being that a font renderer could always draw a primitive version of any glyph, even if you don't have it in a single font anywhere, because the character code itself encodes it. And then that character codes wouldn't be just something totally arbitrary invented by Unicode, but inherently meaningful, and anyone could be free to invent any character they wanted, that would always been drawn by any software, no Unicode gatekeepers needed.
Obviously it's not terribly practical, for a whole host of reasons. But I still sometimes think about how elegant it would be to have a "geometric" self-describing character encoding, and to get away from all of the political decisions around language scripts and where they get put in Unicode and in which version.
- bradrn 4y agoProblem is, how do you define these representations in the first place? For one thing, some characters have multiple different forms… like a/ɑ, or g/ɡ [0]. Then you have characters which differ only minutely — like Thai ช/ซ, or Ethiopic ሀ/ህ, or Cherokee Ꭺ/Ꭿ. And, worse, those characters can also look entirely different between fonts (see e.g. [1] for Thai). So by the time you’ve finished working through all those choices, and created a format which can distinguish them all, you’ve effectively created yet another font — just in a very lossy vectorised format. Or if you go the opposite direction, and expect each individual character to make its own individual choices in this regard — well, that basically has the same problems as PDFs: it may look good, but it’s totally impossible to process programmatically, since it overspecifies the visual details at the expense of semantics. And although that might be fine and even desirable for certain usecases, it does limit the places where this format could be used. That being said, I can certainly see possibilities and places where this could be useful to me. Perhaps I’ll have a go at implementing this someday. [0] In case those look the same in your font, here they are again: a/ɑ g/ɡ And in case those look the same too, then… well, have a look at the codepoints in the Unicode reference charts, I guess! [1] https://wrdingham.co.uk/thai/tellthai_preface.htm https://wrdingham.co.uk/thai/tellthai_preface.htm
- crazygringo 4y agoYup, I didn't say it would be easy. :) But initial thoughts are simply that characters would be defined "canonically" (for progammability) with fonts free to vary stylistically as desired just as they are now (for the classic single- and double-story 'a' and 'g' you mention, for instance.) While minute differences within any language should be handled by the strokes themselves or else the final "family" selector I mentioned when strokes are identical (is it an en-dash or a minus sign). Again, more of a thought experiment of how character encoding might have gone a different way in the past. And because canonical forms would be required for interoperability it would still need a coordinating body (like Unicode) to standardize them, but people would still be free to encode their own meaningful characters outside of the standards (such as rare/ancient family name characters in Chinese that aren't in Unicode). What's really fun to think about is how rendering libraries might even use machine learning to draw glyphs when no font glyph is available, in the style of an existing font, whether a garamond serif, or brush Chinese.
- lifthrasiir 4y agoYou will appreciate RFC 5242 [1]. [1] https://datatracker.ietf.org/doc/html/rfc5242 https://datatracker.ietf.org/doc/html/rfc5242
- crazygringo 4y agoVery interesting, than you! I always thought I couldn't be the only one with this basic idea, fascinating to see a related proposal for it.
- lifthrasiir 4y agoPlease note the publish date. ;-) (But the proposal itself is detailed enough that you will still appreciate it.)
- bentcorner 4y agoIt's an interesting idea, my first thoughts are how do you make it machine readable. Like if you're writing a browser how do you translate something that "looks" like google.com and know you need to go to google.com and not googIe.com? Maybe you don't bother (i.e., don't try to parse bytes in this encoding as plain text) but that has a bunch of consequences too.
- bradrn 4y agoThis is basically the point (or one of the points) I was trying to make in my sibling comment; thank you for expressing it much more clearly than I did!
- keybored 4y agoSounds like a glyph encoding.