Character pronounciation

Character pronounciation

[Zachary Kline]

Hi All,
This is just my two cents on the issue.
I tend to agree that either Speakup or the synthesizer should be responsible
for pronounciation.  If the synthesizer has pretty good default support
I say that the "direct" option in speakup is a good thing. 
That being said, I'm curious what character set the default Speakup
arrangement is pulled from?  (It doesn't seem to be Latin 1.)
Best,
Zack.

Re: Character pronounciation

[Hart Larry]

Well Zack-and-All, I am following this discussion with interest.
I suppose which ever option would give me more control
of my Dec-Talk listening experience.
Seems like when I was in DOS with Vocal-Eyes,
I had complete controll, I could not
only create character-and-key-label
dictionaries, as well as manually
edit Dec-Talk files to get
rid of needless abreviations. Also in almost every windows screen-reader, as 
well as
Jupiter in Linux, there are pronunciation
dictionaries
Now I feel I have quite little access to
customizing my experience, even though Linux
is more powerful.
An example, yesterday some1 posted the path where
the characters file could fix the letter zee.
So I go there-and-with sudo in nano
I edit that file, make all my changes.
Once I exit, the file is automaticly set back
to defaults.  Maybe I should do
a chmod 755 on that directory.
Anyway, for months since we upgraded from
fc6-fc9 most of the time my altered
characters file is not active.
And I still have issues, probably involving caps start-and-stop,
which knock down pitch-and-rate.
Thanks for listening
Hart

Re: Character pronounciation

[Gregory Nowak]

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

On Mon, Mar 02, 2009 at 01:52:29PM -0800, Hart Larry wrote:
> An example, yesterday some1 posted the path where
> the characters file could fix the letter zee.
> So I go there-and-with sudo in nano
> I edit that file, make all my changes.
> Once I exit, the file is automaticly set back
> to defaults.  Maybe I should do
> a chmod 755 on that directory.

This sounds to me more like user error, rather than inadequate
functionality on the part of speakup or gnu/linux. I'll try to help by
addressing your concerns above one by one. First, you don't want to
open the characters file in a editor like nano. What you want to do is
to make a copy of it, perhaps in your home directory, with cp. Once
you've made a copy of it, open that copy in nano, and do with it what
you need to do. Then, you need to cat your copy to speakup's
characters file with a command similar to this:
cat $HOME/characters >/sys/module/speakup/parameters/characters

Note that speakup's characters file will be back to the defaults when
you reboot, and maybe if you switch synths, (I'm not sure on
that). So, you need to put the above command into a script that runs
at boot. As for your comment about doing chmod 755 on that directory,
/sys/module/speakup/parameters is already at 755 on all of my systems,
and I suspect that this is the norm, and not an exception. If you were
to change permissions on that directory, I also suspect that this
change would also not stick across reboots, unless it was in a script,
but I could be wrong here too. Hth.

Greg


- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkmsWSIACgkQ7s9z/XlyUyDtUwCgx9Uqjmz4t+P6EplHH12gf6Un
9bkAoIfg8Hx0ln2yQCOpd6z8CASDsWna
=l5Br
-----END PGP SIGNATURE-----