From: Gregory Nowak <greg@romuald.net.eu.org>
To: speakup@braille.uwo.ca
Subject: reading the full screen
Date: Wed, 24 Oct 2007 14:40:49 -0700 [thread overview]
Message-ID: <20071024214049.GA2856@localhost.localdomain> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all.
I have another straight-forward, though probably loaded question. When
one uses numpad-plus to read the screen, is there a way to control the
size of text chunks speakup sends to the synth, either through
something in /proc/speakup, or in some other way without modifying the
code? The reason I'm asking is because the serial port support in
virtualbox 1.5.2 is still messed up. If reading line by line with
numpad-7 and numpad-9 for example, the bns speaks the text fine in
a virtualbox vm. However, if I attempt reading the full screen, large
chunks of text are skipped, making that feature practically
useless. It's as if there was some sort of handshaking or buffering
issue. It can't be handshaking though, since the same settings worked
just fine for me on physical machines, and even in virtualpc.
On the other hand, if I boot a dos floppy with provox inside
virtualbox, and read the full screen with provox+s, it reads just
fine, though I assume that's because provox sends the data in smaller
chunks, rather than just sending the full screen all at once. If
however there is a program that just sends data to the screen, for
example format.com when formatting a hard drive, I see the same chunk
skipping behavior under provox as well.
Yes, I will be eventually reporting this to innotek, once I've figured
out a way to reproduce the problem without requiring one to have a hardware synth. I
was however hoping for a way to get around the problem in speakup
temporarily, until virtualbox itself gets fixed. Thanks in advance for
any suggestions.
Greg
- --
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@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHH7vh7s9z/XlyUyARAu/wAJ9B0NP57KRVVzSD8GXOnrH6nzp6FwCfeEJ+
5gW2B7NKtQgnmochYNVMEAo=
=1kPk
-----END PGP SIGNATURE-----
next reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
Gregory Nowak [this message]
` Gaijin
` Gregory Nowak
` Kirk Reiser
` Gregory Nowak
` Frank Carmickle
` Gregory Nowak
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=20071024214049.GA2856@localhost.localdomain \
--to=greg@romuald.net.eu.org \
--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).