speakup sftsyn driver

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Does this happen with anyone else?

Some of us prefer not to use the pitch change for capitalization when 
using speakup. The way to do this is to replace the contents of 
caps_start with the work cap and a space, and to replace the contents of 
caps_stop with a space. Then when you run Steve's speakupconf script to 
load the new configuration, it works.

The trouble comes when you are using the sftsyn driver, and you use that 
script to save the configuration, such as when you modify the rate or 
pitch of the synthesized voice. What happens is that the contents of 
caps_start and caps_stop are written with enclosing quotation marks. You 
may never notice this until the next  time you load the configuration 
with speakupconf, which in my case happens on bootup.

The enclosing quotes are pronounced when a capital letter is identified. 
Distracting, but not disastrous. This does not happen with other 
drivers, at least not with those I have tested (ltlk, txprt).

I am using Speakup v-2.00 CVS: Mon May 1 09:46:33 EDT 2006

synth sftsyn version 0.3

Does anyone else see this?

Chuck




- -- 
The Moon is Waning Gibbous (54% of Full)
Get downloads from http://www.mhcable.com/~chuckh
  and remember, INFORMATION WANTS TO BE FREE!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFEu2CkXnuiIOyDVQURAgAPAJwMeu7plH9rdUM8Mf6b62gu96NlAwCeK4YD
b8pu9cY+EdBzTuTK+ZkJ20A=
=HayF
-----END PGP SIGNATURE-----




[Index of Archives]     [Linux for the Blind]     [Fedora Discussioin]     [Linux Kernel]     [Yosemite News]     [Big List of Linux Books]
  Powered by Linux