On Sep 10, 2006, at 11:33 PM, Cheryl Homiak wrote:
Well, if multitasking is beyond your control, using visiovoice for reading or converting to audio isn't really practical for me right now. I do lots of other multitasking with speech so I don't fully understand why this is beyond your control; I run cspeech and speechissimo while doing other things that require speech though I realize those programs do have significant differences from visiovoice.
cspeech uses some kind of trick that hogs the processor, which maybe a solution for export to audio, but not for other uses.
Speechissimo does not use Mac Speech Manager compliant voices, but uses its own communication with its built-in voices as far as I know, so it is not bitten by the VoiceOver-Speech Manager bug that causes audio to be interrupted by VoiceOver. That's nice, but then you won't be able to use Speechissimo with the Infovox iVox voices or with Apple's voices.
And yes, I did read your comments about why you used carbon but it has always been my impression that cocoa was to be preferred for vo- accessible apps; not sure why you were told differently.
Apple wants to keep is message simple to end-users so they come up with these kind of statements, maybe also partly as an excuse for not making iTunes accessible. Reality is that except for some bugs in Apple's own code one can make both Carbon and Cocoa applications just as accessible. Apple's own Pages and Keynote are not very accessible for VoiceOver, yet they were done in Cocoa, so using Cocoa does not guarantee accessibility either.
david.
