See title. Fix this. It's an accessibility issue.
From what friends were able to deduce, it's because the /tts command likely forwards it to the Windows TTS reader instead of the app actually doing the work itself.
Linux obviously isn't Windows. I can only imagine that MacOS has this issue as well.
Войдите в службу, чтобы оставить комментарий.