|
Top-level
 @neauoire @neauoire If you haven't already, make sure to read about the difference between code points vs graphemes vs grapheme clusters. Thinking in terms of "characters" tends to lead to trouble because the word "character" could refer to any of those things. Depending on your level of commitment to international text support it might also be worth getting your head around e.g. the role of technologies like HarfBuzz in text rendering. 2 comments
 @evan Just to be clear, I'm not inventing a new specification, but following the utf8 codepoint map. The permacomputing approach to text editing is likely not to build some sort all encompassing textarea system, but rather just having people implement enough of their own language that they can get their tasks done. In any case, I thought UTF8 would be out of reach from something like uxn, but it isn't that much trouble after all, at least at a scale that I need. |
Gregory's Server
@evan I doubt I will cover much more than what I need to do my work. My goal here was merely that if I encounter a multi-byte glyph, I can walk over, erase, select it properly, instead of say having to walk over 4 spaces in memory for a 4 byte glyph. At least that part, is well designed via utf-8 and I haven't found exceptions yet that Left couldn't handle.