Sonar GNU/Linux merges with Vinux

[Linux for blind general discussion]

well, the fact is, Speech Dispatcher is what Orca currently uses, so
	that Orca doesn’t have to keep up with changes to eSpeak’s
	functions. After all, having many communications between
	synthesizers is why Emacspeak’s eSpeak support is so bad in the
	first place, because Raman uses Voxin, and no one else who knows
	how to program cares about eSpeak NG, or, more likely, has a
	speech server but hasn’t put it out there. So, Speech Dispatcher
	is what we have to work with, whether we like it or not.
-- 
Sent from Discordia using Gnus for Emacs.
Email: r.d.t.prater at gmail.com
Long days and pleasant nights!

Linux for blind general discussion <blinux-list at redhat.com> writes:

> I don't understand the advantage an ASCII speech synthesizer has over
> a unicode speech synthesizer, or the advantage of having an
> intermediary between synthesizer and screen reader. Maybe I'm missing
> something, but I would think a hypothetical espeak-unicode that could
> work directly with Orca would work better than keeping espeak ignorant
> of unicode and requiring speech-dispatcher to translate unicode to
> something espeak understands. Honestly, the use of an intermediary and
> having the intermediary handle Unicode support sounds like the
> computer equivalent of telling someone they shouldn't learn a foreign
> language because they can just use Google Translate.
>
> Anyways, I personally think stringing Greak, Hebrew, Arabic, etc. into
> words instead of reading them as individual characters and actually
> being able to identify individual kanji and kana are more important as
> far as unicode support is concerned. Not that I know enough Hebrew or
> Arabic for their proper reading to tell me anything, but I stumble
> upon enough text in those alphabets that the slowdown to read
> letter-by-letter Orca does to be annoying, and it would be nice if I
> could make use of what little I remember from taking Japanese in high
> school.