[quoted lines by John J. Boyer on 2016/05/31 at 10:29 -0500] >On Linux BRLTTY has its own drivers for all supported displays. Isn't this >true on Windows also?
Yes, it's true on Windows as well. >Why doesn't NVDA just include BRLTTY automatically? It apparently expects one >to go into its menus to make Braille choices. I'm not sure that any of us can answer this question as it's ultimately an NVDA issue. What I do know is that NVDA has some of its own drivers, and also offers the ability to use brltty instead. Here's my guess. Please remember that that's all it is. This isn't an authoritative opinion of any kind or in any way. NVDA probably started out as a free alternative to the various expensive Windows screen readers. Using brltty probably didn't even occur to them at the outset. It could even be that brltty didn't run on Windows and/or that BrlAPI hadn't been developped way back whenever NVDA was started. If this is the case then it would've made sense to use manufacturer-supplied braille drivers since the purchase of a braille device entitled its owner to use its Windows drivers. >SinceI am deaf-blind, I can't use speech. Perhaps you could ask the NVDA people to implement a way to start NVDA with a command line option that'd let you specify which braille driver (in your case, brltty) to use. Perhaps it could have even more command line options, i.e. one for each setting that you might want/need to specify without having to go into its settings screens. -- Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God. Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/ EMail: d...@mielke.cc | Canada K2A 1H7 | http://FamilyRadio.org/ _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
