[nvda] Blank lines was Re: Re: BRLTTY and NVDA
- From: erik burggraaf <erik@xxxxxxxxxxxxxxxxxx>
- To: nvda@xxxxxxxxxxxxx
- Date: Thu, 30 Oct 2008 15:06:55 -0700
Hi, regarding blank lines in braille, this is a point of preference.
I use braille mainly for reading things back and I'm happy with a
double space to indicate a blank line. Having a blank line of braille
where a blank line ott to go breaks up the flow of reading for me
being a very sluggish braille user to begin with.
In most of the software I use, ie mobile speak, there's an ignore
blank lines option which I usually turn on post-haste. I think evry
braille system should have the option, as people who use braille for a
lot of editting might want an actual blank line where a blank line
should go.
Best,
erik burggraaf
Certified Technician
Assistive Computing LTD Support and training
Sales department: 888-828-2445
Support and Training: 888-255-5194
Email: erik@xxxxxxxxxxxxxxxxxx
Website coming soon
On 29-Oct-08, at 5:54 AM, Valiant8086 wrote:
Hi.
Ok it looks like we're getting places now. I was unable to get
brltty to recognise anything through the USB port by just letting it
do auto detect on USB. When I started brltty manually with the -l
debug -n -e switches, I went into a loop trying again and again to
find a display but failing to load every driver. I then uncommented
the lines for bm and for useing serial port, and changec 4 com1 to
com2, and started brltty manually again with those switches. I got a
bleep like noise, and a printout of the settings, and on the display
it said something like no terminal to display or so. So, first round
of success. I was eventually able to get it to show me what I was
typing into command prompt. I then was able to start the service
after I killed it from command prompt. then I told NVDA to use
brltty, and it works! I have been moving around with it with the
NVDA speech turned off. It's doing what I want ok. I discovered that
old virtual buffers don't display with braille, but not entirely
unexpected, think I remember a track ticket about that. I kind of
like how it reads the message list in outlook express, it always
starts with the sender's display name on the far left of the
display. You don't have to hunt around to figure out where it starts
at. On the desktop, on the other hand, it lines up on the right
side, and causes me to have to read backwards sometimes before I can
find the beginning of the desktop item I've selected, very
difficult, in another words, ti just arrow around and look for
something that hast the first letter that i'm looking for. Can you
fo anything about this? I've been trying to get fs to do this for
jaws and am being ignored. I believe we should always make sure
braille extends off the right end of the braille display, not the
left end, at least for english. We'll also need to come up with
shortcuts for saying list item button etc but I believe there's a
track ticket on that also. I'd like to have that configurable,
actually it would probably have to, for the benefit of other
languages.
But yeah, so far, I like what I see, it was no harder, and yes this
is true, to get braille to run on NVDA than it was jaws. I haven't
yet tried the PACMate display but it will probably work streight and
easy just like that.
We need a shortcut, if we haven't already got one, for braille
settings. NVDA+ctrl+l would probably be the shortcut to use.
When a line of text is long and wraps around, the braille display
doesn't appear to display the same text on the continueation of the
line that you receive when you down arrow as speech does.
When you open a message and are on a blank line that has a line
below it that has text on it, the text shows with a space in front
of it on the line below it, even if you've arrowed to the blank line
that's above it. Should the braille display show nothing in this
case? In fact while composing this message it's really hard to
tell when i'm on a blank line.
I believe there's a track ticket for it already, that we'll need to
try and implimint some of the typical shortcuts that can be issued
from the keys on the braille displays. I can advanced and reverse
advance, and use my router buttons, but that's about it.
----- Original Message ----- From: "James Teh" <jamie@xxxxxxxxxxx>
To: <nvda@xxxxxxxxxxxxx>
Sent: Tuesday, October 28, 2008 9:45 PM
Subject: [nvda] Re: BRLTTY and NVDA
On 28/10/2008 10:14 PM, Valiant8086 wrote:
Ok I connected the brailliant 32 and did net stop brlapi. I got a
confirmation that was telling me it was stopped. Net start brlapi
after
that, and it did say it was started. No braille though.
This is odd. I use a Brailliant 40 here with no problems. I
actually don't use it with libusb-win32, but rather, I have it set
to use the serial port that the Brailliant drivers emulate due to a
few problems I was having with libusb-win32. It does work with
libusb-win32 for me, but there are some problems when I disconnect
my display.
You can get more information from brltty by stopping the brltty
service and then running brltty directly like this:
brltty -l debug -n -e
(brltty.exe is in the bin subdir of the BRLTTY installation dir.)
If you wanted to try using the emulated serial port instead of
libusb-win32, modify etc\brltty.conf in your BRLTTY installation
directory and add these two lines to the top:
braille-driver bm
braille-device serial:com4
where com4 is the emulated port for your Brailliant, which you can
find under Ports (com and lpt) in Device Manager.
Jamie
--
James Teh
Email/MSN Messenger/Jabber: jamie@xxxxxxxxxxx
Web site: http://www.jantrid.net/
To post messages to the list send email to
nvda@xxxxxxxxxxxxx
To modify your NVDA Email settings go to:
http://www.freelists.org/list/nvda
Thank you for your continued support of Nonvisual Desktop Access,
an open source free screen reader for Microsoft Windows:
http://www.nvda-project.org/
To get the latest NVDA snapshot:
http://www.nvda-project.org/snapshots/
Report bugs or make feature requests at:
http://trac.nvda-project.org/
Message Archive:
http://www.freelists.org/archives/nvda
---
avast! Antivirus: Inbound message clean.
Virus Database (VPS): 081028-1, 10/28/2008
Tested on: 10/28/2008 9:48:13 PM
avast! - copyright (c) 1988-2008 ALWIL Software.
http://www.avast.com
To post messages to the list send email to
nvda@xxxxxxxxxxxxx
To modify your NVDA Email settings go to:
http://www.freelists.org/list/nvda
Thank you for your continued support of Nonvisual Desktop Access, an
open source free screen reader for Microsoft Windows:
http://www.nvda-project.org/
To get the latest NVDA snapshot:
http://www.nvda-project.org/snapshots/
Report bugs or make feature requests at:
http://trac.nvda-project.org/
Message Archive:
http://www.freelists.org/archives/nvda
To post messages to the list send email to
nvda@xxxxxxxxxxxxx
To modify your NVDA Email settings go to:
http://www.freelists.org/list/nvda
Thank you for your continued support of Nonvisual Desktop Access, an open
source free screen reader for Microsoft Windows:
http://www.nvda-project.org/
To get the latest NVDA snapshot:
http://www.nvda-project.org/snapshots/
Report bugs or make feature requests at:
http://trac.nvda-project.org/
Message Archive:
http://www.freelists.org/archives/nvda
- Follow-Ups:
- [nvda] Re: Blank lines was Re: Re: BRLTTY and NVDA
- From: James Teh
- References:
- [nvda] BRLTTY and NVDA
- From: James Teh
- [nvda] Re: BRLTTY and NVDA
- From: Valiant8086
- [nvda] Re: BRLTTY and NVDA
- From: James Teh
- [nvda] Re: BRLTTY and NVDA
- From: Valiant8086
- [nvda] Re: BRLTTY and NVDA
- From: Valiant8086
- [nvda] Re: BRLTTY and NVDA
- From: James Teh
- [nvda] Re: BRLTTY and NVDA
- From: Valiant8086
Other related posts:
- » [nvda] Blank lines was Re: Re: BRLTTY and NVDA
- » [nvda] Re: Blank lines was Re: Re: BRLTTY and NVDA
- » [nvda] Re: Blank lines was Re: Re: BRLTTY and NVDA
Hi.Ok it looks like we're getting places now. I was unable to get brltty to recognise anything through the USB port by just letting it do auto detect on USB. When I started brltty manually with the -l debug -n -e switches, I went into a loop trying again and again to find a display but failing to load every driver. I then uncommented the lines for bm and for useing serial port, and changec 4 com1 to com2, and started brltty manually again with those switches. I got a bleep like noise, and a printout of the settings, and on the display it said something like no terminal to display or so. So, first round of success. I was eventually able to get it to show me what I was typing into command prompt. I then was able to start the service after I killed it from command prompt. then I told NVDA to use brltty, and it works! I have been moving around with it with the NVDA speech turned off. It's doing what I want ok. I discovered that old virtual buffers don't display with braille, but not entirely unexpected, think I remember a track ticket about that. I kind of like how it reads the message list in outlook express, it always starts with the sender's display name on the far left of the display. You don't have to hunt around to figure out where it starts at. On the desktop, on the other hand, it lines up on the right side, and causes me to have to read backwards sometimes before I can find the beginning of the desktop item I've selected, very difficult, in another words, ti just arrow around and look for something that hast the first letter that i'm looking for. Can you fo anything about this? I've been trying to get fs to do this for jaws and am being ignored. I believe we should always make sure braille extends off the right end of the braille display, not the left end, at least for english. We'll also need to come up with shortcuts for saying list item button etc but I believe there's a track ticket on that also. I'd like to have that configurable, actually it would probably have to, for the benefit of other languages.
But yeah, so far, I like what I see, it was no harder, and yes this is true, to get braille to run on NVDA than it was jaws. I haven't yet tried the PACMate display but it will probably work streight and easy just like that. We need a shortcut, if we haven't already got one, for braille settings. NVDA+ctrl+l would probably be the shortcut to use.
When a line of text is long and wraps around, the braille display doesn't appear to display the same text on the continueation of the line that you receive when you down arrow as speech does.
When you open a message and are on a blank line that has a line below it that has text on it, the text shows with a space in front of it on the line below it, even if you've arrowed to the blank line that's above it. Should the braille display show nothing in this case? In fact while composing this message it's really hard to tell when i'm on a blank line.
I believe there's a track ticket for it already, that we'll need to try and implimint some of the typical shortcuts that can be issued from the keys on the braille displays. I can advanced and reverse advance, and use my router buttons, but that's about it.
----- Original Message ----- From: "James Teh" <jamie@xxxxxxxxxxx> To: <nvda@xxxxxxxxxxxxx> Sent: Tuesday, October 28, 2008 9:45 PM Subject: [nvda] Re: BRLTTY and NVDA
On 28/10/2008 10:14 PM, Valiant8086 wrote:This is odd. I use a Brailliant 40 here with no problems. I actually don't use it with libusb-win32, but rather, I have it set to use the serial port that the Brailliant drivers emulate due to a few problems I was having with libusb-win32. It does work with libusb-win32 for me, but there are some problems when I disconnect my display.Ok I connected the brailliant 32 and did net stop brlapi. I got aconfirmation that was telling me it was stopped. Net start brlapi afterthat, and it did say it was started. No braille though.You can get more information from brltty by stopping the brltty service and then running brltty directly like this:brltty -l debug -n -e (brltty.exe is in the bin subdir of the BRLTTY installation dir.)If you wanted to try using the emulated serial port instead of libusb-win32, modify etc\brltty.conf in your BRLTTY installation directory and add these two lines to the top:braille-driver bm braille-device serial:com4where com4 is the emulated port for your Brailliant, which you can find under Ports (com and lpt) in Device Manager.Jamie -- James Teh Email/MSN Messenger/Jabber: jamie@xxxxxxxxxxx Web site: http://www.jantrid.net/ To post messages to the list send email to nvda@xxxxxxxxxxxxx To modify your NVDA Email settings go to: http://www.freelists.org/list/nvdaThank you for your continued support of Nonvisual Desktop Access, an open source free screen reader for Microsoft Windows:http://www.nvda-project.org/ To get the latest NVDA snapshot: http://www.nvda-project.org/snapshots/ Report bugs or make feature requests at: http://trac.nvda-project.org/ Message Archive: http://www.freelists.org/archives/nvda --- avast! Antivirus: Inbound message clean. Virus Database (VPS): 081028-1, 10/28/2008 Tested on: 10/28/2008 9:48:13 PM avast! - copyright (c) 1988-2008 ALWIL Software. http://www.avast.com
To post messages to the list send email to nvda@xxxxxxxxxxxxx To modify your NVDA Email settings go to: http://www.freelists.org/list/nvdaThank you for your continued support of Nonvisual Desktop Access, an open source free screen reader for Microsoft Windows:
http://www.nvda-project.org/ To get the latest NVDA snapshot: http://www.nvda-project.org/snapshots/ Report bugs or make feature requests at: http://trac.nvda-project.org/ Message Archive: http://www.freelists.org/archives/nvda
- [nvda] Re: Blank lines was Re: Re: BRLTTY and NVDA
- From: James Teh
- [nvda] BRLTTY and NVDA
- From: James Teh
- [nvda] Re: BRLTTY and NVDA
- From: Valiant8086
- [nvda] Re: BRLTTY and NVDA
- From: James Teh
- [nvda] Re: BRLTTY and NVDA
- From: Valiant8086
- [nvda] Re: BRLTTY and NVDA
- From: Valiant8086
- [nvda] Re: BRLTTY and NVDA
- From: James Teh
- [nvda] Re: BRLTTY and NVDA
- From: Valiant8086