UNIC VS wincompose

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 ?

Touche compose. Natif sous linux, et sous windows : https://github.com/samhocevar/wincompose

Julia has made symbol input manageable and lets you define infix operators for many of the Unicode symbols that make sense for that. [1] And JuliaMono was designed to support the symbols that Julia does. [2]

I generally do quite fine with my Compose Key configuration, though (even on Windows, where I use WinCompose). [3]

[1]: https://docs.julialang.org/en/v1/manual/unicode-input/

[2]: https://juliamono.netlify.app/

[3]: https://github.com/samhocevar/wincompose

On Windows, I use http://wincompose.info/ for all my special-character needs (and use the system compose key on Linux).

na windowsa jest sobie WinCompose

Credit to wincompose's GUI for inspiration, which provides similar functionality on Windows.

I’ve previously used a nice little tool called WinCompose for exactly that. Looks like it’s still going:

http://wincompose.info/

Malgré to, yo recomanda WinCompose o simil si tu es in Windows.

I use WinCompose which gives me the same compose-key functionality that's built into Linux. I've chosen one key on my keyboard to be the Compose key (I use Right-Alt, but you can pick any key that's convenient). Then I can type

Assuming you are on desktop/laptop:

The long-winded way is to use your OS's character map tool: find the glyph you want there and copy+paste. Under Windows 10+ there is the emoji keyboard (hit [win]+;) which also gives access to much more including super-/sub- script characters, which is a little more convenient than character map. Presumably other OSs have similar available too.

Better is to have support for a compose key sequence. Usually build in to Linux & similar, you just might have to find the setting to turn it on and configure what your compose key is. Under Windows I use http://wincompose.info/ and there are a couple of similar tools out there. In any case it is useful for more than super- and sub-scripts: accented characters & similar (áàäæçffñ), some fractions (¼,½,¾), other symbols (°∞™®↑↓←→‽¡¿⸘♥⋘»‱), and configurable too so you can make what you use most easiest to access (and if you are really sad like me you can do something https://xkcd.com/2583/ to type hallelujah too!).