Date   

Re: first inprocess

Eduardo Fermiano Luccas
 

https://www.nvaccess.org/post/introducing-in-process/
Sorry, I forgot to put the link, I hope you read it with love even after that

Em qui., 25 de nov. de 2021 às 22:21, Gene <gsasner@...> escreveu:

You evidently tried to send an attachment.  This list, and lists in general, don’t accept attachments for security reasons.  You can upload the material to a file sharing service and send a link in a message.
 
Gene
-----Original Message-----
Sent: Thursday, November 25, 2021 2:36 PM
Subject: [nvda] first inprocess
 
Hello friends, it is with great affection that I send the first in process which was on January 20, 2017! I hope old users remember, and 2020 users like me, I hope you read this to see how the in process was introduced!


Re: first inprocess

Gene
 

You evidently tried to send an attachment.  This list, and lists in general, don’t accept attachments for security reasons.  You can upload the material to a file sharing service and send a link in a message.
 
Gene

-----Original Message-----
Sent: Thursday, November 25, 2021 2:36 PM
Subject: [nvda] first inprocess
 
Hello friends, it is with great affection that I send the first in process which was on January 20, 2017! I hope old users remember, and 2020 users like me, I hope you read this to see how the in process was introduced!


nv speech player

Eduardo Fermiano Luccas
 

hello friends, i was talking to quentin about the NV speech player addon support, and i think it would be nice for a user who understands that to continue the project! i know that with NVDA 2021.2 we had espeak NG with the same voices and i thought even better, but it's not for me, it's for users who like eloquence and can't buy it, so someone can continue this project, it would be really cool


Thanksgiving greetings

udit pandey
 

hi group,
I want to say to you all
Happy Thanksgiving to everyone if you celebrate it in your country


first inprocess

Eduardo Fermiano Luccas
 

Hello friends, it is with great affection that I send the first in process which was on January 20, 2017! I hope old users remember, and 2020 users like me, I hope you read this to see how the in process was introduced!


locked Owner's Note: Thank You #adminnotice

Nimer Jaber
 

Hello,

On this Thanksgiving day in the U.S., I want to babble and do a bit of reflection, and I hope you will read this message thoroughly. I hope this message finds all of you happy, healthy, content, etc.

This past year has been nothing short of a nightmare for many of us. I know I have, and continue to face struggles, and I have no doubt that many of you are as well. All I can say is, we need to try to remain resilient. We need to lean on one another. We need to lean into those things that make each of us who we are. We need to love, we need to live, and we need to laugh. A lot. Some of us also need to grieve. We need to work through our pain. We need to scream,  we need to cry. For those things, all of those things are what unite us as human beings, across cultures, across religious boundaries, across borders.

In all of that, I want to thank you. Thank you for being part of this community. Thank you for passing along your knowledge to others. Thank you for being part of what makes this community a community. We are all united around NVDA, of course, but we are also unique individuals with struggles, hopes, dreams, etc., and anyone contributing to this community helps make it what it is. Whether you are here to post your questions, or are mostly providing answers, and even if you are simply a lurker, thank you. I am grateful for your support, for being here. We might disagree with one another at times, we might get annoyed at one another at times, but we are all humans, all here united around NVDA.

I also want to thank NvAccess. They are the reason we are here, of course, and they provide equity where that wasn't a thing before NVDA, to many who can now use their computers at no cost. Should you feel called to do so, please consider giving to NVAccess in the form of a donation this year. There are many deals this time of year, of lots of things to buy, but we can all help make sure that NVAccess continues to deliver.

Finally, I realize that Thanksgiving is not celebrated by everyone, and I recognize that some may even be hurting on this day. If you are one of those individuals, I want you to feel comfortable reaching out to me personally, using the contact information in my signature. I am happy to talk to you, and to do what I can to help. If you are an Indigenous person, I hope that you will understand the intent behind this message, and recognize that it is not my intent to cause you suffering. If, for some other reason, you are struggling on this day, I am sorry for your pain, and I hope you will reach out to someone. You are not alone.

--
Best,

Nimer Jaber

Registered Linux User 529141.
http://counter.li.org/

To find out about a free, open-source, and versatile screen reader for Windows, visit nvaccess.org

You can follow @nimerjaber on Twitter for the latest technology news.

Thank you, and have a great day!


Re: wanted eliquence for my old nvda on windows 7

Gene
 

You can avoid such problems if all you want is Eloquence by hnot purchasing the Eloquence Add-on, which comes with another synthesizer and not just Eloquence.  You can purchase the Eloquence MSAPI5 version.  This version only contains Eloquence and you can use it with any program that supports the MSAPI5 speech interface.  And no matter how NVDA is updated, the MSAPI version will work so you don’t have to worry about losing access to it for a short while now and then because of an occasional NVDA update. 
 
Gene

-----Original Message-----
Sent: Thursday, November 25, 2021 3:22 AM
Subject: Re: [nvda] wanted eliquence for my old nvda on windows 7
 
Well you can buy the code factory sapi ones for like 60 bucks or the
nvda one atguys.com should have all those.

I use eloquence and vocaliser in sapi and for all they are they are good
packages with good interfaces.

The only issue I have ever had was after a version update vocaliser
forgot to tell me they would be updating some voices and not
reinstalling them so I had  to remove all voices and put them back which
wasted an hour but that was fine.



On 25/11/2021 10:19 pm, sazid wrote:
> dear group members, can anyone provide me synths for my nvda running
> on windows 7
>
> thanks and regards,
> sazid
>
>
>
>
>





Re: wanted eliquence for my old nvda on windows 7

Gene
 

Your subject line says you want Eloquence.  Your message doesn’t specify. 
 
I shall assume in this message that you only want Eloquence.  Let us know if that isn’t correct. 
 
You can buy Eloquence and the same Eloquence will work in Windows 7 as in later versions of Windows.  I’ll let those more familiar with ;purchasing Eloquence discuss it further.  I will say, however, that there is a demo which runs for seven days so you can evaluate it.
 
Gene

-----Original Message-----
From: sazid
Sent: Thursday, November 25, 2021 3:19 AM
To: nvda
Subject: [nvda] wanted eliquence for my old nvda on windows 7
 
dear group members, can anyone provide me synths for my nvda running
on windows 7

thanks and regards,
sazid





Re: wanted eliquence for my old nvda on windows 7

 

Well you can buy the code factory sapi ones for like 60 bucks or the nvda one atguys.com should have all those.

I use eloquence and vocaliser in sapi and for all they are they are good packages with good interfaces.

The only issue I have ever had was after a version update vocaliser forgot to tell me they would be updating some voices and not reinstalling them so I had  to remove all voices and put them back which wasted an hour but that was fine.

On 25/11/2021 10:19 pm, sazid wrote:
dear group members, can anyone provide me synths for my nvda running
on windows 7

thanks and regards,
sazid




wanted eliquence for my old nvda on windows 7

sazid
 

dear group members, can anyone provide me synths for my nvda running
on windows 7

thanks and regards,
sazid


Re: Outlook 2010 focus problem

Gene
 

We don’t know what the problem is and we don’t know enough to assume it is an NVDA problem.  It should be tested with another screen-reader to see if the same problem occurs.
 
Gene

-----Original Message-----
Sent: Wednesday, November 24, 2021 10:27 PM
Subject: [nvda] Outlook 2010 focus problem
 
Hi guys


I do not use this program at all but a user from another list is having
the below problem


I have an annoying problem where I loose focus when using outlook 2010. 
I can arrow up and down but can’t hear emails.  I have had to tab to the
to do bar or go out and back again.  I mean tab say to desktop then back
in.  Other times I had to go and restart NVDA.


She has used the com tool still with the same results.


I will get her to tell me also what version of nvda she has.


Has any one got any ideas of what she can try?


Gene nz


Has any one got any ideas of what she can try to fix the problem.




a






Re: Outlook 2010 focus problem

 

Gene,

             The following is said without a trace of snark:  Update Office.

              Office 2010 has been out of support by Microsoft for some time now, and all of the current supported versions of Microsoft Office have their roots in Office 2016.

              There will be more and more and more issues as time marches on and a very great many may have no fix, too.  None of the screen reader makers is going to even try to fix issues with Office 2010 as those occur at this juncture.  They've got to focus on what's current as well as what they have preview builds for on software that's "coming up soon."
--

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

 


Outlook 2010 focus problem

hurrikennyandopo ...
 

Hi guys


I do not use this program at all but a user from another list is having the below problem


I have an annoying problem where I loose focus when using outlook 2010.  I can arrow up and down but can’t hear emails.  I have had to tab to the to do bar or go out and back again.  I mean tab say to desktop then back in.  Other times I had to go and restart NVDA.


She has used the com tool still with the same results.


I will get her to tell me also what version of nvda she has.


Has any one got any ideas of what she can try?


Gene nz


Has any one got any ideas of what she can try to fix the problem.




a


Re: accessible way of moving playlists to folders in spotify?

Eduardo Fermiano Luccas
 



Em ter., 23 de nov. de 2021 às 17:47, Gene <gsasner@...> escreveu:

I only played with the attachment a little bit but I’m not sure it does anything more than the method for dragging and dropping already available in NVDA. 
 
Gene
-----Original Message-----
Sent: Tuesday, November 23, 2021 2:18 PM
Subject: Re: [nvda] accessible way of moving playlists to folders in spotify?
 

Yeah seems to have a nightmare with object navigation. At times I get an object has no location when using the review cursor and navigator to find the correct playlist.

On 23/11/2021 20:00, Sarah k Alawami wrote:

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 mailto: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

 


Re: Is the Windows 10 (and, I'd presume, 11) Sandbox Feature Accessible?

farhan israk
 

Thank you.


On Tue, 23 Nov 2021, 10:07 pm Joseph Lee, <joseph.lee22590@...> wrote:

Hi,

Regarding keyboard shortcuts, it will feel like logging onto a Remote Desktop session - you would press Control+Alt+Break (Pause) key to switch between host (the computer you are using) and guest (sandboxed environment). The way I run NVDA (or for that matter, any screen reader other than Narrator) inside Windows Sandbox is:

  1. On the host computer, prepare the screen reader files - NVDA installer or a portable copy of NVDA.
  2. Copy the screen reader file(s) to the clipboard.
  3. Go to Windows Sandbox and switch to the guest environment.
  4. Open a folder location (say, Documents). The easiest way is typing the name of the folder from Run dialog.
  5. When the desired folder opens in the guest environment, paste the just copied scren reader file(s).
  6. Because it will take time for files to be copied (especially if you are copying a folder containing portable NVDA files), switch out of sandboxed environment, then use Windows OCR (NVDA+R) to recognize what Windows Sandbox is displaying.
  7. Once the copy operation is complete, switch back to the sandboxed environment, locate NVDA executable and run it.

You can also do all these with Narrator on - just before opening the folder in the guest environment (just after performing step 3), press Control+Windows+Enter while switched to the guest environment to start Narrator inside the sandbox. When NVDA starts, close Narrator.

I belive Windows Sandbox was covered somewhat on WinAccess forum (may need to check the archive for that one).

Cheers,

Joseph


Re: Clock and StationPlaylist add-on 21.11 released #addonrelease

 

Hi,

And finally, StationPlaylist add-on 21.11 is now being distributed via Add-on Updater.

Cheers,

Joseph


Re: Rearrange Pinned Items

Jason Bratcher
 

Hence why to check your pointer speed and acceleration sliders so you don't have an out-of-control cheese seeker!

-
Jason Bratcher


Re: More flexible line length in browsing mode

Steve Nutt
 

It's something that Window-Eyes always allowed you to do. You could set a line length, but if you set it to 0, it would honour the HTML structure.

All the best

Steve

--
To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

Computer Room Services
77 Exeter Close
Stevenage
Hertfordshire
SG1 4PW
T: +44(0)1438-742286
M: +44(0)7956-334938
F: +44(0)1438-759589
E: steve@...
W: https://www.comproom.co.uk

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: 24 November 2021 12:49
To: nvda@nvda.groups.io
Subject: Re: [nvda] More flexible line length in browsing mode

Its an interesting question and one I haven't thought about. I find it a good idea to allow the maximum line length to be changed but is there a technical reason it is better to set a maximum length in the browse mode buffer than have the length determined by the screen width, as is the case in the presentation of the underlying HTML page?


Gene

On 11/24/2021 3:36 AM, Steve Nutt wrote:

I don't quite get why we need a line length mode anyway.

It would be good if NVDA could honour the lines on the screen, even in the virtual buffer.

I like the screen layout support, where links appear where they should, so why not make this work for formatting as well?

All the best

Steve

--
To subscribe to our News and Special Offers list, go to
https://www.comproom.co.uk/subscribe

Computer Room Services
77 Exeter Close
Stevenage
Hertfordshire
SG1 4PW
T: +44(0)1438-742286
M: +44(0)7956-334938
F: +44(0)1438-759589
E: steve@...
W: https://www.comproom.co.uk

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Martin J.
Dürst
Sent: 24 November 2021 08:25
To: nvda@nvda.groups.io
Subject: Re: [nvda] More flexible line length in browsing mode

Hello Gene,

Many thanks for your mail. We want to try and find out whether there is a difference between various ways of reading text (fixed one-hundred characters or somewhat more flexible). Of course, if there's a link, and NVDA is set to read that separately, I guess we will read that separately.

Regards, Martin.

On 2021-11-21 11:20, Gene via groups.io 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
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.











--
Prof. Dr.sc. Martin J. Dürst
Department of Intelligent Information Technology College of Science
and Engineering Aoyama Gakuin University Fuchinobe 5-1-10, Chuo-ku,
Sagamihara
252-5258 Japan












Re: More flexible line length in browsing mode

Gene
 

Its an interesting question and one I haven't thought about.  I find it a good idea to allow the maximum line length to be changed but is there a technical reason it is better to set a maximum length in the browse mode buffer than have the length determined by the screen width, as is the case in the presentation of the underlying HTML page?


Gene

On 11/24/2021 3:36 AM, Steve Nutt wrote:

I don't quite get why we need a line length mode anyway.

It would be good if NVDA could honour the lines on the screen, even in the virtual buffer.

I like the screen layout support, where links appear where they should, so why not make this work for formatting as well?

All the best

Steve

--
To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

Computer Room Services
77 Exeter Close
Stevenage
Hertfordshire
SG1 4PW
T: +44(0)1438-742286
M: +44(0)7956-334938
F: +44(0)1438-759589
E: steve@...
W: https://www.comproom.co.uk

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Martin J. Dürst
Sent: 24 November 2021 08:25
To: nvda@nvda.groups.io
Subject: Re: [nvda] More flexible line length in browsing mode

Hello Gene,

Many thanks for your mail. We want to try and find out whether there is a difference between various ways of reading text (fixed one-hundred characters or somewhat more flexible). Of course, if there's a link, and NVDA is set to read that separately, I guess we will read that separately.

Regards, Martin.

On 2021-11-21 11:20, Gene via groups.io 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
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.











--
Prof. Dr.sc. Martin J. Dürst
Department of Intelligent Information Technology College of Science and Engineering Aoyama Gakuin University Fuchinobe 5-1-10, Chuo-ku, Sagamihara
252-5258 Japan











Re: More flexible line length in browsing mode

Steve Nutt
 

I don't quite get why we need a line length mode anyway.

It would be good if NVDA could honour the lines on the screen, even in the virtual buffer.

I like the screen layout support, where links appear where they should, so why not make this work for formatting as well?

All the best

Steve

--
To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

Computer Room Services
77 Exeter Close
Stevenage
Hertfordshire
SG1 4PW
T: +44(0)1438-742286
M: +44(0)7956-334938
F: +44(0)1438-759589
E: steve@...
W: https://www.comproom.co.uk

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Martin J. Dürst
Sent: 24 November 2021 08:25
To: nvda@nvda.groups.io
Subject: Re: [nvda] More flexible line length in browsing mode

Hello Gene,

Many thanks for your mail. We want to try and find out whether there is a difference between various ways of reading text (fixed one-hundred characters or somewhat more flexible). Of course, if there's a link, and NVDA is set to read that separately, I guess we will read that separately.

Regards, Martin.

On 2021-11-21 11:20, Gene via groups.io 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
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.












--
Prof. Dr.sc. Martin J. Dürst
Department of Intelligent Information Technology College of Science and Engineering Aoyama Gakuin University Fuchinobe 5-1-10, Chuo-ku, Sagamihara
252-5258 Japan

7021 - 7040 of 96924