Re: [BRLTTY] 5.4 has been released.

2016-07-04 Thread Mario Lang
Samuel Thibault writes: > Dave Mielke, on Sun 03 Jul 2016 22:16:58 -0400, wrote: >> [quoted lines by Samuel Thibault on 2016/07/03 at 20:51 +0200] >> >I see that the md driver was added to the 0403/6001 USB ID autodetection >> >udev rule. Is it really safe to add it? (we used to have issues with

[BRLTTY] got brltty working, now some questions

2016-07-04 Thread Devin Prater
Hi all. I got BRLTTY working. I used sudo systemctl enable brltty, then sudo systemctl start brltty. Now I have a few questions. Is it possible to have braille input be contracted, as well as output? I’d wanna type in contracted braille, at least for documents and email. Next, sometimes, especia

Re: [BRLTTY] got brltty working, now some questions

2016-07-04 Thread Dave Mielke
[quoted lines by Devin Prater on 2016/07/04 at 03:33 -0500] >Is it possible to have braille input be contracted, as well as output? I’d >wanna type in contracted braille, at least for documents and email. No, typing in contracted braille isn't supported. >sometimes, especially when quitting pr

Re: [BRLTTY] 5.4 has been released.

2016-07-04 Thread Dave Mielke
[quoted lines by Samuel Thibault on 2016/07/04 at 07:26 +0200] >> >I see that the md driver was added to the 0403/6001 USB ID autodetection >> >udev rule. Is it really safe to add it? (we used to have issues with at, >> >ce, and mm, which we disabled in the Debian packaging) >> >> As long as only

Re: [BRLTTY] pacing line output to a Braille terminal?

2016-07-04 Thread Rich Morin
On Jul 3, 2016, at 22:43, Shérab wrote: > Rich Morin (2016/07/03 16:18 -0700): >> On Jul 3, 2016, at 15:40, Samuel Thibault >> wrote: >>> I guess what you want to use is BrlAPI. >>> http://mielke.cc/brltty/doc/Manual-BrlAPI/English/BrlAPI.html >> >> Thanks; that's certainly one possibility. Ho

Re: [BRLTTY] pacing line output to a Braille terminal?

2016-07-04 Thread Jason White
Rich Morin wrote: > On a related question, I haven't had any luck in finding out how fast > these sorts of devices can respond to new data (eg, accept the data, > raise and lower the appropriate pins). Can anyone give me an estimate > or (better) point me to any documentation? Since they gene

[BRLTTY] documentation issues

2016-07-04 Thread Rich Morin
While perusing the BRLTTY and BrlAPI web pages, I ran into several issues (see below). No guarantees, but let me know if some editing assistance would be welcomed. -r # The BrlAPI Programmers' Reference The "Documentation" page (http://mielke.cc/brltty/documentation.html) contains a link (The

Re: [BRLTTY] pacing line output to a Braille terminal?

2016-07-04 Thread Rich Morin
On Jul 4, 2016, at 11:02, Jason White wrote: > Since they generally use similar piezoelectric actuators, I would > expect response times to be similar. As I understand it, all of the actuators are made by a single firm. > I don't recall those details ever appearing in manufacturers' > specificat

Re: [BRLTTY] pacing line output to a Braille terminal?

2016-07-04 Thread Jason White
Rich Morin wrote: > As I understand it, all of the actuators are made by a single firm. There are several firms. KGS in Japan make braille display cell technology. VFO Group in the US do likewise (they formed as a merger of Freedom Scientific and Optelec, and recently acquired AI Squared, but t

Re: [BRLTTY] Error "Can't determine tty number"

2016-07-04 Thread Samuel Thibault
t w, on Mon 04 Jul 2016 05:13:21 +, wrote: > HOWEVER, nothing is actually written on the Braille display, and it also does > not recognize any input. Do you have xbrlapi running? (I'm not asking for you to run it, I'm wondering whether it is already running) Is the konsole window active when

Re: [BRLTTY] documentation issues

2016-07-04 Thread Samuel Thibault
Hello, Rich Morin, on Mon 04 Jul 2016 11:07:12 -0700, wrote: > The "Documentation" page (http://mielke.cc/brltty/documentation.html) > contains a link (The BrlAPI Programmers' Reference) to: > > BrlAPI 1.0 > http://mielke.cc/brltty/doc/BrlAPIref/index.html > > The page in question appears t

Re: [BRLTTY] 5.4 has been released.

2016-07-04 Thread Samuel Thibault
Dave Mielke, on Mon 04 Jul 2016 09:27:38 -0400, wrote: > [quoted lines by Samuel Thibault on 2016/07/04 at 07:26 +0200] > > >> >I see that the md driver was added to the 0403/6001 USB ID autodetection > >> >udev rule. Is it really safe to add it? (we used to have issues with at, > >> >ce, and mm,

Re: [BRLTTY] documentation issues

2016-07-04 Thread Dave Mielke
[quoted lines by Rich Morin on 2016/07/04 at 11:07 -0700] ># The BrlAPI Programmers' Reference > >The "Documentation" page (http://mielke.cc/brltty/documentation.html) >contains a link (The BrlAPI Programmers' Reference) to: > > BrlAPI 1.0 > http://mielke.cc/brltty/doc/BrlAPIref/index.html > >T

Re: [BRLTTY] documentation issues

2016-07-04 Thread Rich Morin
On Jul 4, 2016, at 14:10, Dave Mielke wrote: > [quoted lines by Rich Morin on 2016/07/04 at 11:07 -0700] >> BrlAPI 1.0 >> http://mielke.cc/brltty/doc/BrlAPIref/index.html >> >> The page in question appears to be rather dated, > > In what way does it look dated? When I went to research this, I

Re: [BRLTTY] documentation issues

2016-07-04 Thread Samuel Thibault
Rich Morin, on Mon 04 Jul 2016 14:53:28 -0700, wrote: > However, I still wonder what > BrlAPI changes may need to added to the 2006 document. Most probably none :) Samuel ___ This message was sent via the BRLTTY mailing list. To post a message, send an

Re: [BRLTTY] Error "Can't determine tty number"

2016-07-04 Thread t w
Hi Samuel,> Do you have xbrlapi running? (I'm not asking for you to run it, I'm > wondering whether it is already running) No, xbrlapi is not running. I also tried running it in a different tab (and checked that it is running), then ran my program, but it doesn't seem to make any difference. > I