(devil's advocate mode)
Yikes, that would involve a lot of editing throughout the vap profile. Just thinking ahead, if someone wanted to use this present profile then they would have to learn how these types of non-standard VA commands:-
Set Text [EDDI environment script] to $= is [entering;jumping to] supercruise.
work in order to build further voice commands into their vap..
I know you have done a lot of work with this new TTS engine, which we all very much appreciate, but wonder if it might have been better to explain how these new TTS commands work and how they can be incorperated into EDDI's VA scripts if the User chooses?
Or better still, offer two EDDI vap scripts, one normal, the other using this new TTS speech engine?
Since VA scripts can be 'switched' between muliple VA scripts, i.e EDDI & A.S.T.R.A working together, a default TTS voice between 2 or more VA profiles fits easily together than one that is set to a different TTS voice.
The only non-standard thing in the TTS string is $=, which is explained in the README as being the name of the ship if set and if not the phrase 'your ship'.
Regarding different VAP scripts, it would be a fair bit of manual effort to keep the two in sync and isn't something I'd be interested in doing at the moment. Bear in mind that EDDI isn't meant to be a replacement for ASTRA or similar, but a way of enhancing such scripts with more data and the event loop. In a fully fledged integration I'd expect that the only thing from the EDDI profile that made it in to a custom ASTRA profile would be the event loop, with the user building the rest to their own personal preference.