rfc: speakup's character and punctuation processing

[Gregory Nowak]

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

I'd say to just let the synthesizer deal with pronunciation, though
the best of both worlds would be to allow the user to switch among
both options, perhaps by loading a pronunciation dictionary to
somewhere under /sys/accessibility/speakup, as is done with chartab
and friends now.

Greg


On Sun, Apr 25, 2010 at 04:23:19PM -0500, William Hubbs wrote:
> All,
> 
> speakup does a number of things to have all of the characters and
> punctuation marks pronounced the same way for all of the synthesizers it
> supports instead of allowing the synthesizers to process them.
> 
> The disadvantage of this is primarily obvious for internationalization.
> We are forcing English pronunciations instead of allowing the
> synthesizer to pronounce things in the correct language.
> 
> For the softsynth, there is a direct option, which  passes things
> straight to the synthesizer.  I am wondering though if we should  just
> get rid of all of the character and punctuation processing that is part
> of speakup and allow the synthesizer to handle this?
> 
> This is just an idea right now.  I am not planning on doing this without
> discussion; I am wondering at this point what others think.
> 
> So, your input is welcome.
> 
> Thanks,
> 
> William
> 
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

- -- 
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 at EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkvUtKEACgkQ7s9z/XlyUyArqQCfY3WnKts0e6wP69aOqQYRgFiE
J1sAoMN6J74knvk8i1Mh7pdwSo0mUZ8A
=430V
-----END PGP SIGNATURE-----