unidecode

It's a design decision. On one end, if I'm reading your question correctly, you could use 0xFFFD (the replacement character) for anything not recognized as language-specific characters in the BMP and SMPs (this can be done within practically all existing Unicode libraries by filtering on character class) which will inadvertantly filter some non-emoji symbols and doesn't really convey any information (it can even look unprofessional, it reminds me a lot of the early web during the pre-unicode growing pains of poorly implemented i18n/l11n). There are libraries like Unidecode[0py] [0go] [0js] which convert from unicode to ASCII text that might be easiest to include in a TUI. All the ones I looked at will convert emoji to `[?]` but many other characters are converted to that, too, including unknowns. On the other end you can keep a running

This looks pretty cool! Is this basically efficient/scalable fuzzy object matching? IMO, it would be super useful to have some performance benchmarks – how fast is this for 1k/100k objects? How does that compare to other approaches etc Not sure how feasible these are, but features I would find super useful: - string matching across languages in different scripts (with something like unidecode maybe? [1]) - fuzzy matching that includes continuous variables like lat/long, age etc Excited about using this – will be following the repo very closely! [1] https://github.com/avian2/unidecode