From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from tds-solutions.net (tds-solutions.net [66.220.1.115]) by speech.braille.uwo.ca (Postfix) with ESMTP id 864BFC1A3B3 for ; Sun, 25 Apr 2010 17:26:09 -0400 (EDT) Received: from [192.168.0.20] (unknown [168.103.85.95]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tds-solutions.net (Postfix) with ESMTPSA id 93B501611B for ; Sun, 25 Apr 2010 15:25:38 -0600 (MDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1077) Subject: Re: rfc: speakup's character and punctuation processing From: Tyler Littlefield In-Reply-To: <20100425212319.GA6910@linux1> Date: Sun, 25 Apr 2010 15:25:34 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20100425212319.GA6910@linux1> To: "Speakup is a screen review system for Linux." X-Mailer: Apple Mail (2.1077) X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.13 Precedence: list Reply-To: "Speakup is a screen review system for Linux." List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Apr 2010 21:26:09 -0000 Why not an option that would allow for speakup to handle punctuation or = to bypass the speakup punctuation and pass it off to the synth for = processing? Thanks, Tyler Littlefield http://tds-solutions.net Twitter: sorressean On Apr 25, 2010, at 3:23 PM, William Hubbs wrote: > All, >=20 > 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. >=20 > 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. >=20 > 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? >=20 > 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. >=20 > So, your input is welcome. >=20 > Thanks, >=20 > William >=20 > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup