I like the idea of supporting or standing behind a standard set of screen reading keyboard commands. I will commend the developers of System Access, because in their day, they did use several screen reading specific keyboard commands that were pretty much the same as JFW. And at least GW Micro allowed us to remap Window-Eyes keyboard commands so for those of us who worked with multiple screen reading text to speech programmes had somewhat less of a challenge to continuously trying to keep the different commands in our heads. NV Access is kind of close, but they could be closer. Personally I don't care which screen reading programme one selects as the standard, I just would like the industry to pick a lane and commit. Vic Pereira Project Manager, Network, Security and Digital Services (NSDS) Shared Services Canada, Government of Canada vic.pereira@ssc-spc.gc.ca / Tel: 204-781-5046 Gestionnaire de Projet, Réseaux, sécurité et services numériques (RSSN) Services partagés Canada, Gouvernement du Canada vic.pereira@ssc-spc.gc.ca / Tél. : 204-781-5046 -----Original Message----- From: John G Heim <jheim@math.wisc.edu> Sent: August-07-19 8:40 AM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org>; Ibraam Wahib <ibraam.wahib@gmail.com> Subject: [Blind-sysadmins] Re: Terminal improvements are coming to NVDA 2019.3! You can't build one screen reader for two different operating systems. The best you could do is write two different screen readers, have them operate much the same way, and call them both the same thing. I have been arguing for years in favor of trying to standardize shortcut keys in screen readers as much as possible. You would not believe how controversial even that is. It's ridiculous. Bunch of religious fanatics. Right now, I am a little irritated with Microsoft. Alt+Super+s has long since been established in Linux as the way to start the screen reader. So they come along and make it Control+Windows+Enter. Of course, it was already something different, Command+F5, In MacOS. I think there should be one standard key combination to start/stop the screen reader. There should be another standardized key combination to get into screen reader help. That's the bare minimum. On 8/7/19 5:24 AM, Ibraam Wahib wrote:
is any hope to develop linux version of nvda for gui and cli in one program? thanks
----- Original Message ----- From: <vic.pereira@ssc-spc.gc.ca> To: <blind-sysadmins@lists.hodgsonfamily.org> Sent: Tuesday, August 06, 2019 9:37 PM Subject: [Blind-sysadmins] Re: Terminal improvements are coming to NVDA 2019.3!
This is amazing news. Hopefully there are others looking at those applications that also provide challenges with text to speech users. These would be items like MS Project, Open Office etc.
Vic Pereira
Project Manager, Network, Security and Digital Services (NSDS) Shared Services Canada, Government of Canada vic.pereira@ssc-spc.gc.ca / Tel: 204-781-5046
Gestionnaire de Projet, Réseaux, sécurité et services numériques (RSSN) Services partagés Canada, Gouvernement du Canada vic.pereira@ssc-spc.gc.ca / Tél. : 204-781-5046
-----Original Message----- From: Bill Dengler <codeofdusk@gmail.com> Sent: August-06-19 2:34 PM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: [Blind-sysadmins] Terminal improvements are coming to NVDA 2019.3!
Hello, I’ve been working as a Google Summer of Code student with NV Access over the past couple of months. My project <https://summerofcode.withgoogle.com/organizations/5317267756154880/> involves improving NVDA performance and stability in the Windows Console used by Command Prompt, PowerShell, and the Windows Subsystem for Linux on Windows 10 version 1803 and later. The new console support is set to ship as part of NVDA 2019.3, to be released later this year. In the mean time, I’d greatly appreciate your testing of, and feedback from, the latest master (alpha) snapshots, which can be found on this page <http://nvda-project.org/snapshots>. A limited version of the new support will also ship in 2019.2 within the next few weeks behind a feature flag.
Thanks in advance for testing, and be sure to let me know what you think! Bill _______________________________________________ Blind-sysadmins mailing list -- blind-sysadmins@lists.hodgsonfamily.org To unsubscribe send an email to blind-sysadmins-leave@lists.hodgsonfamily.org _______________________________________________ Blind-sysadmins mailing list -- blind-sysadmins@lists.hodgsonfamily.org To unsubscribe send an email to blind-sysadmins-leave@lists.hodgsonfamily.org
_______________________________________________ Blind-sysadmins mailing list -- blind-sysadmins@lists.hodgsonfamily.org To unsubscribe send an email to blind-sysadmins-leave@lists.hodgsonfamily.org
Blind-sysadmins mailing list -- blind-sysadmins@lists.hodgsonfamily.org To unsubscribe send an email to blind-sysadmins-leave@lists.hodgsonfamily.org