Date   

Re: Observations with ETI eloquence add on.

Robert Doc Wright godfearer
 

Try this open Eloquence and uncheck everything that you have checked. Then press ctrl+insert+v, tab twice, make sure it is pointing to ETI Eloquence and go through  and set all your other changes.

 

******

If we can't look at ourselves, and ask, why?  then where does the learning start?

 

From: Sue J. Ward
Sent: Wednesday, February 12, 2020 12:02 PM
To: nvda groups
Subject: [nvda] Observations with ETI eloquence add on.

 

  Hello am noticing some things when I did update to the latest ETI

Eloquence add on that works with NVDA 2019.3. Sometimes whenever am I

reading something on a webpage or tabbing through folders in Thunderbird

the add on will stop working and when ever that happens I have to

restart NVDA. It has happened to me for the past week and at least seven

times a day it is driving me crazy. I don't know who is behind this but

it could use some help in getting stuff straightened out. I also noticed

whenever I raise the pitch to a percentage in the speech settings it

does not do anything when I come a across a capital letter it does not

do that. I also noticed in the Sapi 5 eloquence driver as well. In the

old add on I did not notice anything like this. I am not a developer am

just an average home user so if anyone has a  email address so I can

contact who works on the add on maybe I could contact them and let them

know what I am noticing. Thank you.

____________________________________________________________

1 Simple Trick Removes Eye Bags and Lip Lines in Seconds

bevhillsmd.com

http://thirdpartyoffers.juno.com/TGL3131/5e444aec116064aeb66dest01vuc

 

 

 


Observations with ETI eloquence add on.

Sue J. Ward
 

Hello am noticing some things when I did update to the latest ETI Eloquence add on that works with NVDA 2019.3. Sometimes whenever am I reading something on a webpage or tabbing through folders in Thunderbird the add on will stop working and when ever that happens I have to restart NVDA. It has happened to me for the past week and at least seven times a day it is driving me crazy. I don't know who is behind this but it could use some help in getting stuff straightened out. I also noticed whenever I raise the pitch to a percentage in the speech settings it does not do anything when I come a across a capital letter it does not do that. I also noticed in the Sapi 5 eloquence driver as well. In the old add on I did not notice anything like this. I am not a developer am just an average home user so if anyone has a email address so I can contact who works on the add on maybe I could contact them and let them know what I am noticing. Thank you.
____________________________________________________________
1 Simple Trick Removes Eye Bags and Lip Lines in Seconds
bevhillsmd.com
http://thirdpartyoffers.juno.com/TGL3131/5e444aec116064aeb66dest01vuc


Re: how to disable announcing of battery charging/not charging

Samuel Kacer
 

Thanks to you all for the suggestions.

@Tyler Spivey  Your trick works and is exactly the thing I was looking for.

To the others, I appreciate the suggestions for checking what the problem with the battery was, even though that's not what I was looking for, but it is appreciated none the less.

Today the mysterious battery problems stopped, mysteriously. Yesterday while this was going on, storm Ciara was raging outside, so maybe it was affecting the electric lines in some way and that's what was causing the faulty behaviour.

On Wed, Feb 12, 2020 at 1:48 AM Quentin Christensen <quentin@...> wrote:
I'd concur with wanting to get to the root cause - stopping NVDA reporting whether the battery is charging or not will only silence the symptom, not fix the problem.

Check your battery, cable, transformer and power point.  Make sure everything is connected tightly etc - if you can replace any one of those things conveniently, that can at least rule that item out (eg I expect you should be able to plug it into a different power point to see if it keeps happening, which will at least confirm the powerpoint is ok).

On Wed, Feb 12, 2020 at 7:49 AM Tyler Spivey <tspivey@...> wrote:

Pop into the python console and paste this in, pressing enter after:


import winKernel;winKernel.GetSystemPowerStatus = lambda x: None


The worst that will happen is that NVDA will break, requiring a restart. No big deal.


On 2/11/2020 12:32 PM, Samuel Kacer wrote:
Hello,

my laptop seems to be going a bit haywire. Every couple seconds the battery goes from charging to not charging and back again. NVDA announcing this each time is extremely annoying.

I tried checking NVDA settings, but couldn't find anything. Is it possible to disable NVDA automatically announcing when battery starts/stops charging?

Much appreciated,
Sam



--
Quentin Christensen
Training and Support Manager



Re: A solution for read subtitles with NVDA, the program Pot Player

yunus Emre
 

Hello, i am watching things with subtitles for a year or longer. If anyone needs any help about potplayer I'd like to help.
I tried to tell to developer make able us to read two subtitles at the sametimes but he's ignoring that sadly.


Re: Remote 2.3 released.

Gene
 

Modern doesn't mean now in that context.  it means writing with certain characteristics, thhough they may vary, but Stravinsky would be considered modern and Rite of Spring was composed early in the Twentieth Century. 
 
Modern literature would refer to a good deal of writing in the Twentieth century. 
 
In the context of computer programs, which is a different context with different usage, modern NVDA implies that older versions are far behind the times and inferior.  Not necessarily, depending on how the user uses the version or versions . 
 
I still use a quite old version of NVDA because I don't need a newer one with the programs and Windows versions I use and it does certain things more smoothly, such as how it works with my e-mail program.  I don't consider it not to be modern.  It is an old version, which has very different connotations. 
 
Gene

----- Original Message ------
Sent: Wednesday, February 12, 2020 11:37 AM
Subject: Re: [nvda] Remote 2.3 released.

I like modern better. Youhave modden classical music not current classical music for example, moddern meaning, in this case, now.

Take care

Sarah Alawami, owner of TFFP. . For more info go to our website. This is also our libsyn page as well.

to subscribe to the feed click here

Our telegram channel is also a good place for an announce only in regard to podcasts, contests, etc.

Our discord is where you will know when we go live on [twitch.](twitch.tv/ke7zum] Feel free to give the channel a follow and see what is up there.

Finally, to become a patron and help support the podcast go here

On 12 Feb 2020, at 9:12, Joseph Lee wrote:

Hi,
"Current" makes more sense... at least for now. There will come a time when we will update to a newer Python 3.x release, and that'll change what "current" means by then.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io nvda@nvda.groups.io On Behalf Of Cordelia Scharpf
Sent: Wednesday, February 12, 2020 9:08 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Remote 2.3 released.

Hi,
I see where "modern" comes from, but wonder whether "current" might be more appropriate. "Modern" being preciously relative, "current" reflects the present, i.e., here and now.
Cordelia

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Wednesday, February 12, 2020 5:58 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Remote 2.3 released.

Hi,
That's an interesting point. I think part of the reason for labeling it that way is due to Python 2 versus Python 3 - the former is ancient now, and the latter is modern.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io nvda@nvda.groups.io On Behalf Of Steve Matzura
Sent: Wednesday, February 12, 2020 8:47 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Remote 2.3 released.

I'm not thrilled that this add-on is said to work with "modern" NVDA, as some folks think 2019.2.1 is pretty modern already. Why can't that page just say 2019.3 and above, and be done with it?

On 2/11/2020 3:53 PM, Robert Kingett wrote:

They just tweeted this out. This new version will work with the new
NVDA. Below is the download page.

https://nvdaremote.com/download/


Re: Remote 2.3 released.

Sarah k Alawami
 

I like modern better. Youhave modden classical music not current classical music for example, moddern meaning, in this case, now.

Take care

Sarah Alawami, owner of TFFP. . For more info go to our website. This is also our libsyn page as well.

to subscribe to the feed click here

Our telegram channel is also a good place for an announce only in regard to podcasts, contests, etc.

Our discord is where you will know when we go live on [twitch.](twitch.tv/ke7zum] Feel free to give the channel a follow and see what is up there.

Finally, to become a patron and help support the podcast go here

On 12 Feb 2020, at 9:12, Joseph Lee wrote:

Hi,
"Current" makes more sense... at least for now. There will come a time when we will update to a newer Python 3.x release, and that'll change what "current" means by then.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io nvda@nvda.groups.io On Behalf Of Cordelia Scharpf
Sent: Wednesday, February 12, 2020 9:08 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Remote 2.3 released.

Hi,
I see where "modern" comes from, but wonder whether "current" might be more appropriate. "Modern" being preciously relative, "current" reflects the present, i.e., here and now.
Cordelia

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Wednesday, February 12, 2020 5:58 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Remote 2.3 released.

Hi,
That's an interesting point. I think part of the reason for labeling it that way is due to Python 2 versus Python 3 - the former is ancient now, and the latter is modern.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io nvda@nvda.groups.io On Behalf Of Steve Matzura
Sent: Wednesday, February 12, 2020 8:47 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Remote 2.3 released.

I'm not thrilled that this add-on is said to work with "modern" NVDA, as some folks think 2019.2.1 is pretty modern already. Why can't that page just say 2019.3 and above, and be done with it?

On 2/11/2020 3:53 PM, Robert Kingett wrote:

They just tweeted this out. This new version will work with the new
NVDA. Below is the download page.

https://nvdaremote.com/download/


Re: NVDA 2019.3.1 and Chrome 80

Clarissa Mitchell
 

Arrow keys don't work for me. Or when they do, it says "not checked"
like I didn't even check the box. I thought the problem might be with
my keyboard, so I put new batteries in it. But the problem persists.
Now I know I'm not the only one with this issue. Sometimes my tab key
doesn't work, and sometimes I can't even get the page in NVDA's focus,
and pressing F6 only cycles through address bar and tab control. It
doesn't bring me back to the full page. After I restart NVDA, it
works. Something weird is definitely going on here.



On 2/11/20, Sarah k Alawami <marrie12@gmail.com> wrote:
Tryu up and down arrowing to get the button to click. I have had this
problem with 19.2 and any web page like interface now for months.

Take care

Sarah Alawami, owner of TFFP. . For more info go to our
[website.](http://www.tffppodcast.com) This is also our libsyn page as
well.

to subscribe to the feed click [here](http://feeds.feedburner.com/tffp)

Our [telegram](https://t.me/tffppodcast) channel is also a good place
for an announce only in regard to podcasts, contests, etc.

Our [discord](https://discord.gg/dfr7MaVK) is where you will know when
we go live on [twitch.](twitch.tv/ke7zum] Feel free to give the channel
a follow and see what is up there.


Finally, to become a patron and help support the podcast go
[here](Http://patreon.com/tffppodcast)

On 11 Feb 2020, at 15:17, Clarissa Mitchell wrote:

I am having the following issue with the new NVDA update and the
latest update to the Chrome browser. If I'm filling out a long form
that has several pages, a survey for instance, I try to check a box or
a radio button, and NVDA will not say "checked". It acts like nothing
happened. And if I press the "next" button, it seems like nothing
happens. If I go to the NVDA menu or restart NVDA, and go back to the
browser window, the refreshed page will display. I've had to restart
NVDA countless times just for one survey. What could be causing this,
and is anyone else having this issue with Chrome? It seems to work
fine on Firefox.

Google Chrome Version: 80.0.3987.100
NVDA version: 2019.3.1

Thanks.



I tried insert+space, and that didn't do the trick either.


Re: Remote 2.3 released.

 

Hi,
"Current" makes more sense... at least for now. There will come a time when we will update to a newer Python 3.x release, and that'll change what "current" means by then.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Cordelia Scharpf
Sent: Wednesday, February 12, 2020 9:08 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Remote 2.3 released.

Hi,
I see where "modern" comes from, but wonder whether "current" might be more appropriate. "Modern" being preciously relative, "current" reflects the present, i.e., here and now.
Cordelia

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Wednesday, February 12, 2020 5:58 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Remote 2.3 released.

Hi,
That's an interesting point. I think part of the reason for labeling it that way is due to Python 2 versus Python 3 - the former is ancient now, and the latter is modern.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Steve Matzura
Sent: Wednesday, February 12, 2020 8:47 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Remote 2.3 released.

I'm not thrilled that this add-on is said to work with "modern" NVDA, as some folks think 2019.2.1 is pretty modern already. Why can't that page just say 2019.3 and above, and be done with it?


On 2/11/2020 3:53 PM, Robert Kingett wrote:

They just tweeted this out. This new version will work with the new
NVDA. Below is the download page.

https://nvdaremote.com/download/


Re: Remote 2.3 released.

Cordelia Scharpf
 

Hi,
I see where "modern" comes from, but wonder whether "current" might be more appropriate. "Modern" being preciously relative, "current" reflects the present, i.e., here and now.
Cordelia

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Wednesday, February 12, 2020 5:58 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Remote 2.3 released.

Hi,
That's an interesting point. I think part of the reason for labeling it that way is due to Python 2 versus Python 3 - the former is ancient now, and the latter is modern.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Steve Matzura
Sent: Wednesday, February 12, 2020 8:47 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Remote 2.3 released.

I'm not thrilled that this add-on is said to work with "modern" NVDA, as some folks think 2019.2.1 is pretty modern already. Why can't that page just say 2019.3 and above, and be done with it?


On 2/11/2020 3:53 PM, Robert Kingett wrote:

They just tweeted this out. This new version will work with the new
NVDA. Below is the download page.

https://nvdaremote.com/download/


Re: Remote 2.3 released.

 

Hi,
That's an interesting point. I think part of the reason for labeling it that way is due to Python 2 versus Python 3 - the former is ancient now, and the latter is modern.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Steve Matzura
Sent: Wednesday, February 12, 2020 8:47 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Remote 2.3 released.

I'm not thrilled that this add-on is said to work with "modern" NVDA, as some folks think 2019.2.1 is pretty modern already. Why can't that page just say 2019.3 and above, and be done with it?


On 2/11/2020 3:53 PM, Robert Kingett wrote:

They just tweeted this out. This new version will work with the new
NVDA. Below is the download page.

https://nvdaremote.com/download/


Re: special characters and punctuation feedback while typing in v2019.3.1

Gene
 

I don't know how special characters were handled previously, I don't use them.  But the suggestion sounds like a very good one. 
 
Aside from that, I think that how certain default behaviors are reached would be a good topic for discussion.  At times, I think it would be a good idea to place certain proposed behaviors before a panel of users or on a list like this as advisory.
 
Gene

----- Original Message -----
Sent: Wednesday, February 12, 2020 6:41 AM
Subject: Re: [nvda] special characters and punctuation feedback while typing in v2019.3.1

Hi,


as I tryed to state, I want typed characters set to off! :-)

But still one has to get feedback on typed characters in word mode - they cannot be ignored, they have to be spoken as words then.

If someone wants spoken words feedback, it does not mean, that he does not care about which characters he typed ;-) ...as this smiley for example. I now did not hear if it was typed or not. I also do not get feedback about the "," and "." ...this is defenitely not how someone can write, even in speak-words mode.


I will restart the computer, but would be very surprised if that changes something ...

cheers

Martin


Am 12.02.2020 um 12:43 schrieb Quentin Christensen:
Hi Martin,

Have you restarted the computer since you updated NVDA?  I just tried type a. with speak typed characters on, and NVDA read "A dot" just as you expected.  I don't have Eloquence, but it worked the same with eSpeak and with Windows OneCore voices.

Occasionally you get random bugs (such as this) after installing or updating the software but before restarting the computer.  Restarting the computer shuts everything down and loads again from scratch so usually fixes up these random on-off issues.

Also double check that you have speak typed characters on as well :)

Kind regards

Quentin.

On Wed, Feb 12, 2020 at 10:00 PM Martin Thomas Swaton <list@...> wrote:
Hi,


I searched for this problem, but could not find a topic on it ... so if
this already was asked, I am sorry...


Since the update the feedback of special characters and punctuation
while typing has changed when you set the feedback to "words" and
disable "characters".


normally special characters and punctuation was spoken emedeately on
their keypress together with any other characters, that have been typed
before.


example of old behaviour:

type: a.

feedback: a dot


new behavour:

type: a.

feedback: a


this is very problematic as you now do not get any feedback on typed
special characters and punctuation. Try to type a smiley, you won't hear
it. just silence.


Tried that with eloquence and espeak. So the speech/voice does not matter.


Hope this can be fixed

and additionally I would suggest to add a option/choice to choose wether
special characters (and numbers) should be spoken emedeately on their
keypress or together with other characters as whole words. So users
could decide, which they prefer, as there where discussions in the past
about that.


but right now it would be important to get back any feedback for theese
special characters and punctuation.


cheers

Martin








--
Quentin Christensen
Training and Support Manager



Re: Remote 2.3 released.

Steve Matzura
 

I'm not thrilled that this add-on is said to work with "modern" NVDA, as some folks think 2019.2.1 is pretty modern already. Why can't that page just say 2019.3 and above, and be done with it?

On 2/11/2020 3:53 PM, Robert Kingett wrote:

They just tweeted this out. This new version will work with the new NVDA. Below is the download page.

https://nvdaremote.com/download/


Re: special characters and punctuation feedback while typing in v2019.3.1

Gene
 

I would imagine there is a setting to change this behavior but it is another example of a very poor choice for the default being chosen.  Are such choices reviewed by a panel of users or perhaps sent to a list like this?  How are such choices made?  At times defaults are chosen that I consider very poor.
 
Gene
----- Original Message -----

Sent: Wednesday, February 12, 2020 5:00 AM
Subject: [nvda] special characters and punctuation feedback while typing in v2019.3.1

Hi,


I searched for this problem, but could not find a topic on it ... so if
this already was asked, I am sorry...


Since the update the feedback of special characters and punctuation
while typing has changed when you set the feedback to "words" and
disable "characters".


normally special characters and punctuation was spoken emedeately on
their keypress together with any other characters, that have been typed
before.


example of old behaviour:

type: a.

feedback: a dot


new behavour:

type: a.

feedback: a


this is very problematic as you now do not get any feedback on typed
special characters and punctuation. Try to type a smiley, you won't hear
it. just silence.


Tried that with eloquence and espeak. So the speech/voice does not matter.


Hope this can be fixed

and additionally I would suggest to add a option/choice to choose wether
special characters (and numbers) should be spoken emedeately on their
keypress or together with other characters as whole words. So users
could decide, which they prefer, as there where discussions in the past
about that.


but right now it would be important to get back any feedback for theese
special characters and punctuation.


cheers

Martin






Re: java access bridge doesn't work in nvda anymore

Kara Goldfinch
 

Michael,
Java Access Bridge is included with NVDA as of the latest version.


On 12 Feb 2020, at 04:36, Michael Maslo <michaelmaslo04@...> wrote:



I am new to nVda and was wondering where I would get Java access Bridge From? Also I have seen a application like this before in the office I work at.I was wondering the Purpose of this application?

Any help would be appreciated.                                                             

Sincerely,

Michael maslo

On Feb 11, 2020, at 19:59, Quentin Christensen <quentin@...> wrote:


What is the Java program you are using which doesn't work?  Have you got a link to its website please?

Also have you restarted your computer since updating NVDA?  (It's worth doing that just because sometimes random things can misbehave in that time between updating software and restarting the PC).

Kind regards

Quentin.

On Wed, Feb 12, 2020 at 12:27 PM heike67 <heikesb1967@...> wrote:
hello
i have installed version 2019.3 and in >what's new in nvda< i can read that java access bridge is accessible now for nvda. i started an application that needs java to see if there are changes, it doesn't recognized anymore and java access bridge wasn't deactivated in ease of access center. some hours before it has still worked. can someone please help?
sorry if my english is not perfect.



--
Quentin Christensen
Training and Support Manager



Re: nvda 2019.3 vocalizer, and remote support

nutkittirat@...
 

Hello Rui, thank you for your help. But today before I receive your reply, I have reset my laptop because I'm not sure what the problem is. Then I just install NVDA 2019.2.1 and Vocalizer Expressive driver 3.0.14 and I can activate my license again. But to do so I have lost my 1 activation, would you recover it for me please?
Thank you

note: After then I try to upgrade both NVDA and the driver to the latest version but I got the no speech issue too. So I just downgrade to 2019.2.1 and it's work again.


Re: special characters and punctuation feedback while typing in v2019.3.1

Ralf Kefferpuetz
 

Martin,

I just checked it again with 2019.2.1. I have the same symptoms there as you describe in 2019.3.1

Please do me a favour and go to your 2019.2.1 installation and press NVDA-Q and restart NVDA with addons disabled and give it a try. If you then see the misbehaviour you got an addon loaded under 2019.2.1 which does what you want.

 

Regards,

  Ralf

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Martin Thomas Swaton
Sent: Mittwoch, 12. Februar 2020 15:36
To: nvda@nvda.groups.io
Subject: Re: [nvda] special characters and punctuation feedback while typing in v2019.3.1

 

Hello,

 

as anounced I looked up the version of NVDA where it last worked correctly:

nvda v2019.2.1 gives the feedback as expected.

a "." is spoken emedeately. Other "words" are spoken on space or at the keypress of such special characters.

In V2019.3.1 special characters still trigger speaking of words, but are not spoken themselves.

 

This should be fixed as soon as possible as typing in word mode is no longer manageable.

 

cheers

Martin

 

Am 12.02.2020 um 13:50 schrieb Martin Thomas Swaton:

Hi again,

 

the reboot did not change anything - as expected.

 

@Ralf I had 2019.2 (do not know which one exactly) installed on this computer (and still have it on my notebook) and there it works as expected.

   when I get back home, I can look at the version of nvda where it worked last.

 

cheers

Martin

 

 

 

Am 12.02.2020 um 13:04 schrieb Ralf Kefferpuetz:

Hi Quentin,

I understood Martin that he discovers that with typed chars off and typed words on. And that can beconfirmed at my end, but it was the same under 2019.2.1

 

Cheers,

  Ralf

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen
Sent: Mittwoch, 12. Februar 2020 12:43
To: nvda@nvda.groups.io
Subject: Re: [nvda] special characters and punctuation feedback while typing in v2019.3.1

 

Hi Martin,

 

Have you restarted the computer since you updated NVDA?  I just tried type a. with speak typed characters on, and NVDA read "A dot" just as you expected.  I don't have Eloquence, but it worked the same with eSpeak and with Windows OneCore voices.

 

Occasionally you get random bugs (such as this) after installing or updating the software but before restarting the computer.  Restarting the computer shuts everything down and loads again from scratch so usually fixes up these random on-off issues.

 

Also double check that you have speak typed characters on as well :)

 

Kind regards

 

Quentin.

 

On Wed, Feb 12, 2020 at 10:00 PM Martin Thomas Swaton <list@...> wrote:

Hi,


I searched for this problem, but could not find a topic on it ... so if
this already was asked, I am sorry...


Since the update the feedback of special characters and punctuation
while typing has changed when you set the feedback to "words" and
disable "characters".


normally special characters and punctuation was spoken emedeately on
their keypress together with any other characters, that have been typed
before.


example of old behaviour:

type: a.

feedback: a dot


new behavour:

type: a.

feedback: a


this is very problematic as you now do not get any feedback on typed
special characters and punctuation. Try to type a smiley, you won't hear
it. just silence.


Tried that with eloquence and espeak. So the speech/voice does not matter.


Hope this can be fixed

and additionally I would suggest to add a option/choice to choose wether
special characters (and numbers) should be spoken emedeately on their
keypress or together with other characters as whole words. So users
could decide, which they prefer, as there where discussions in the past
about that.


but right now it would be important to get back any feedback for theese
special characters and punctuation.


cheers

Martin







 

--

Quentin Christensen
Training and Support Manager

 

 


Re: special characters and punctuation feedback while typing in v2019.3.1

Martin Thomas Swaton
 

Hello,


as anounced I looked up the version of NVDA where it last worked correctly:

nvda v2019.2.1 gives the feedback as expected.

a "." is spoken emedeately. Other "words" are spoken on space or at the keypress of such special characters.

In V2019.3.1 special characters still trigger speaking of words, but are not spoken themselves.


This should be fixed as soon as possible as typing in word mode is no longer manageable.


cheers

Martin


Am 12.02.2020 um 13:50 schrieb Martin Thomas Swaton:

Hi again,


the reboot did not change anything - as expected.


@Ralf I had 2019.2 (do not know which one exactly) installed on this computer (and still have it on my notebook) and there it works as expected.

   when I get back home, I can look at the version of nvda where it worked last.


cheers

Martin




Am 12.02.2020 um 13:04 schrieb Ralf Kefferpuetz:

Hi Quentin,

I understood Martin that he discovers that with typed chars off and typed words on. And that can beconfirmed at my end, but it was the same under 2019.2.1

 

Cheers,

  Ralf

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen
Sent: Mittwoch, 12. Februar 2020 12:43
To: nvda@nvda.groups.io
Subject: Re: [nvda] special characters and punctuation feedback while typing in v2019.3.1

 

Hi Martin,

 

Have you restarted the computer since you updated NVDA?  I just tried type a. with speak typed characters on, and NVDA read "A dot" just as you expected.  I don't have Eloquence, but it worked the same with eSpeak and with Windows OneCore voices.

 

Occasionally you get random bugs (such as this) after installing or updating the software but before restarting the computer.  Restarting the computer shuts everything down and loads again from scratch so usually fixes up these random on-off issues.

 

Also double check that you have speak typed characters on as well :)

 

Kind regards

 

Quentin.

 

On Wed, Feb 12, 2020 at 10:00 PM Martin Thomas Swaton <list@...> wrote:

Hi,


I searched for this problem, but could not find a topic on it ... so if
this already was asked, I am sorry...


Since the update the feedback of special characters and punctuation
while typing has changed when you set the feedback to "words" and
disable "characters".


normally special characters and punctuation was spoken emedeately on
their keypress together with any other characters, that have been typed
before.


example of old behaviour:

type: a.

feedback: a dot


new behavour:

type: a.

feedback: a


this is very problematic as you now do not get any feedback on typed
special characters and punctuation. Try to type a smiley, you won't hear
it. just silence.


Tried that with eloquence and espeak. So the speech/voice does not matter.


Hope this can be fixed

and additionally I would suggest to add a option/choice to choose wether
special characters (and numbers) should be spoken emedeately on their
keypress or together with other characters as whole words. So users
could decide, which they prefer, as there where discussions in the past
about that.


but right now it would be important to get back any feedback for theese
special characters and punctuation.


cheers

Martin






 

--

Quentin Christensen
Training and Support Manager

 

 


Re: special characters and punctuation feedback while typing in v2019.3.1

Rui Fontes
 

Ok, then it is a different problem...


Rui Fontes


Às 12:52 de 12/02/2020, Martin Thomas Swaton escreveu:

Hi Rui,



Are you talking when writing in a browser, in Skype and so on?

it does not matter where - right now I write in thunderbird, I also tryed firefox and Notebad.

It is a global behaviour

best,

Martin



Rui Fontes


Às 11:00 de 12/02/2020, Martin Thomas Swaton escreveu:
Hi,


I searched for this problem, but could not find a topic on it ... so if this already was asked, I am sorry...


Since the update the feedback of special characters and punctuation while typing has changed when you set the feedback to "words" and disable "characters".


normally special characters and punctuation was spoken emedeately on their keypress together with any other characters, that have been typed before.


example of old behaviour:

type: a.

feedback: a dot
a.aa a.a.

new behavour:

type: a.

feedback: a


this is very problematic as you now do not get any feedback on typed special characters and punctuation. Try to type a smiley, you won't hear it. just silence.


Tried that with eloquence and espeak. So the speech/voice does not matter.


Hope this can be fixed

and additionally I would suggest to add a option/choice to choose wether special characters (and numbers) should be spoken emedeately on their keypress or together with other characters as whole words. So users could decide, which they prefer, as there where discussions in the past about that.


but right now it would be important to get back any feedback for theese special characters and punctuation.


cheers

Martin







Re: special characters and punctuation feedback while typing in v2019.3.1

Martin Thomas Swaton
 

Hi Rui,



Are you talking when writing in a browser, in Skype and so on?

it does not matter where - right now I write in thunderbird, I also tryed firefox and Notebad.

It is a global behaviour

best,

Martin



Rui Fontes


Às 11:00 de 12/02/2020, Martin Thomas Swaton escreveu:
Hi,


I searched for this problem, but could not find a topic on it ... so if this already was asked, I am sorry...


Since the update the feedback of special characters and punctuation while typing has changed when you set the feedback to "words" and disable "characters".


normally special characters and punctuation was spoken emedeately on their keypress together with any other characters, that have been typed before.


example of old behaviour:

type: a.

feedback: a dot


new behavour:

type: a.

feedback: a


this is very problematic as you now do not get any feedback on typed special characters and punctuation. Try to type a smiley, you won't hear it. just silence.


Tried that with eloquence and espeak. So the speech/voice does not matter.


Hope this can be fixed

and additionally I would suggest to add a option/choice to choose wether special characters (and numbers) should be spoken emedeately on their keypress or together with other characters as whole words. So users could decide, which they prefer, as there where discussions in the past about that.


but right now it would be important to get back any feedback for theese special characters and punctuation.


cheers

Martin






Re: special characters and punctuation feedback while typing in v2019.3.1

Martin Thomas Swaton
 

Hi again,


the reboot did not change anything - as expected.


@Ralf I had 2019.2 (do not know which one exactly) installed on this computer (and still have it on my notebook) and there it works as expected.

   when I get back home, I can look at the version of nvda where it worked last.


cheers

Martin




Am 12.02.2020 um 13:04 schrieb Ralf Kefferpuetz:

Hi Quentin,

I understood Martin that he discovers that with typed chars off and typed words on. And that can beconfirmed at my end, but it was the same under 2019.2.1

 

Cheers,

  Ralf

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen
Sent: Mittwoch, 12. Februar 2020 12:43
To: nvda@nvda.groups.io
Subject: Re: [nvda] special characters and punctuation feedback while typing in v2019.3.1

 

Hi Martin,

 

Have you restarted the computer since you updated NVDA?  I just tried type a. with speak typed characters on, and NVDA read "A dot" just as you expected.  I don't have Eloquence, but it worked the same with eSpeak and with Windows OneCore voices.

 

Occasionally you get random bugs (such as this) after installing or updating the software but before restarting the computer.  Restarting the computer shuts everything down and loads again from scratch so usually fixes up these random on-off issues.

 

Also double check that you have speak typed characters on as well :)

 

Kind regards

 

Quentin.

 

On Wed, Feb 12, 2020 at 10:00 PM Martin Thomas Swaton <list@...> wrote:

Hi,


I searched for this problem, but could not find a topic on it ... so if
this already was asked, I am sorry...


Since the update the feedback of special characters and punctuation
while typing has changed when you set the feedback to "words" and
disable "characters".


normally special characters and punctuation was spoken emedeately on
their keypress together with any other characters, that have been typed
before.


example of old behaviour:

type: a.

feedback: a dot


new behavour:

type: a.

feedback: a


this is very problematic as you now do not get any feedback on typed
special characters and punctuation. Try to type a smiley, you won't hear
it. just silence.


Tried that with eloquence and espeak. So the speech/voice does not matter.


Hope this can be fixed

and additionally I would suggest to add a option/choice to choose wether
special characters (and numbers) should be spoken emedeately on their
keypress or together with other characters as whole words. So users
could decide, which they prefer, as there where discussions in the past
about that.


but right now it would be important to get back any feedback for theese
special characters and punctuation.


cheers

Martin






 

--

Quentin Christensen
Training and Support Manager

 

 

13841 - 13860 of 83879