From: David Csercsics <david@really.isa-geek.net>
To: "Speakup is a screen review system for Linux."
<speakup@braille.uwo.ca>, Alex Snow <alex_snow@gmx.net>
Subject: Re: bug in the transport driver?
Date: Wed, 05 May 2004 16:23:22 -0700 [thread overview]
Message-ID: <0HX900C5FKOGF2@l-daemon> (raw)
In-Reply-To: <20040505225804.GA8928@gmx.net>
>Hi all. I noticed that when using speakup with an artic transport some
>words are left out when the screeen is read. for example when I'm
>compiling something and speakup is reading the gcc commandline i here
>gcc --- - - or something like that. some options are read but others
>aren't.
>I've seen this with both speakup 1.5 and recent versions of speakup cvs.
>anyone had this problem?
Yep if you want to hear the options just set punctuation to a
higher level. I have had this problem when punctuation is set to
some or none. Anotehr problem I have is that colons and dashes will
get spoken even when punc_level is set to 0. I would assume your
transport has the same issue. If you don't have this issue tehn I
guess it's specific to my synth.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Alex Snow
` David Csercsics [this message]
` Alex Snow
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=0HX900C5FKOGF2@l-daemon \
--to=david@really.isa-geek.net \
--cc=alex_snow@gmx.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).