Re: How is verbosity decided
|
Quentin Christensen
Firstly, Yes you are correct, figures are reported but there is currently no document formatting option to toggle that. There is, however, an issue for that already - so do feel free to subscribe to that for updates on when it is updated: https://github.com/nvaccess/nvda/issues/10826 The idea of including configuration profiles in NVDA itself is of course possible, but what would be included? (rhetorical question!) If we did that, then suddenly some programs would behave differently to others - or you'd really want to change a setting, and yet it wouldn't be changed in every program, and why does NVDA read this really useful information in Word but not Firefox? It would cause more problems than it would solve, especially as how one user uses Word for instance, might be very different to how another user does. So the best solution, we feel, is to not have any configuration profiles setup by default, but to hopefully teach users how to access them. I have put forward my idea for improving configuration profiles here: https://github.com/nvaccess/nvda/issues/10322 - as with any other issue, feel free to subscribe to that, or to add your own 2 cents to it if you have a point to add which hasn't been made already on the issue. The scripts term is a bit confusing. Most of the time when people use it, they mean either Jaws scripts or NVDA add-ons. In fact, the term has crept into our "What's new" document (in quite a few places as I look at it now) to mean a software function in NVDA itself. For instance in 2020.3 one change was: "The Report formatting script (NVDA+f) has now been changed to report the formatting at the system caret rather than at the review cursor position. To report formatting at the review cursor position now use NVDA+shift+f. (#9505)" Which refers to NVDA's own internal routine which runs when a user presses NVDA+f. So Gene's comment about NVDA using "scripts for various programs", is (I think I'm reading his intentions correctly) in line with that usage of the word, and I'm happy to put my hand up and say we can take the blame for that particular confusion :) Also the difference between bug report and feature request is more around the prompts in the template itself - the issue still ends up in the same place (as an issue), and several people have commented that we should actually add a few more of the prompt questions from the bug report template to the feature request template. In essence, whatever you are reporting or requesting, try to include as much information as possible which might be relevant, even if it isn't explicitly asked. Quentin. On Thu, Dec 17, 2020 at 9:56 AM Brian Vogel <britechguy@...> wrote: On Wed, Dec 16, 2020 at 05:13 PM, Gene wrote: --
Quentin Christensen Training and Support Manager Training: https://www.nvaccess.org/shop/ Certification: https://certification.nvaccess.org/ User group: https://nvda.groups.io/g/nvda Facebook: http://www.facebook.com/NVAccess Twitter: @NVAccess |
|
|