From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.174]) by speech.braille.uwo.ca (Postfix) with ESMTP id 7BC3E10A4B for ; Mon, 2 Mar 2009 08:30:58 -0500 (EST) Received: by wf-out-1314.google.com with SMTP id 26so2487889wfd.23 for ; Mon, 02 Mar 2009 05:30:57 -0800 (PST) Received: by 10.142.84.5 with SMTP id h5mr3012528wfb.200.1236000657675; Mon, 02 Mar 2009 05:30:57 -0800 (PST) Received: from lnx3.holmesgrown.com (ip72-208-219-132.ph.ph.cox.net [72.208.219.132]) by mx.google.com with ESMTPS id 30sm9027274wfc.24.2009.03.02.05.30.56 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 02 Mar 2009 05:30:57 -0800 (PST) Date: Mon, 2 Mar 2009 06:30:54 -0700 From: Steve Holmes To: speakup@braille.uwo.ca Subject: Re: Re: espeak and the letter z Message-ID: <20090302133054.GA4366@lnx3.holmesgrown.com> Mail-Followup-To: speakup@braille.uwo.ca References: <20090227005213.GA7046@cq.ftml.net> <20090126233619.cmbrannon@cox.net> <5034230206jsd@clara.co.uk> <20090301213923.GA23555@linux1> <49ABBE37.1050701@aim.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline In-Reply-To: <49ABBE37.1050701@aim.com> User-Agent: Mutt/1.5.18 (2008-05-17) X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.11 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: Mon, 02 Mar 2009 13:30:58 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Yes, the influince of different speech synths, libraries and support layers is confusing enough. My opinion is any speech charactistics including pronunciation should be controled by the screen reader application or speakup in this case and *maybe* by the synth itself but never by the stuff in the middle. And while I'm on this subject, I can't resist the opportunity to complain once more that synthesizers should *NEVER* plug in substitutions for abreviations! On Mon, Mar 02, 2009 at 11:08:39AM +0000, Michael Whapples wrote: > On this topic, I know that speechd-up modifies some of speakup's > settings when it starts (I think characters was an example). I am > slightly split in my mind whether this really should be done > (particularly as default), but I can see the arguments for it and this z > issue highlights it so may be espeakup could do some of this setting > stuff (I would opt that it should only alter stuff if certain options > are given, so leaving the default as no modification of speakup's > settings). > > Any other views? > > Also as a separate question, but linked, by setting > /sys/modules/speakup/parameters/direct will settings like punctuation > level stop working (IE. do you mean it doesn't process the character > table or do you mean speakup does absolutely no processing of text)? > > Michael Whapples > On 23/12/42 19:59, William Hubbs wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On Fri, Feb 27, 2009 at 10:55:31AM +0000, Jonathan Duddington wrote: >> >>> On 27 Feb, Chris Brannon wrote: >>> >>>> When you type z or read z with the speakup cursor, speakup sends the >>>> text zehd to espeakup. >>>> >>> Why not just send "z" ? >>> >> >> Actually this can be done if you are running the latest speakup, it is >> just not set as the default. >> >> There is a sys file for speakup called >> /sys/module/speakup/parameters/direct. If you set the value in there >> to 1, text will be sent directly to espeak with no speakup processing. >> >> William >> >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v2.0.9 (GNU/Linux) >> >> iEYEARECAAYFAkmrAIsACgkQblQW9DDEZThbeACbB0Z+hEIJJ7sDJIPvRZA1tHS0 >> MwMAnRtPIwA8IuuzRnC+cYHHLmmIeDol >> =sxyi >> -----END PGP SIGNATURE----- >> >> > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEAREDAAYFAkmr344ACgkQWSjv55S0LfFVMwCgtZLyjsn+UmeSmJGbTx/6XPQv XvoAoPqSfU+Nxa2WJY/FBrQew6ZA1KXC =boFC -----END PGP SIGNATURE-----