Re: NVDA Settings Documentation
There is no truncating. I worked with the feature in JAWS years ago. I don't remember the line length in JAWS, if it was the same, longer or shorter than in NVDA, both using default settings. The point of it is that the MSAA buffer needs to have a line length set. the underlying page has none and the line length is determined by how much will fit on the screen being used unless the page designer has placed line codes on the page, which they usually don't. So you can set the length of a line you hear when you up and down arrow on a page.toggle quoted messageShow quoted text
If I am looking for something on a page and I want to be able to move quickly from line to line listening to a bit and then moving on, I may want shorter lines than the default so I can quickly move by line and when I'm close to what I'm looking for, slow down. If lines are too long, I may miss what I'm looking for because it may be near the ende of a long line and I may move down before hearing it.
Others may have other uses. That is the use I made of the feature. I set the line length to be shorter and left it there so I could move quickly from line to line and not have too much on a line to prevent easy skimming.
From: Brian Vogel
Sent: Monday, October 19, 2020 6:45 PM
Subject: Re: [nvda] NVDA Settings Documentation
Here's some input in the form of questions.
What constitutes a line?
Does the maximum number of characters result in truncation and, if so, under what reading conditions? (I can't imagine this setting affects read all behavior, for instance).
If a line (after defined) is longer than that maximum, what happens when that occurs during browse mode?
Brian - Windows 10 Pro, 64-Bit, Version 2004, Build 19041
It’s hard waking up and realizing it’s not always black and white.
~ Kelley Boorn