As Gene noted, the line length in NVDA is a simple number - and it doesn't
look to see if it can "just add the last word of a sentence". I can see
that it might be advantageous though, I would suggest the best thing to do
is create an issue on our tracker at:
https://github.com/nvaccess/nvda/issues requesting the feature.
Kind regards
Quentin.
On Sun, Nov 21, 2021 at 1:20 PM Gene <gsasner@...> wrote:

In browse mode, you can set the line length. The default is one-hundred
carachters. I suppose it would be possible to have a read by sentence
option but I don’t know if there is any .demand for that. And it would
conflict with sentences in which there are links and you have NVDA set to
read every link on its own line.

Gene
-----Original Message-----
*From:* Tony Malykh <anton.malykh@...>
*Sent:* Saturday, November 20, 2021 7:43 PM
*To:* nvda@nvda.groups.io
*Subject:* Re: [nvda] More flexible line length in browsing mode

I believe in browse mode lines are defined visually, I don't recall NVDA
setting that would define line length.

If you would like to read by sentences, you can install my SentenceNav
add-on.

HTH

--Tony

On 11/18/2021 11:07 PM, Martin J. Dürst wrote:

Hello everybody,

I have been using NVDA on and off for a few weeks. It's really a great
help. I'm new to this mailing list, so please forgive me if I'm asking
something old.

When reading text from a Web page, the text is read in "lines", and
the user presses arrow-down for each line. NVDA has a setting for line
length, which is at 100 characters originally. So well, so good.

What I find somewhat confusing, and possibly a place for improvement,
is that often a "line" ends a word or two before the end of a
sentence, or includes a word or two of a new sentence. I suspect that
quit a bit of thought must have gone into this, but I haven't found
any details yet.

I would really appreciate if somebody could explain why "lines" end at
arbitrary positions in sentences, and are not done a bit more flexibly
so that they more often end at the end of a sentence.

If this has been discussed already, I would appreciate pointers. Also
if there's some scientific paper about the issue.

I have tried to think about why things are as described above, and
have come up with various possible reasons. If any of these reasons
applies, please just tell me.

- There is already a setting/add-on for this, just use it.

- Having more variable line lengths would make it more difficult to read
Web pages (e.g. because the intervals between the presses of the down
arrow would be more irregular). If that's the case, then I haven't yet
had enough practice to notice it.

- Finding better positions to split text into lines is a much harder
problem than it looks. It is difficult to find actual sentence
boundaries in text (not all periods are sentence endings), and
long sentences without punctuation are also difficult to split.

- Finding better positions to split is possible, but good algorithms
are too slow. Text-to-speech conversion already uses quite a bit
of processing power.

- Finding sentence boundaries is quit language dependent, and therefore
difficult to implement in a general way.

- The overall architecture of NVDA (and other screen readers) makes
it too difficult to implement such a feature.

- Some other screen readers already do a better job at this, but we
at NVDA just have not had time to get around to do something here.
Help is appreciated. (I might want to help.)

- That's how screen readers always have done it, and everybody is
used to it, and so changing it isn't a good idea.

If there are any other actual or potential reasons, please tell me.

Many thanks in advance for your help.

With kind regards, Martin.

In browse mode, you can set the line length. The default is one-hundred carachters. I suppose it would be possible to have a read by sentence option but I don’t know if there is any .demand for that. And it would conflict with sentences in which there are links and you have NVDA set to read every link on its own line.
Gene
-----Original Message-----
From: Tony Malykh
Sent: Saturday, November 20, 2021 7:43 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] More flexible line length in browsing mode
I believe in browse mode lines are defined visually, I don't recall NVDA
setting that would define line length.
If you would like to read by sentences, you can install my SentenceNav
add-on.
HTH
--Tony
On 11/18/2021 11:07 PM, Martin J. Dürst wrote:

Hello everybody,

I have been using NVDA on and off for a few weeks. It's really a great
help. I'm new to this mailing list, so please forgive me if I'm asking
something old.

When reading text from a Web page, the text is read in "lines", and
the user presses arrow-down for each line. NVDA has a setting for line
length, which is at 100 characters originally. So well, so good.

What I find somewhat confusing, and possibly a place for improvement,
is that often a "line" ends a word or two before the end of a
sentence, or includes a word or two of a new sentence. I suspect that
quit a bit of thought must have gone into this, but I haven't found
any details yet.

I would really appreciate if somebody could explain why "lines" end at
arbitrary positions in sentences, and are not done a bit more flexibly
so that they more often end at the end of a sentence.

If this has been discussed already, I would appreciate pointers. Also
if there's some scientific paper about the issue.

I have tried to think about why things are as described above, and
have come up with various possible reasons. If any of these reasons
applies, please just tell me.

- There is already a setting/add-on for this, just use it.

- Having more variable line lengths would make it more difficult to read
Web pages (e.g. because the intervals between the presses of the down
arrow would be more irregular). If that's the case, then I haven't yet
had enough practice to notice it.

- Finding better positions to split text into lines is a much harder
problem than it looks. It is difficult to find actual sentence
boundaries in text (not all periods are sentence endings), and
long sentences without punctuation are also difficult to split.

- Finding better positions to split is possible, but good algorithms
are too slow. Text-to-speech conversion already uses quite a bit
of processing power.

- Finding sentence boundaries is quit language dependent, and therefore
difficult to implement in a general way.

- The overall architecture of NVDA (and other screen readers) makes
it too difficult to implement such a feature.

- Some other screen readers already do a better job at this, but we
at NVDA just have not had time to get around to do something here.
Help is appreciated. (I might want to help.)

- That's how screen readers always have done it, and everybody is
used to it, and so changing it isn't a good idea.

If there are any other actual or potential reasons, please tell me.

Many thanks in advance for your help.

With kind regards, Martin.

I believe in browse mode lines are defined visually, I don't recall NVDA setting that would define line length.
If you would like to read by sentences, you can install my SentenceNav add-on.
HTH
--Tony
On 11/18/2021 11:07 PM, Martin J. Dürst wrote:

Hello everybody,

I have been using NVDA on and off for a few weeks. It's really a great help. I'm new to this mailing list, so please forgive me if I'm asking something old.

When reading text from a Web page, the text is read in "lines", and the user presses arrow-down for each line. NVDA has a setting for line length, which is at 100 characters originally. So well, so good.

What I find somewhat confusing, and possibly a place for improvement, is that often a "line" ends a word or two before the end of a sentence, or includes a word or two of a new sentence. I suspect that quit a bit of thought must have gone into this, but I haven't found any details yet.

I would really appreciate if somebody could explain why "lines" end at arbitrary positions in sentences, and are not done a bit more flexibly so that they more often end at the end of a sentence.

If this has been discussed already, I would appreciate pointers. Also if there's some scientific paper about the issue.

I have tried to think about why things are as described above, and have come up with various possible reasons. If any of these reasons applies, please just tell me.

- There is already a setting/add-on for this, just use it.

- Having more variable line lengths would make it more difficult to read
  Web pages (e.g. because the intervals between the presses of the down
  arrow would be more irregular). If that's the case, then I haven't yet
  had enough practice to notice it.

- Finding better positions to split text into lines is a much harder
  problem than it looks. It is difficult to find actual sentence
  boundaries in text (not all periods are sentence endings), and
  long sentences without punctuation are also difficult to split.

- Finding better positions to split is possible, but good algorithms
  are too slow. Text-to-speech conversion already uses quite a bit
  of processing power.

- Finding sentence boundaries is quit language dependent, and therefore
  difficult to implement in a general way.

- The overall architecture of NVDA (and other screen readers) makes
  it too difficult to implement such a feature.

- Some other screen readers already do a better job at this, but we
  at NVDA just have not had time to get around to do something here.
  Help is appreciated. (I might want to help.)

- That's how screen readers always have done it, and everybody is
  used to it, and so changing it isn't a good idea.

If there are any other actual or potential reasons, please tell me.

Many thanks in advance for your help.

With kind regards,   Martin.

.

I just had a look on mine - Windows 10 (64-bit) Version: 21H2 (2009), Build: 19044.1348 and collapsing items on the start menu leaves the focus on the collapsed item, as expected.

With the symbol grouping - could it be your punctuation level?  Mine is called "#" and that does read as "Number grouping" at some, most and all, but if you have your punctuation level set to "none" it just reads "Grouping".

Quentin.

On Tue, Nov 23, 2021 at 5:29 PM Shaun Everiss <sm.everiss@...> wrote:

This is windows 10 I thought I put 10 in the message somewhere.

On 23/11/2021 7:22 pm, Arlene wrote:

Hi, Is this windows ten or 11?

 

Sent from Mail for Windows

 

From: Shaun Everiss
Sent: November 22, 2021 9:43 PM
To: nvda@nvda.groups.io
Subject: [nvda] anyone noticed this

 

Hi.

 

Well

 

Just got the latest windows build

 

21.2 19.441387 build released today.

 

This had the windows installer fix.

 

I have however noticed a small issue which isn't an issue as such

because I can get round it easy enough.

 

Its just when I select the first item in the start menu ie hitting down

arrow from search I get all apps, then you get the programs starting

with punctuation like & or *, etc well that group does not read but the

items in it do and can be executed.

 

When colapsing a group it seems I get jumpped back to the top of the

list as well.

 

Again not a real big huge issue since I mostly search anyway but just

wandered if anyone has noticed.

 

I have not had any other issues in fact things seem a bit more stable,

but we will see what happens after I do some more shell work.

 

 

 

 

 

 

 

 

--

Quentin Christensen
Training and Support Manager

Web: www.nvaccess.org 

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

Since it is electron I doubt it will work. I have not had any luck using this add on for dragging dropping  stuff, at all. Not to say it does not work, but for me it has worked maybe 1 time out of the 10 or so I’ve used it.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Orhan Deniz via groups.io
Sent: Tuesday, November 23, 2021 11:46 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] accessible way of moving playlists to folders in spotify?

 

It seems that when I try to mark a playlist, then drop it into the relevant folder I get a can't drop here error. I am not sure if this add on will work with spotify playlists, but I will give it more of a road-test.

On 23/11/2021 19:39, Brian Vogel wrote:

Orhan,

Just FYI, this add-on is compatible with 2021.3 and, in addition, does have help/usage information packaged with it that you can access via gaining focus the add-on in Add-Ons Manager (NVDA + N, T, A, Enter) then activating the Add-On Help button.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 

It seems that when I try to mark a playlist, then drop it into the relevant folder I get a can't drop here error. I am not sure if this add on will work with spotify playlists, but I will give it more of a road-test.

Orhan,

Just FYI, this add-on is compatible with 2021.3 and, in addition, does have help/usage information packaged with it that you can access via gaining focus the add-on in Add-Ons Manager (NVDA + N, T, A, Enter) then activating the Add-On Help button.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 

Hi, Drag and drop add-ons may also help.

Cheers

Orhan,

Just FYI, this add-on is compatible with 2021.3 and, in addition, does have help/usage information packaged with it that you can access via gaining focus the add-on in Add-Ons Manager (NVDA + N, T, A, Enter) then activating the Add-On Help button.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 

Orhan,

I mentioned the following just last night in a topic about Rearranging Task Bar Items, but since you weren't a member then, you would not have seen it.

Javi Dominguez has written an add-on for Drag and Drop, which others have said is very helpful.  And by that I mean helpful in achieving actual drag and drop regardless of the context.  It would be worth a try.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy