Date   

Re: My Documents Opening In Windows Media Player

Narayan <krishnashree1221@...>
 

it is very easy. first select the file which you want to open, right click on this, and find open with option, and hit on choose default program option from the list. then select proper application from the appropriate list and check the next option called always open this file with this application. and press OK. that's it.

On 1/1/2018 3:47 AM, Ibrahim Ajayi wrote:
Hello:
I am having another unusual and odd problem.
But this problem has nothing to do with NVDA, although I use the screenreader.
Actually, many of my documents are now opening in windows media
player. The documents were created by me in microsoft word, and
wordpad, but now they open in windows media player.
I am also having the same problem with some materials Emailed to me.
The attachments are in word document,, but when I attempt to open
them, they open in windows media player.
I just can't figure out what this problem is all about.
Please has anyone ever had this problem at any time? how did you resolve it.
Hope to read your response.
Ibrahim.

--
Shree


My Documents Opening In Windows Media Player

Ibrahim Ajayi
 

Hello:
I am having another unusual and odd problem.
But this problem has nothing to do with NVDA, although I use the screenreader.
Actually, many of my documents are now opening in windows media
player. The documents were created by me in microsoft word, and
wordpad, but now they open in windows media player.
I am also having the same problem with some materials Emailed to me.
The attachments are in word document,, but when I attempt to open
them, they open in windows media player.
I just can't figure out what this problem is all about.
Please has anyone ever had this problem at any time? how did you resolve it.
Hope to read your response.
Ibrahim.


Problem facing in google-chrome

Narayan <krishnashree1221@...>
 

Hi group members, I am using google chrome with NVDA screen reader. but, i am facing a problem in this. from 2-3 days some contents are not displayed properly in google chrome.I cannot navigate paragraphs in website using arrow keys correctly. if i navigate using tab, there only links are displayed. I cannot access all the contents in the page using arrow keys. please help me providing solution. thanks in advance.

Shree


Problem facing in NVDA with office 2007

Narayan <krishnashree1221@...>
 

hi group members, i am using Microsoft office word 2007 with NVDA screen reader for my PHD work in Hindi. when i use arrow keys for reading, some time
paragraphs or lines are not speak properly. some time NVDA gets hanging. what can i do? please help me for it. thanks in advance.

--
Shree


Re: help wanted in porting espeak fixes over to windows

Peter Beasley
 

Espeak is rubbish.

-----Original Message-----
From: Shaun Everiss
Sent: Sunday, December 31, 2017 6:56 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] help wanted in porting espeak fixes over to windows

To be honest, and I know all the devs will shoot me down for this, but I
have sceen no real reason that we shouldn't drop back to the last real
version of espeak by default, have espeak ng as an optional or include
both synths they have seperate directorys for data and so I see no real
reason we can't have both installed, true espeak ng's espeak.dll will
have to be espeakng.dll or something but to be honest.

The espeak ng screwups don't worry me that much but I do know for bidden
is not fir bidden.

pir cent is not purcent.

or whatever it is.

Its almost like spaces in some words are being added when they were
coded in.

At any rate, mr espeak robot is not to be understood.

Its a crappy low powered synth used for admin work and other generalness.

If I wanted my voices understood I'd use my slow good quality but
resource hungry synth I have about.

Its not a big issue but the fact the list is growing.

They have fixed most of the accent issues but even so.

I really do hope that things continue to work.




On 31/12/2017 8:51 p.m., Brian's Mail list account via Groups.Io wrote:
I had always understood that the engine in nvda is updated regularly to take account of fixes, but recently there seem to have been a number of nasty bugs and silly mispronunciations added during code clean up. I'm speaking about UK English here and so have gone back to Speech Player in Espeak add on to get to an older version of Espeak which does not have these issues.
In my view there seems to be a focus in the team to attempt to make the code understandable, by moving stuff about. I guess this makes sense if they want to understand it, but its not really doing anything to fix crashes inimogees, bad pronunciations or other strange funnies, in fact its already broken language dictionaries and some other bits on the latest nvda meaning that Nvda team had to make work around to help them use the latest code.
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: <coffeekingms@...>
To: <nvda@nvda.groups.io>
Sent: Sunday, December 31, 2017 4:18 AM
Subject: [nvda] help wanted in porting espeak fixes over to windows


Hi all
I maintain a repository of espeak fixes. That is, pronunciation fixes for the US English language for words and names espeak ng mangles, for Linux based operating systems, located at http//GitHub.com/coffeeking/espeak-en-us. I’ve been wanting to for some time port these over to windows and NVDA, as well as making them available to anyone using the sapi5 version of espeak ng. I don’t have the coding skills to do this though and need help. I’ve tried to get help on the espeak ng mailing list and no one seems interested. The biggest issue is writing a script to compile the fixes into espeak ng. I don’t know enough coding to do this. The other big problem is that to be able to compile the fixes, which are just text tfiles into the binary dictionary format espeak ng needs, you have to have installed espeak ng into whatever OS you use, I don’t think you can do it with just NVDA’s built in copy. I’d love to be able to get rid of this step if at all possible, since it would drastically increase the ease of new users being able to use and contribute to my fixes. My goal is to eventually become part of espeak ng’s development itself by helping reece dunn with US English, although I haven’t managed it yet. My fixes are occasionally added to espeak ng itself, but only when reece has time to comb through them and fix any I get wrong. Is anyone interested in helping me make it possible to use these with NVDA? I don’t know where NVDA looks for espeak ng’s dictionary files, so in addition to being able to compile the files, you have to copy them to wherever it is NVDA looks for them so it can pick up on them. I’m not sure about the sapi 5 version of espeak ng, but I’d like to make it possible for people to use my fixes regardless how they use espeak ng or what they use it on, right now it’s limited strictly to Linux or unix OSes since I had help with the bash script which compiles and copies them.
Thanks
Kendell Clark

Sent from my Vizio Ultrabook





.


Re: I'm dissappointed

Brian's Mail list account <bglists@...>
 

While I agree with you, I tend to think that the most experienced software writer for access has now gone and I'm not sure how anyone else but somebody who has lived with the code from its earliest days could get to the same level of expertise.
The second thing to think about are changes on the horizon of hardware and software generally making access for a screenreader which is not built in by the operating system maker to perform at all.
You only need to look at the model Apple use and the obvious direction Narrator is going. add to this the apparent idea Microsoft has to emulate Apple by having stuff in a store and only approved stuff will run with the screenreader built in reliably.
It would be interesting to be a fly on the wall of other software houses who make bespoke software which companies use. What are they going to do?

Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Shaun Everiss" <@smeveriss>
To: <nvda@nvda.groups.io>
Sent: Sunday, December 31, 2017 6:59 PM
Subject: Re: [nvda] I'm dissappointed


Sounds like we should restructure our files into modules.

Ie, profiles should be in some sort of setting files we can transfer away if we need, maybe more ini files.

We can maybe add other dictionaries and stuff to the program, I know that could make a few more broken things and space things but maybe if we could take more things away who knows.




On 31/12/2017 11:04 p.m., Sandra Pilz wrote:
Hi,

I'm a bit late but have only read the discussion now.

I have been using NVDA nearly exclusivelely since 2012 for work and also privately.

For the new job I started this year, I can only use NVDA, because JAWS will crash when I log into the web interface I am required to use.

However, I agree with Gene. JAWS is more easily configurable by the user. You can label graphics, you can assign window classes and see if that makes a program work more smoothly with NVDA, you can assign application specific hotkeys. I am not so sure if the JAWS frames feature still works so well under Windows 10. I just tried it recently without success.

Also, for me the question is not only can I do something with a screen reader, but also how quickly can I do what I need to do. One example for me is the text analysing feature of JAWS in MS Word. I think it helps a lot when writing a document and checking the formatting. I can do this with NVDA, too, but it takes a lot longer. The JAWS text analyser or whatever they call it just checks the document for me and allows me to
see where unexpected formatting or characters have been found. I then can check whether they are intended or not and make corrections. And it is so much quicker to do it that way than to read the entire document with NVDA reporting all attributes selectable in the document dialogue of NVDA. And additionally, the latter method is so monotonous that there is the risk of not catching all of the formatting problems.

I love using NVDA and think it can do a lot more than users of other screen readers may be aware of. But in a workplace setting, I might still recommend JAWS, because it is easier for people who are not programmers to adjust it so it can work with applications the way they need it to, and because tech support is available.

What would be the legal status for NVDA extensions written by a third party to make a specific program more accessible? If the would they be allowed to sell them? probably not, because NVDA is free. What would be the incentive for them to develop these extensions for rarely used software if they can only bill the hours once? With JAWS it's very clear, assistive tech companies can write scripts and sell them... That doesn't make JAWS better of course, I'm just wondering if this could be another reason why JAWS is chosen for the workplace more often than NVDA.

I think thanks to object navigation, NVDA could have a superior feature to JAWS' being able to read frames. It would be cool if we were able to specify a screen object, and then tell NVDA what we want it to do with the object: read it whenever content changes, leftclick or rightclick it and probably more. Frames in JAWS only worked if screen resolution didn't change. If the actions were tied to an object and not a frame thus not dependent on its dimensions on the screen, the configuration could work for different people with different screen resolutions.

Best

Sandra






Am 23.12.2017 um 23:52 schrieb Gene:
You can't label graphics, you can't create frames and there is no adjustment of the screen echo. There is also no way to skip baqck and forward by line when the screen echo is set to all or when using read to end and have speech continue. If these abilities were present, as far as I know, that would make NVDA as user configurable as JAWS and Window-eyes. These are important lacks in NVDA.
Gene
----- Original Message -----
*From:* Adriani Botez <mailto:adriani.botez@...>
*Sent:* Saturday, December 23, 2017 2:34 PM
*To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject:* Re: [nvda] I'm dissappointed

This is not correct. NVDA is well adjustable, even much easier than jaws.



Von meinem iPhone gesendet

Am 23.12.2017 um 03:47 schrieb Gene <gsasner@... <mailto:gsasner@...>>:

You can't do what I could do when I used Pine with a shell account a long time ago. I didn't need to create any frames or scripts. All I had to do was set the screen echo of JAWS to all, open a message, and then use the jaws skip line wile reading feature, right shift, to very quickly jump to the start of the message body. Even if NVDA reads such material when it appears on screen, you either listen to everything or nothing and use the tedious read by line screen review option. Hardly a convenient or reasonable way to go through thirty e-mails.
Like it or not, NVDA isn't user definable. You can't label graphics and you can't create frames. These are serious deficiencies even if many of us don't need such options.
And you can't set the screen echo to all and then do what I did, as I described. This may be an important ability for some users.
Gene
----- Original Message -----
*From:* coffeekingms@... <mailto:coffeekingms@...>
*Sent:* Friday, December 22, 2017 7:16 PM
*To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject:* Re: [nvda] I'm dissappointed

Hi

I concur. I firmly believe that NVDA can do most, if not all, the things more expensive programs can do. With some very rare exceptions. There are still some apps that require jfw with specific scripts to be usable, but as time goes on those apps will dwindle until there are none left. But for 99 percent of people, NVDA can work for them, either alone or in combination with narrator, which has gotten quite good. I don’t really set much store by such presentations, as the few I’ve bothered to listen to gloss over the free options as if they’re not there, are not worth mentioning or aren’t good enough. This applies to NVDA as well as open source operating systems like Linux. I have not listened to the presentation people are talking about, so I don’t want to ruffle any feathers, but as a rule I don’t listen to them. They tend to unilaterally insist that only the paid apps are worth using. Except for the NVDA podcasts. Those are great, although I don’t follow those either. I’m just a user. I use NVDA on a daily basis and have found very little that it can’t do. If it can’t navigate an app by the usual methods, tab, shift tab, arrows, then it can by either touch, if you have a touch screen or object navigation.Even when I was using Linux full time I would keep up with NVDA’s progress, and NVDA is what eventually brought me back to using windows again.

Thanks

Kendell Clark

Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

------------------------------------------------------------------------

*From:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> <nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>> on behalf of Don H <lmddh50@... <mailto:lmddh50@...>>
*Sent:* Friday, December 22, 2017 6:18:54 PM
*To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject:* Re: [nvda] I'm dissappointed
I think that NVDA is just as good or better than any other screen
reader. I think the issue for businesses is the fact that NVDA is open
source thus in their minds less secure.





Re: help wanted in porting espeak fixes over to windows

Brian's Mail list account <bglists@...>
 

Percent is even differently spoken in the progress bars to how it is in sentences as well.
It is a mess. I did raise this some months back, but I suspect that most devs are not using Espeak, and also many are Australian and they talk funny....
Hides behind sofa..
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Shaun Everiss" <@smeveriss>
To: <nvda@nvda.groups.io>
Sent: Sunday, December 31, 2017 6:56 PM
Subject: Re: [nvda] help wanted in porting espeak fixes over to windows


To be honest, and I know all the devs will shoot me down for this, but I have sceen no real reason that we shouldn't drop back to the last real version of espeak by default, have espeak ng as an optional or include both synths they have seperate directorys for data and so I see no real reason we can't have both installed, true espeak ng's espeak.dll will have to be espeakng.dll or something but to be honest.

The espeak ng screwups don't worry me that much but I do know for bidden is not fir bidden.

pir cent is not purcent.

or whatever it is.

Its almost like spaces in some words are being added when they were coded in.

At any rate, mr espeak robot is not to be understood.

Its a crappy low powered synth used for admin work and other generalness.

If I wanted my voices understood I'd use my slow good quality but resource hungry synth I have about.

Its not a big issue but the fact the list is growing.

They have fixed most of the accent issues but even so.

I really do hope that things continue to work.




On 31/12/2017 8:51 p.m., Brian's Mail list account via Groups.Io wrote:
I had always understood that the engine in nvda is updated regularly to take account of fixes, but recently there seem to have been a number of nasty bugs and silly mispronunciations added during code clean up. I'm speaking about UK English here and so have gone back to Speech Player in Espeak add on to get to an older version of Espeak which does not have these issues.
In my view there seems to be a focus in the team to attempt to make the code understandable, by moving stuff about. I guess this makes sense if they want to understand it, but its not really doing anything to fix crashes inimogees, bad pronunciations or other strange funnies, in fact its already broken language dictionaries and some other bits on the latest nvda meaning that Nvda team had to make work around to help them use the latest code.
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: <coffeekingms@...>
To: <nvda@nvda.groups.io>
Sent: Sunday, December 31, 2017 4:18 AM
Subject: [nvda] help wanted in porting espeak fixes over to windows


Hi all
I maintain a repository of espeak fixes. That is, pronunciation fixes for the US English language for words and names espeak ng mangles, for Linux based operating systems, located at http//GitHub.com/coffeeking/espeak-en-us. I’ve been wanting to for some time port these over to windows and NVDA, as well as making them available to anyone using the sapi5 version of espeak ng. I don’t have the coding skills to do this though and need help. I’ve tried to get help on the espeak ng mailing list and no one seems interested. The biggest issue is writing a script to compile the fixes into espeak ng. I don’t know enough coding to do this. The other big problem is that to be able to compile the fixes, which are just text tfiles into the binary dictionary format espeak ng needs, you have to have installed espeak ng into whatever OS you use, I don’t think you can do it with just NVDA’s built in copy. I’d love to be able to get rid of this step if at all possible, since it would drastically increase the ease of new users being able to use and contribute to my fixes. My goal is to eventually become part of espeak ng’s development itself by helping reece dunn with US English, although I haven’t managed it yet. My fixes are occasionally added to espeak ng itself, but only when reece has time to comb through them and fix any I get wrong. Is anyone interested in helping me make it possible to use these with NVDA? I don’t know where NVDA looks for espeak ng’s dictionary files, so in addition to being able to compile the files, you have to copy them to wherever it is NVDA looks for them so it can pick up on them. I’m not sure about the sapi 5 version of espeak ng, but I’d like to make it possible for people to use my fixes regardless how they use espeak ng or what they use it on, right now it’s limited strictly to Linux or unix OSes since I had help with the bash script which compiles and copies them.
Thanks
Kendell Clark

Sent from my Vizio Ultrabook




.


Re: help wanted in porting espeak fixes over to windows

Brian's Mail list account <bglists@...>
 

Was that an intended pun?
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Shaun Everiss" <@smeveriss>
To: <nvda@nvda.groups.io>
Sent: Sunday, December 31, 2017 6:45 PM
Subject: Re: [nvda] help wanted in porting espeak fixes over to windows


On that note, what would happen if you give it to espeak ng authors as a
contritution to the project, they can't bash you for doing so especially
if you maintain it yourself.




On 31/12/2017 5:18 p.m., coffeekingms@... wrote:
Hi all
I maintain a repository of espeak fixes. That is, pronunciation fixes for the US English language for words and names espeak ng mangles, for Linux based operating systems, located at http//GitHub.com/coffeeking/espeak-en-us. I’ve been wanting to for some time port these over to windows and NVDA, as well as making them available to anyone using the sapi5 version of espeak ng. I don’t have the coding skills to do this though and need help. I’ve tried to get help on the espeak ng mailing list and no one seems interested. The biggest issue is writing a script to compile the fixes into espeak ng. I don’t know enough coding to do this. The other big problem is that to be able to compile the fixes, which are just text tfiles into the binary dictionary format espeak ng needs, you have to have installed espeak ng into whatever OS you use, I don’t think you can do it with just NVDA’s built in copy. I’d love to be able to get rid of this step if at all possible, since it would drastically increase the ease of new users being able to use and contribute to my fixes. My goal is to eventually become part of espeak ng’s development itself by helping reece dunn with US English, although I haven’t managed it yet. My fixes are occasionally added to espeak ng itself, but only when reece has time to comb through them and fix any I get wrong. Is anyone interested in helping me make it possible to use these with NVDA? I don’t know where NVDA looks for espeak ng’s dictionary files, so in addition to being able to compile the files, you have to copy them to wherever it is NVDA looks for them so it can pick up on them. I’m not sure about the sapi 5 version of espeak ng, but I’d like to make it possible for people to use my fixes regardless how they use espeak ng or what they use it on, right now it’s limited strictly to Linux or unix OSes since I had help with the bash script which compiles and copies them.
Thanks
Kendell Clark

Sent from my Vizio Ultrabook


Re: help wanted in porting espeak fixes over to windows

Brian's Mail list account <bglists@...>
 

Ah the eternal paradox. Fix one problem creat two more.
I'm sure users of Skype can attest to this one and more recently Firefox of course. ahem....
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Shaun Everiss" <@smeveriss>
To: <nvda@nvda.groups.io>
Sent: Sunday, December 31, 2017 6:44 PM
Subject: Re: [nvda] help wanted in porting espeak fixes over to windows


Well it happens for all english english us, english standard uk and
whatever.

But yeah, it will be good if there is a file or something we can load in
to fix the ever growing list of espeak ng's total screwups.

They are not bad, but it suggests to me that the person who does this is
not a native language speaker of english maybe he speaks that way.

However the issue I have with espeak ng is that it screws up more and
more words as it gets better.




On 31/12/2017 5:18 p.m., coffeekingms@... wrote:
Hi all
I maintain a repository of espeak fixes. That is, pronunciation fixes for the US English language for words and names espeak ng mangles, for Linux based operating systems, located at http//GitHub.com/coffeeking/espeak-en-us. I’ve been wanting to for some time port these over to windows and NVDA, as well as making them available to anyone using the sapi5 version of espeak ng. I don’t have the coding skills to do this though and need help. I’ve tried to get help on the espeak ng mailing list and no one seems interested. The biggest issue is writing a script to compile the fixes into espeak ng. I don’t know enough coding to do this. The other big problem is that to be able to compile the fixes, which are just text tfiles into the binary dictionary format espeak ng needs, you have to have installed espeak ng into whatever OS you use, I don’t think you can do it with just NVDA’s built in copy. I’d love to be able to get rid of this step if at all possible, since it would drastically increase the ease of new users being able to use and contribute to my fixes. My goal is to eventually become part of espeak ng’s development itself by helping reece dunn with US English, although I haven’t managed it yet. My fixes are occasionally added to espeak ng itself, but only when reece has time to comb through them and fix any I get wrong. Is anyone interested in helping me make it possible to use these with NVDA? I don’t know where NVDA looks for espeak ng’s dictionary files, so in addition to being able to compile the files, you have to copy them to wherever it is NVDA looks for them so it can pick up on them. I’m not sure about the sapi 5 version of espeak ng, but I’d like to make it possible for people to use my fixes regardless how they use espeak ng or what they use it on, right now it’s limited strictly to Linux or unix OSes since I had help with the bash script which compiles and copies them.
Thanks
Kendell Clark

Sent from my Vizio Ultrabook


Re: New Year greetings

Brian's Mail list account <bglists@...>
 

Yes I heard it come in this morning our time in Newzealand via Mushroom FM so this of course means 2018 has been under beta test before we get it and of course it means I can go to bed early and ignore it totally, its already on the Earth as far as I'm concerned :-)

Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Clive Pallett" <clive.pallett@...>
To: <nvda@nvda.groups.io>
Sent: Sunday, December 31, 2017 4:52 PM
Subject: [nvda] New Year greetings


Hello everyone,

I would like to wish you all a very happy 2018.

Best wishes,

Clive Pallett


Re: I'm dissappointed

 

Sounds like we should restructure our files into modules.

Ie, profiles should be in some sort of setting files we can transfer away if we need, maybe more ini files.

We can maybe add other dictionaries and stuff to the program, I know that could make a few more broken things and space things but maybe if we could take more things away who knows.

On 31/12/2017 11:04 p.m., Sandra Pilz wrote:
Hi,

I'm a bit late but have only read the discussion now.

I have been using NVDA nearly exclusivelely since 2012 for work and also privately.

For the new job I started this year, I can only use NVDA, because JAWS will crash when I log into the web interface I am required to use.

However, I agree with Gene. JAWS is more easily configurable by the user. You can label graphics, you can assign window classes and see if that makes a program work more smoothly with NVDA, you can assign application specific hotkeys. I am not so sure if the JAWS frames feature still works so well under Windows 10. I just tried it recently without success.

Also, for me the question is not only can I do something with a screen reader, but also how quickly can I do what I need to do. One example for me is the text analysing feature of JAWS in MS Word. I think it helps a lot when writing a document and checking the formatting. I can do this with NVDA, too, but it takes a lot longer. The JAWS text analyser or whatever they call it just checks the document for me and allows me to
see where unexpected formatting or characters have been found. I then can check whether they are intended or not and make corrections. And it is so much quicker to do it that way than to read the entire document with NVDA reporting all attributes selectable in the document dialogue of NVDA. And additionally, the latter method is so monotonous that there is the risk of not catching all of the formatting problems.

I love using NVDA and think it can do a lot more than users of other screen readers may be aware of. But in a workplace setting, I might still recommend JAWS, because it is easier for people who are not programmers to adjust it so it can work with applications the way they need it to, and because tech support is available.

What would be the legal status for NVDA extensions written by a third party to make a specific program more accessible? If the would they be allowed to sell them? probably not, because NVDA is free. What would be the incentive for them to develop these extensions for rarely used software if they can only bill the hours once? With JAWS it's very clear, assistive tech companies can write scripts and sell them... That doesn't make JAWS better of course, I'm just wondering if this could be another reason why JAWS is chosen for the workplace more often than NVDA.

I think thanks to object navigation, NVDA could have a superior feature to JAWS' being able to read frames. It would be cool if we were able to specify a screen object, and then tell NVDA what we want it to do with the object: read it whenever content changes, leftclick or rightclick it and probably more. Frames in JAWS only worked if screen resolution didn't change. If the actions were tied to an object and not a frame thus not dependent on its dimensions on the screen, the configuration could work for different people with different screen resolutions.

Best

Sandra






Am 23.12.2017 um 23:52 schrieb Gene:
You can't label graphics, you can't create frames and there is no adjustment of the screen echo.  There is also no way to skip baqck and forward by line when the screen echo is set to all or when using read to end and have speech continue.  If these abilities were present, as far as I know, that would make NVDA as user configurable as JAWS and Window-eyes.  These are important lacks in NVDA.
Gene
----- Original Message -----
*From:* Adriani Botez <mailto:adriani.botez@...>
*Sent:* Saturday, December 23, 2017 2:34 PM
*To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject:* Re: [nvda] I'm dissappointed

This is not correct. NVDA is well adjustable, even much easier than jaws.



Von meinem iPhone gesendet

Am 23.12.2017 um 03:47 schrieb Gene <gsasner@... <mailto:gsasner@...>>:

You can't do what I could do when I used Pine with a shell account a long time ago.  I didn't need to create any frames or scripts.  All I had to do was set the screen echo of JAWS to all, open a message, and then use the jaws skip line wile reading feature, right shift, to very quickly jump to the start of the message body.  Even if NVDA reads such material when it appears on screen, you either listen to everything or nothing and use the tedious read by line screen review option.  Hardly a convenient or reasonable way to go through thirty e-mails.
Like it or not, NVDA isn't user definable.  You can't label graphics and you can't create frames.  These are serious deficiencies even if many of us don't need such options.
And you can't set the screen echo to all and then do what I did, as I described.  This may be an important ability for some users.
Gene
----- Original Message -----
*From:* coffeekingms@... <mailto:coffeekingms@...>
*Sent:* Friday, December 22, 2017 7:16 PM
*To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject:* Re: [nvda] I'm dissappointed

Hi

I concur. I  firmly believe that NVDA can do most, if not all, the things more expensive programs can do. With some very rare exceptions. There are still some apps that require jfw with specific scripts to be usable, but as time goes on those apps will dwindle until there are none left. But for 99 percent of people, NVDA can work for them, either alone or in combination with narrator, which has gotten quite good. I don’t really set much store by such presentations, as the few I’ve bothered to listen to gloss over the free options as if they’re not there, are not worth mentioning or aren’t good enough. This applies to NVDA as well as open source operating systems like Linux. I have not listened to the presentation people are talking about, so I don’t want to ruffle any feathers, but as a rule I don’t listen to them. They tend to unilaterally insist that only the paid apps are worth using. Except for the NVDA podcasts. Those are great, although I don’t follow those either. I’m just a user. I use NVDA on a daily basis and have found very little that it can’t do. If it can’t navigate an app by the usual methods, tab, shift tab, arrows, then it can by either touch, if you have a touch screen or object navigation.Even when I was using Linux full time I would keep up with NVDA’s progress, and NVDA is what eventually brought me back to using windows again.

Thanks

Kendell Clark

Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

------------------------------------------------------------------------

*From:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> <nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>> on behalf of Don H <lmddh50@... <mailto:lmddh50@...>>
*Sent:* Friday, December 22, 2017 6:18:54 PM
*To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject:* Re: [nvda] I'm dissappointed
I think that NVDA is just as good or better than any other screen
reader.  I think the issue for businesses is the fact that NVDA is open
source thus in their minds less secure.




Re: help wanted in porting espeak fixes over to windows

 

To be honest, and I know all the devs will shoot me down for this, but I have sceen no real reason that we shouldn't drop back to the last real version of espeak by default, have espeak ng as an optional or include both synths they have seperate directorys for data and so I see no real reason we can't have both installed, true espeak ng's espeak.dll will have to be espeakng.dll or something but to be honest.

The espeak ng screwups don't worry me that much but I do know for bidden is not fir bidden.

pir cent is not purcent.

or whatever it is.

Its almost like spaces in some words are being added when they were coded in.

At any rate, mr espeak robot is not to be understood.

Its a crappy low powered synth used for admin work and other generalness.

If I wanted my voices understood I'd use my slow good quality but resource hungry synth I have about.

Its not a big issue but the fact the list is growing.

They have fixed most of the accent issues but even so.

I really do hope that things continue to work.

On 31/12/2017 8:51 p.m., Brian's Mail list account via Groups.Io wrote:
I had always understood that the engine in nvda is updated regularly to take account of fixes, but recently there seem to have been a number of nasty bugs and silly mispronunciations added during code clean up. I'm speaking about UK English here and so have gone back to Speech Player in Espeak add on to get to an older version of Espeak which does not have these issues.
In my view there seems to be a focus in the team to attempt to make the code understandable, by moving stuff about. I guess this makes sense if they want to understand it, but its not really doing anything to fix crashes inimogees, bad pronunciations or other strange funnies, in fact its already broken language dictionaries and some other bits on the latest nvda meaning that Nvda team had to make  work around to help them use the latest code.
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: <coffeekingms@...>
To: <nvda@nvda.groups.io>
Sent: Sunday, December 31, 2017 4:18 AM
Subject: [nvda] help wanted in porting espeak fixes over to windows


Hi all
I  maintain a repository of espeak fixes. That is, pronunciation fixes for the US English language for words and names espeak ng mangles, for Linux based operating systems, located at http//GitHub.com/coffeeking/espeak-en-us. I’ve been wanting to for some time port these over to windows and NVDA, as well as making them available to anyone using the sapi5 version of espeak ng. I don’t have the coding skills to do this though and need help. I’ve tried to get help on the espeak ng mailing list and no one seems interested. The biggest issue is writing a script to compile the fixes into espeak ng. I don’t know enough coding to do this. The other big problem is that to be able to compile the fixes, which are just text tfiles into the binary dictionary format espeak ng needs, you have to have installed espeak ng into whatever OS you use, I don’t think you can do it with just NVDA’s built in copy. I’d love to be able to get rid of this step if at all possible, since it would drastically increase the ease of new users being able to use and contribute to my fixes. My goal is to eventually become part of espeak ng’s development itself by helping reece dunn with US English, although I haven’t managed it yet. My fixes are occasionally added to espeak ng itself, but only when reece has time to comb through them and fix any I get wrong. Is anyone interested in helping me make it possible to use these with NVDA? I don’t know where NVDA looks for espeak ng’s dictionary files, so in addition to being able to compile the files, you have to copy them to wherever it is NVDA looks for them so it can pick up on them. I’m not sure about the sapi 5 version of espeak ng, but I’d like to make it possible for people to use my fixes regardless how they use espeak ng or what they use it on, right now it’s limited strictly to Linux or unix OSes since I had help with the bash script which compiles and copies them.
Thanks
Kendell Clark

Sent from my Vizio Ultrabook




.


Re: help wanted in porting espeak fixes over to windows

 

On that note, what would happen if you give it to espeak ng authors as a contritution to the project, they can't bash you for doing so especially if you maintain it yourself.

On 31/12/2017 5:18 p.m., coffeekingms@... wrote:
Hi all
I maintain a repository of espeak fixes. That is, pronunciation fixes for the US English language for words and names espeak ng mangles, for Linux based operating systems, located at http//GitHub.com/coffeeking/espeak-en-us. I’ve been wanting to for some time port these over to windows and NVDA, as well as making them available to anyone using the sapi5 version of espeak ng. I don’t have the coding skills to do this though and need help. I’ve tried to get help on the espeak ng mailing list and no one seems interested. The biggest issue is writing a script to compile the fixes into espeak ng. I don’t know enough coding to do this. The other big problem is that to be able to compile the fixes, which are just text tfiles into the binary dictionary format espeak ng needs, you have to have installed espeak ng into whatever OS you use, I don’t think you can do it with just NVDA’s built in copy. I’d love to be able to get rid of this step if at all possible, since it would drastically increase the ease of new users being able to use and contribute to my fixes. My goal is to eventually become part of espeak ng’s development itself by helping reece dunn with US English, although I haven’t managed it yet. My fixes are occasionally added to espeak ng itself, but only when reece has time to comb through them and fix any I get wrong. Is anyone interested in helping me make it possible to use these with NVDA? I don’t know where NVDA looks for espeak ng’s dictionary files, so in addition to being able to compile the files, you have to copy them to wherever it is NVDA looks for them so it can pick up on them. I’m not sure about the sapi 5 version of espeak ng, but I’d like to make it possible for people to use my fixes regardless how they use espeak ng or what they use it on, right now it’s limited strictly to Linux or unix OSes since I had help with the bash script which compiles and copies them.
Thanks
Kendell Clark

Sent from my Vizio Ultrabook


Re: help wanted in porting espeak fixes over to windows

 

Well it happens for all english english us, english standard uk and whatever.

But yeah, it will be good if there is a file or something we can load in to fix the ever growing list of espeak ng's total screwups.

They are not bad, but it suggests to me that the person who does this is not a native language speaker of english maybe he speaks that way.

However the issue I have with espeak ng is that it screws up more and more words as it gets better.

On 31/12/2017 5:18 p.m., coffeekingms@... wrote:
Hi all
I maintain a repository of espeak fixes. That is, pronunciation fixes for the US English language for words and names espeak ng mangles, for Linux based operating systems, located at http//GitHub.com/coffeeking/espeak-en-us. I’ve been wanting to for some time port these over to windows and NVDA, as well as making them available to anyone using the sapi5 version of espeak ng. I don’t have the coding skills to do this though and need help. I’ve tried to get help on the espeak ng mailing list and no one seems interested. The biggest issue is writing a script to compile the fixes into espeak ng. I don’t know enough coding to do this. The other big problem is that to be able to compile the fixes, which are just text tfiles into the binary dictionary format espeak ng needs, you have to have installed espeak ng into whatever OS you use, I don’t think you can do it with just NVDA’s built in copy. I’d love to be able to get rid of this step if at all possible, since it would drastically increase the ease of new users being able to use and contribute to my fixes. My goal is to eventually become part of espeak ng’s development itself by helping reece dunn with US English, although I haven’t managed it yet. My fixes are occasionally added to espeak ng itself, but only when reece has time to comb through them and fix any I get wrong. Is anyone interested in helping me make it possible to use these with NVDA? I don’t know where NVDA looks for espeak ng’s dictionary files, so in addition to being able to compile the files, you have to copy them to wherever it is NVDA looks for them so it can pick up on them. I’m not sure about the sapi 5 version of espeak ng, but I’d like to make it possible for people to use my fixes regardless how they use espeak ng or what they use it on, right now it’s limited strictly to Linux or unix OSes since I had help with the bash script which compiles and copies them.
Thanks
Kendell Clark

Sent from my Vizio Ultrabook


New Year greetings

Clive Pallett
 

Hello everyone,
 
I would like to wish you all a very happy 2018.
 
Best wishes,
 
Clive Pallett
 
 


Re: Using Win10's Mail App

Robert Mendoza
 

Hi, David


Thanks for the feedback. One thing more I noticed I am using the latest master snapshot of nvda, then, when I am about to enter my password I could not hear echoing as I typed into the field though my keys were set echo on in the settings. Is this should be normal for not hearing to announce when typing? Or, did I missed out some thing to get it work. But, when I shifted to used narrator I have no problem I could hear the focus as I tabbed around in the password panel.


Robert Mendoza
On 12/31/2017 9:28 PM, David Griffith wrote:

For me Windows Mail loads faster than any other   mail app though I do have 4 times the ram at 16GB which may make   a difference.

Normally I  use NVDA with Mail.  I am doing so at  the moment. One thing I do notice is that Mail may lock up with NVDA if there is anything processor intensive happening in the background. If I switch temprorarily to Narrator whilst this is happening   mail suddenly comes back to life.

It may be worth trying mail with Narrator if it  is unresponsive with NVDA as they works quite nicely together.

David Griffith

My Blind Access and Guide dog Blog
http://dgriffithblog.wordpress.com/
My Blind hammer Blog
https://www.westhamtillidie.com/authors/blind-hammer/posts

 

From: Robert Mendoza
Sent: 30 December 2017 13:25
To: nvda@nvda.groups.io
Subject: Re: [nvda] Using Win10's Mail App

 

Out of curiosity I tested awhile ago for the first time the Mail apps to

my Windows 10 machine, I noticed when opening the mentioned apps took me

so long to loads or open. Though, I never had experience this to other

third-party applications like Thunderbird, and etc. Or, is this really

normal as it was supposed to be?Again, this happen although none

application is running in the background. I am currently using a Dual

Core processor 5th generation with 4GB RAM. Not sure what exactly could

cause of this. I appreciate your advice. Thanks.

 

 

Robert Mendoza

 

On 12/30/2017 10:39 AM, Rosemarie Chavarria wrote:

> Hi, Pauline,

> David Moore has a great tutorial on how to use the mail app. It also covers the calendar and the people app.

> Hope this helps.

> Rosemarie

> -----Original Message-----

> From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Pauline Smith

> Sent: Friday, December 29, 2017 5:44 PM

> To: nvda@nvda.groups.io

> Subject: [nvda] Using Win10's Mail App

> Good Evening,

> Are any instructions for using Win10's Mail app with NVDA?  Thanks and an early wish for a happy new year.

> Pauline

>

 

 

 

 



Re: I'm dissappointed

Sandra Pilz
 

Hi,

I'm a bit late but have only read the discussion now.

I have been using NVDA nearly exclusivelely since 2012 for work and also privately.

For the new job I started this year, I can only use NVDA, because JAWS will crash when I log into the web interface I am required to use.

However, I agree with Gene. JAWS is more easily configurable by the user. You can label graphics, you can assign window classes and see if that makes a program work more smoothly with NVDA, you can assign application specific hotkeys. I am not so sure if the JAWS frames feature still works so well under Windows 10. I just tried it recently without success.

Also, for me the question is not only can I do something with a screen reader, but also how quickly can I do what I need to do. One example for me is the text analysing feature of JAWS in MS Word. I think it helps a lot when writing a document and checking the formatting. I can do this with NVDA, too, but it takes a lot longer. The JAWS text analyser or whatever they call it just checks the document for me and allows me to
see where unexpected formatting or characters have been found. I then can check whether they are intended or not and make corrections. And it is so much quicker to do it that way than to read the entire document with NVDA reporting all attributes selectable in the document dialogue of NVDA. And additionally, the latter method is so monotonous that there is the risk of not catching all of the formatting problems.

I love using NVDA and think it can do a lot more than users of other screen readers may be aware of. But in a workplace setting, I might still recommend JAWS, because it is easier for people who are not programmers to adjust it so it can work with applications the way they need it to, and because tech support is available.

What would be the legal status for NVDA extensions written by a third party to make a specific program more accessible? If the would they be allowed to sell them? probably not, because NVDA is free. What would be the incentive for them to develop these extensions for rarely used software if they can only bill the hours once? With JAWS it's very clear, assistive tech companies can write scripts and sell them... That doesn't make JAWS better of course, I'm just wondering if this could be another reason why JAWS is chosen for the workplace more often than NVDA.

I think thanks to object navigation, NVDA could have a superior feature to JAWS' being able to read frames. It would be cool if we were able to specify a screen object, and then tell NVDA what we want it to do with the object: read it whenever content changes, leftclick or rightclick it and probably more. Frames in JAWS only worked if screen resolution didn't change. If the actions were tied to an object and not a frame thus not dependent on its dimensions on the screen, the configuration could work for different people with different screen resolutions.

Best

Sandra






Am 23.12.2017 um 23:52 schrieb Gene:

You can't label graphics, you can't create frames and there is no adjustment of the screen echo.  There is also no way to skip baqck and forward by line when the screen echo is set to all or when using read to end and have speech continue.  If these abilities were present, as far as I know, that would make NVDA as user configurable as JAWS and Window-eyes.  These are important lacks in NVDA.
 
Gene 
----- Original Message -----
Sent: Saturday, December 23, 2017 2:34 PM
Subject: Re: [nvda] I'm dissappointed

This is not correct. NVDA is well adjustable, even much easier than jaws.



Von meinem iPhone gesendet

Am 23.12.2017 um 03:47 schrieb Gene <gsasner@...>:

You can't do what I could do when I used Pine with a shell account a long time ago.  I didn't need to create any frames or scripts.  All I had to do was set the screen echo of JAWS to all, open a message, and then use the jaws skip line wile reading feature, right shift, to very quickly jump to the start of the message body.  Even if NVDA reads such material when it appears on screen, you either listen to everything or nothing and use the tedious read by line screen review option.  Hardly a convenient or reasonable way to go through thirty e-mails. 
 
Like it or not, NVDA isn't user definable.  You can't label graphics and you can't create frames.  These are serious deficiencies even if many of us don't need such options.
 
And you can't set the screen echo to all and then do what I did, as I described.  This may be an important ability for some users.
Gene
----- Original Message -----
Sent: Friday, December 22, 2017 7:16 PM
Subject: Re: [nvda] I'm dissappointed

Hi

I concur. I  firmly believe that NVDA can do most, if not all, the things more expensive programs can do. With some very rare exceptions. There are still some apps that require jfw with specific scripts to be usable, but as time goes on those apps will dwindle until there are none left. But for 99 percent of people, NVDA can work for them, either alone or in combination with narrator, which has gotten quite good. I don’t really set much store by such presentations, as the few I’ve bothered to listen to gloss over the free options as if they’re not there, are not worth mentioning or aren’t good enough. This applies to NVDA as well as open source operating systems like Linux. I have not listened to the presentation people are talking about, so I don’t want to ruffle any feathers, but as a rule I don’t listen to them. They tend to unilaterally insist that only the paid apps are worth using. Except for the NVDA podcasts. Those are great, although I don’t follow those either. I’m just a user. I use NVDA on a daily basis and have found very little that it can’t do. If it can’t navigate an app by the usual methods, tab, shift tab, arrows, then it can by either touch, if you have a touch screen or object navigation.Even when I was using Linux full time I would keep up with NVDA’s progress, and NVDA is what eventually brought me back to using windows again.

Thanks

Kendell Clark

 

Sent from Mail for Windows 10

 


From: nvda@nvda.groups.io <nvda@nvda.groups.io> on behalf of Don H <lmddh50@...>
Sent: Friday, December 22, 2017 6:18:54 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] I'm dissappointed
 
I think that NVDA is just as good or better than any other screen
reader.  I think the issue for businesses is the fact that NVDA is open
source thus in their minds less secure.






Re: Using Win10's Mail App

David Griffith
 

For me Windows Mail loads faster than any other   mail app though I do have 4 times the ram at 16GB which may make   a difference.

Normally I  use NVDA with Mail.  I am doing so at  the moment. One thing I do notice is that Mail may lock up with NVDA if there is anything processor intensive happening in the background. If I switch temprorarily to Narrator whilst this is happening   mail suddenly comes back to life.

It may be worth trying mail with Narrator if it  is unresponsive with NVDA as they works quite nicely together.

David Griffith

My Blind Access and Guide dog Blog
http://dgriffithblog.wordpress.com/
My Blind hammer Blog
https://www.westhamtillidie.com/authors/blind-hammer/posts

 

From: Robert Mendoza
Sent: 30 December 2017 13:25
To: nvda@nvda.groups.io
Subject: Re: [nvda] Using Win10's Mail App

 

Out of curiosity I tested awhile ago for the first time the Mail apps to

my Windows 10 machine, I noticed when opening the mentioned apps took me

so long to loads or open. Though, I never had experience this to other

third-party applications like Thunderbird, and etc. Or, is this really

normal as it was supposed to be?Again, this happen although none

application is running in the background. I am currently using a Dual

Core processor 5th generation with 4GB RAM. Not sure what exactly could

cause of this. I appreciate your advice. Thanks.

 

 

Robert Mendoza

 

On 12/30/2017 10:39 AM, Rosemarie Chavarria wrote:

> Hi, Pauline,

> David Moore has a great tutorial on how to use the mail app. It also covers the calendar and the people app.

> Hope this helps.

> Rosemarie

> -----Original Message-----

> From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Pauline Smith

> Sent: Friday, December 29, 2017 5:44 PM

> To: nvda@nvda.groups.io

> Subject: [nvda] Using Win10's Mail App

> Good Evening,

> Are any instructions for using Win10's Mail app with NVDA?  Thanks and an early wish for a happy new year.

> Pauline

>

 

 

 

 


Re: trying to find the tutorial for ripping CD's using NVDA

Arno Schuh
 

Windows Media Player uses its own database to fetch the CD info. That's different to FreeCDB, Music Brains or CDText. So WMP for me is an alternate source when CDEX and iTunes (still uses the GraceNote DB) didn't come back with a result.

Arno

Am Sonntag, 31. Dezember 2017 08:43 schrieb Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io>:

Is there a reason why you want to use Windows Media player? I use
CD-EX for this task. its made for it in fact.
Its also free!
No messing about, just get your wav or mp 3 files and it even seems
to be able to use cddb and cd text to get info too.
Brian


Re: help wanted in porting espeak fixes over to windows

John Isige
 

You shouldn't actually need any help, except figuring out where NVDA
places dictionary files. Install this on Windows, assuming you're using
Windows 10 of course.


https://docs.microsoft.com/en-us/windows/wsl/install-win10


You should, after installing any utilities you need, be able to use your
bash scripts at that point. Alternatively, if you're not on 10, consider
Cygwin. The real question though is, why do you need to do this on
Windows? eSpeak is cross-platform, no? Shouldn't you just be able to
produce compiled dictionaries on linux, and dump them in the appropriate
place in whatever eSpeak installation is running on an OS?

On 12/30/2017 22:18, coffeekingms@... wrote:

Hi all

I maintain a repository of espeak fixes. That is, pronunciation fixes
for the US English language for words and names espeak ng mangles, for
Linux based operating systems, located at
http//GitHub.com/coffeeking/espeak-en-us. I’ve been wanting to for
some time port these over to windows and NVDA, as well as making them
available to anyone using the sapi5 version of espeak ng. I don’t have
the coding skills to do this though and need help. I’ve tried to get
help on the espeak ng mailing list and no one seems interested. The
biggest issue is writing a script to compile the fixes into espeak ng.
I don’t know enough coding to do this. The other big problem is that
to be able to compile the fixes, which are just text tfiles into the
binary dictionary format espeak ng needs, you have to have installed
espeak ng into whatever OS you use, I don’t think you can do it with
just NVDA’s built in copy. I’d love to be able to get rid of this step
if at all possible, since it would drastically increase the ease of
new users being able to use and contribute to my fixes. My goal is to
eventually become part of espeak ng’s development itself by helping
reece dunn with US English, although I haven’t managed it yet. My
fixes are occasionally added to espeak ng itself, but only when reece
has time to comb through them and fix any I get wrong. Is anyone
interested in helping me make it possible to use these with NVDA? I
don’t know where NVDA looks for espeak ng’s dictionary files, so in
addition to being able to compile the files, you have to copy them to
wherever it is NVDA looks for them so it can pick up on them. I’m not
sure about the sapi 5 version of espeak ng, but I’d like to make it
possible for people to use my fixes regardless how they use espeak ng
or what they use it on, right now it’s limited strictly to Linux or
unix OSes since I had help with the bash script which compiles and
copies them.

Thanks

Kendell Clark

Sent from my Vizio Ultrabook