@amir@fastfinge It's crazy that everyone is layering it in wrappers nowadays. Do you know if codefactory are doing the same with their new android build?
@FreakyFwoof There is a 32-bit compatibility layer in the works for NVDA itself (although it currently only references SAPI4). But with any luck the need for every add-on to implement its own will go away.
@jscholes@cachondo@FreakyFwoof@amir My understanding is that when this comes to addons, it's going to require some kind of secure addons API/layer. And it won't be ready for 2026.1, or maybe not even 2026.2.
@fastfinge Where are you getting the first part of that understanding from? I.e. the dependence on the secure add-on runtime. @cachondo@FreakyFwoof@amir
@fastfinge I see the "Secure add-on runtime" on the roadmap, with the note that "The first version of the runtime will provide support for speech synthesis and braille devices."
I don't see any implication that any 32-bit compatibility layer will only work for secure add-ons, which is hopefully a bit of a leap.
Still, the fact that people don't know what will or won't be happening, or whether their preferred synthesiser(s) will work or not, continues to be a big part of the problem. @cachondo@FreakyFwoof@amir
@jscholes@cachondo@FreakyFwoof@amir That's my assumption because the only things that really need a 32-bit compatibility layer are speech synthesizers and braille devices.
@clv1@jscholes@cachondo@FreakyFwoof@amir The issue is that both of these are effectively concatenative or parametric, rather than formant, systems. So they will never be as intelligible as eloquence.
