public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Glenn Ervin at Home" <GlennErvin@cableone.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Braille Blazer problems
Date: Wed, 14 Jan 2004 21:22:53 -0600	[thread overview]
Message-ID: <008e01c3db16$dce71100$6d00a8c0@desktop> (raw)
In-Reply-To: <20040115024445.GB23885@romuald.net.eu.org>


I thought the Blazer was an embosser.
Glenn.

----- Original Message ----- 
From: "Gregory Nowak" <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Wednesday, January 14, 2004 8:44 PM
Subject: Re: Braille Blazer problems


I've seen the problem of the blazer resetting itself when too much
text is sent to it with speakup 1.00, and with 1.5. Speakup is the
only screen reader I've seen this problem with, both provox and
window-eyes work fine.

As for the pitch not changing in the bns driver for lower and upper
case, I've found that I need to make a change in one of the speakup
files (I.E. /proc/speakup/volume, /proc/speakup/punct ETC.), and then
the voice lowers for upper case, and comes back to normal for lower
case, which is the opposite of how it's normally done, but there is
case change indication at least.

Greg


On Wed, Jan 14, 2004 at 08:36:56PM -0500, Garrett Klein wrote:
> Hello all,
> I am running Slackware 9.1 with Speakup 1.5 using my Braille Blazer as a 
> synthesizer. I, however, am having multiple issues with it. For one 
> thing, when too much text gets sent over the serial port, it turns 
> itself off and back on, which destroys my punctuation/pitch settings (I 
> can fix the pitch and speed, though). My second problem is 
> Speakup-related. I've seen it in Speakup 1.0, 1.5, and CVS speakup 
> (which, might I add, made my blazer sound quite weird). This problem is 
> that it does not announce uppercase letters in a higher pitch than 
> lowercase ones. This has also happened when using my Braille Lite 40 as 
> a synth. I've tried a warm reset, and that didn't help. Sometimes it'll 
> say some letters higher when spelling a word, but I think it doesn't 
> just do the uppercase ones in that case, it's hard to tell. Case 
> sensativity works in JAWS for DOS, BTW.
> I'm looking into getting a DoubleTalk LT, so I won't have to worry about 
> these problems anymore. Either that, or possibly getting a TrippleTalk 
> USB and using its serial port, would that work with speakup? Any 
> suggestions to fix these annoying issues would be appreciated.
> Thanks in advance,
> Garrett
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 
Free domains: http://www.eu.org/ or mail dns-manager@EU.org


_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup



  reply	other threads:[~ UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Garrett Klein
 ` Alex Snow
   ` Garrett Klein
     ` Alex Snow
       ` Sina Bahram
         ` Luke Davis
           ` Geoff Shang
           ` Alex Snow
             ` Alex Snow
         ` Alex Snow
           ` Sina Bahram
         ` Kelly Prescott
           ` Steve Holmes
           ` Sina Bahram
 ` Gregory Nowak
   ` Glenn Ervin at Home [this message]
     ` Luke Davis
     ` Alex Snow
   ` Kirk Reiser
     ` Gregory Nowak
     ` Garrett Klein

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='008e01c3db16$dce71100$6d00a8c0@desktop' \
    --to=glennervin@cableone.net \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).