Nick Giannak III

This is vibe coded, although I should hope it was done responsibly. If there are any issues, report them please. I am using this in production going forward and enjoying it. Again, thanks to all who have come before me, and I hope this is useful to someone besides me.

While working on the fix and realizing I might be on my own, I found myself wondering what Eloquence might be like if we combined Sam's logic with the Rust host of davidacm/NVDA-IBMTTS-Driver, just without the IBM specific plumming? What we get is lower RAM usage and, maybe it's just my ears, lower keypress delay. We still, for now, have the need to copy an executable onto secure screens, there are no interface changes in this version. But we cut RAM usage in half.

Before I say anything, most of the credit for this here goes to @fastfinge and friends and their Eloquence64 project, which until today I considered the most complete, stable Eloquence. However, I had a bug that only I seemed to exhibit regarding unicode handling, and Sam and co weren't comfortable with my fix. understandable.

So here is Eloquence64 19.0-RS-RC1

https://github.com/Nick6489/Eloquence64RS/releases/download/v19.0-RS-RC1/Eloquence-v19.0-RS-RC1.nvda-addon

@FreakyFwoof Ah, well there you go. I think he must have left this slightly incomplete, the addon needs a settings page where you can push the button to copy it. That's logic you can port from the Eloquence addon, either his or mine.

@FreakyFwoof Wow, exe almost identically sized to the Pythonic Eloquence64 host process, and I even recognize some of the host.py logic. This tells me that the maintainer did base his process on Eloquence64 which *does not* copy the host on its own unless you specifically push the button int he Eloquence page. This is a defect of the design choice made in using an exe host - it doesn't have to be this way.

@FreakyFwoof Is there a repo where I can take a look at the synth and its wrapper?