@twynn Not surprising. Eloquence itself doesn't support anything but the English alphabet. For Korean, Japanese, and Chinese, it actually has separate DLL files that turn all those characters into letters from the English alphabet, and then reads the text that way. That's why if you switch the Eloquence language to Korean, it can suddenly read hangul, and when you switch back to English, it can't anymore. We can't really fix that without the eloquence source code.
However, the problem I'm trying to fix is with eloquence loading at all. If you have any unicode or non-English characters in your Windows username, the addon will fail to load, because Eloquence can't read those characters, so it can't find its own .ini or .dll files because it can't access your user folder. That means you can't even use Eloquence in English. I need to figure out how to encode those paths so eloquence can deal with them.
🇨🇦Samuel Proulx🇨🇦
@fastfinge@interfree.ca