Re: Fritz Will Be Digging Into This - Window-Eyes Scripting Introduction

  • From: "public.niran" <public.niran@xxxxxxxxx>
  • To: <programmingblind@xxxxxxxxxxxxx>
  • Date: Mon, 14 Apr 2008 11:52:22 +0530

virtualy everyone on this list will be interested to read such info..
From where did you get it? Is there any public place from which I can download it? Can you also send me a copy?
Niran
----- Original Message ----- From: "Mario Percinic" <mario.percinic@xxxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx>
Sent: Monday, April 14, 2008 11:27 AM
Subject: RE: Fritz Will Be Digging Into This - Window-Eyes Scripting Introduction


Sure my friend, let me just brows thru my very big archive of ebooks and
i'll send it to you. Don't worry it will be today :)

-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of inthaneelf
Sent: Monday, April 14, 2008 2:14 AM
To: programmingblind@xxxxxxxxxxxxx
Subject: Re: Fritz Will Be Digging Into This - Window-Eyes Scripting
Introduction

Mario, in your last message, you said "I have the documentation about SAPI
synths and how to make them, I can send you the book about it."

would you send me that book/information please, there have been folks
looking for information like that out here, smile.

thanks,
inthane
----- Original Message -----
From: "Mario Percinic" <mario.percinic@xxxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx>
Sent: Sunday, April 13, 2008 4:07 PM
Subject: Re: Fritz Will Be Digging Into This - Window-Eyes Scripting
Introduction


Well since you brought up some very good questions,let me break this
message into logical pieces and give you the answers.

----- Original Message -----
From: "Octavian Rasnita" <orasnita@xxxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx>
Sent: Sunday, April 13, 2008 9:26 PM
Subject: Re: Fritz Will Be Digging Into This - Window-Eyes Scripting
Introduction


"Yes, of course I am lazy. So? Is this a problem? :-)"

No ofcourse not, everyone chooses its own way. I was just stating how
the situation in general works with blind popularity, no matter in
what country you are. Ok ofcourse, in smaller countrys like Romania or
Croatia in my case, the situation is harder but than the person has to
see if the solution can be adapted for your language considering the
best results, financial situation, amount of people who work on the
project, timing, knoledge etc.

"I don't think I can build a software synthesizer at least as good as
US Eloquence by just reading the documentation and making research,
without knowing C/C++."

Correct, but i never said that. When i said that you can checkout
espeak, i thought that you will find the documentation and the web
page considering the thinks you did in the past. In order to make
better improvements for espeak you really don't need to know c plus
plus, ok if you know it better for you, but still you can see what
sounds wrong and what you can do to make it sound better or to
pronounce different characters or words, and also make different
voices which really can sound completely different.


"There are more romanian synthesizers, but I don't like any of them,
and they all are made by software companies that have more good
programmers.
One of them sounds pretty good but is very slow responsive, another
one sounds like a robot and it doesn't work at a higher rate, another
one sounds very very bad (the one which is made by the german company
Baum, that company that made Gnopernicus screen reader for Linux, and
Virgo screen reader for Windows)."

If some company has more developers employed that doesn't need to mean
anything. In my case, software solutions which were made by an
individual showed up as better because the developer really showed
more interest that his aplication works with all screen readers,
languages, protocols etc.
I worked on almost all software synth development exept Check
wintalker voice which is also have adapted for Croatian language.
I told you to try and join espeak development team for Romanian mainly
because espeak is right now used under windows as a sapi 5, as a stand
alone portable version in windows screen reader called nvda, and orca
for linux and also it can work with mac. So lots of platforms are
supported, just because its author is very open minded and accepts
lots of suggestion as long as the person knows language rules and
something about computer usage.
If you need more info about speech synths you can contact me privately
and i'll write you more about it.


"Even if I would know C/C++, I don't think that it would be easy
enough to create a better synthesizer than US Eloquence.
And by the way, where can we find documentation about how to create a
synthesizer at least as good and fast as Eloquence?
I am asking this, because you seem to be very well informed..."

I have the documentation about sapi synths and how to make them, i can
send you the book about it. Eloquence as far as i'm aware came out
from IBM's via voice which became eloquence at the later time.
Eloquence belongs to the group of formant speech synthesizers and that
explains one of the sides why is it so responsive.
Mario
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind




__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind


__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind


__________
View the list's information and change your settings at //www.freelists.org/list/programmingblind

Other related posts: