sapi4activeVoice and sapi4serotek do not always handle interuptive messages properly

[mdcurran]

When using both sapi4 drivers (sapi5 does not have this problem) some interuptive messages, such as "loading document..." in virtualBuffers, does not stpeak. It most likely has something to do with the first speak being lost after a cancel, if the speak is in the same cycle/event.

[jteh]

This is because we start rendering the buffer immediately after speaking the "Loading document" message and window messages do not get pumped enough for the message to be spoken. (SAPI 4 requires messages to be pumped in order for it to speak.) We either need to pump enough messages for the message to be spoken or pump messages while rendering virtual buffers.

[jteh]

This is actually caused by the old virtual buffers not yielding as they build the buffer. SAPI4 requires that window messages be pumped in order for speech to occur. By the time messages are pumped again, the document has finished loading, so the "loading document..." message is never spoken. Thus, this is actually an issue with the old virtual buffers, which are no longer being maintained.

[zvonimir1]

(In #206) hmmmm this synth needs to be added to test version

[jteh]

(In #206) Please don't change the ticket information unless you have a particular reason to do so.

The Newfon synth itself will never be added to NVDA because it is not open source and has a restrictive license. See the previous comments for more details.

The NVDA driver for the Newfon synth will be added after 0.6p3. It cannot be added to 0.6p3 due to the language string freeze as noted above.