[BRLTTY] Emacspeak and Braille displays

2016-06-13 Thread Rich Morin
can access. Specifically, I would hope that BRLTTY can be used to display arbitrary content from a specified terminal session, Emacpeak buffer, etc. Is this the case? If not, would it be hard to set up? Comments and suggestions welome... (ducks) -r -- http://www.cfcl.com/rdm

Re: [BRLTTY] Emacspeak and Braille displays

2016-06-14 Thread Rich Morin
On Jun 14, 2016, at 03:37, Dave Mielke wrote: > [quoted lines by Rich Morin on 2016/06/13 at 20:08 -0700] >> If not, would it be hard to set up? > > That was achieved way back in the mid '90s. :-) Thanks for the clarifications! This sounds quite encouraging. >> Comme

Re: [BRLTTY] Emacspeak and Braille displays

2016-06-15 Thread Rich Morin
On Jun 15, 2016, at 02:51, Dave Mielke wrote: > [quoted lines by Rich Morin on 2016/06/14 at 10:31 -0700] > > The only one who may need to duck his head around here is myself whenever > stupid bugs slip through. :-) That being said, I myself don't believe in head > ducking

Re: [BRLTTY] Emacspeak and Braille displays

2016-06-15 Thread Rich Morin
On Jun 15, 2016, at 10:06, cov...@ccs.covici.com wrote: > Dave Mielke wrote: >> [quoted lines by Rich Morin on 2016/06/15 at 08:53 -0700] >>> I'm not sure how closely Apple's support for Braille displays is tied to >>> VoiceOver. >> >> It'

[BRLTTY] pacing line output to a Braille terminal?

2016-07-03 Thread Rich Morin
I'm working on a project where I'd like to feed a series of 40-character lines to a Braille terminal at a controlled, but variable rate. I'm hoping for an easy way to do this using BRLTTY, VoiceOver, or ??? -r -- http://www.cfcl.com/rdm Rich Morin r..

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

2016-07-03 Thread Rich Morin
socket I/O) that would be more language independent? -r -- http://www.cfcl.com/rdm Rich Morin r...@cfcl.com http://www.cfcl.com/rdm/resumeSan Bruno, CA, USA +1 650-873-7841 Software system design, development, and documentation _

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 >> >

[BRLTTY] documentation issues

2016-07-04 Thread Rich Morin
which is specific to a particular version of Linux. It would be nice to have tar.gz or zip versions available, as well. -- http://www.cfcl.com/rdm Rich Morin r...@cfcl.com http://www.cfcl.com/rdm/resumeSan Bruno, CA, USA +1 650-873-7841

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

2016-07-04 Thread Rich Morin
ial" answer. -r -- http://www.cfcl.com/rdm Rich Morin r...@cfcl.com http://www.cfcl.com/rdm/resumeSan Bruno, CA, USA +1 650-873-7841 Software system design, development, and documentation ___ This message was sent via the BRLTT

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 dat

Re: [BRLTTY] documentation issues

2016-07-05 Thread Rich Morin
nary builds. There's a build that uses the older LibUSB Win32 interface and there's a build that uses the newer LibUSB-1.0 WinUSB interface. = As a small nit, I'd also add a tag just above the first table (between the introductory text and the heading row). -r -- htt

Re: [BRLTTY] documentation issues

2016-07-05 Thread Rich Morin
high-quality PDF, but Samuel will know for sure. -r -- http://www.cfcl.com/rdm Rich Morin r...@cfcl.com http://www.cfcl.com/rdm/resumeSan Bruno, CA, USA +1 650-873-7841 Software system design, development, and documentation ___

Re: [BRLTTY] documentation issues

2016-07-06 Thread Rich Morin
On Jul 5, 2016, at 15:03, Dave Mielke wrote: > [quoted lines by Rich Morin on 2016/07/05 at 09:29 -0700] >> I would add a descriptive section on "Distribution Formats", near the top >> of the page (eg, just below the "Copyright and Disclaimer"). > > P

Re: [BRLTTY] documentation issues

2016-07-06 Thread Rich Morin
#x27;s tmux? Screen vs tmux https://www.wikivs.com/wiki/screen_vs_tmux https://en.wikipedia.org/wiki/Tmux http://dominik.honnef.co/posts/2010/10/why_you_should_try_tmux_instead_of_screen/ -r -- http://www.cfcl.com/rdm Rich Morin r...@cfcl.com http://www.cfcl.com/rdm/resume

Re: [BRLTTY] documentation issues

2016-07-06 Thread Rich Morin
On Jul 6, 2016, at 07:11, Dave Mielke wrote: > [quoted lines by Rich Morin on 2016/07/06 at 05:04 -0700] > >> TCL -> Tcl > > I know about this one, but I'm kind of stubborn about it. The C and the L, > after all, also stand for words in their own

Re: [BRLTTY] documentation issues

2016-07-06 Thread Rich Morin
On Jul 6, 2016, at 07:45, Dave Mielke wrote: > [quoted lines by Rich Morin on 2016/07/06 at 07:21 -0700] > >> Screen vs tmux >> https://www.wikivs.com/wiki/screen_vs_tmux > > I didn't know about tmux. I still don't understand your suggestion > on this poin

Re: [BRLTTY] documentation issues

2016-07-06 Thread Rich Morin
On Jul 6, 2016, at 16:51, Dave Mielke wrote: > [quoted lines by Rich Morin on 2016/07/06 at 05:04 -0700] > > Please check the Download page to see if the formatting has improved and/or > if > there are any new problems. There are a few validator errors to fix, still, > but

Re: [BRLTTY] documentation issues

2016-07-07 Thread Rich Morin
-r -- http://www.cfcl.com/rdm Rich Morin r...@cfcl.com http://www.cfcl.com/rdm/resumeSan Bruno, CA, USA +1 650-873-7841 ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@