UNIC VS fut

For reference, here is an equivalent library in Rust: https://github.com/open-i18n/rust-unic/

There is also rust-unic which provides both normalization and access to the character database. I have also used this because of their text segmentation support, and I would probably recommend rust-unic in general. I hope to see more progress on that front.

I try to be mindful of making my software as accessible as possible, but the following

> creating a lookup table for all the unicode material out there might've been considered impractical or performance-hitting for the developers.

just doesn't ring true to me in any way for current software. I understand that people can be using older software, which is why I strive to restrict myself to ASCII as much as possible for the widest possible support for my users, but my software also supports unicode identifiers, up to and including a whole unicode table to talk about confusables[1]. And not all TTS software "ignores" characters, which is why people advice against using 𝑓𝑎𝑛𝑐𝑦 unicode because it doesn't get read as text but instead each character is described individually. (This is also something that TTS software should support for their users' sake, but I digress.)

[1]: this is thanks to the crate unic-udc containing this information: https://github.com/open-i18n/rust-unic

Regarding https://github.com/open-i18n/rust-unic, could it be that the project, or otherwise was superseded by https://github.com/unicode-org/icu4x ?

I've just learned that Ć is no longer a viable name (thankfully). Now it's Fusion Programming Language (or fut?) https://github.com/fusionlanguage/fut

Interesting unrelated find: one of the implementations is written in “Ć” which transpiles cleanly into multiple languages: https://github.com/pfusik/cito

For some reason, I recall that Hytale was forked from Manic Digger, which is written in Cito. I could be wrong, but that would mean that Hytale was written in a subset of C# meant to be compiled to other languages.

There is also Ć