Date   

Re: Language issue with NVDA

Sean Budd (NV Access)
 

Can you please test 2022.2beta1. I believe we fixed this issue in that release: https://www.nvaccess.org/post/nvda-2022-2beta1/ 

 

Kind Regards,

Sean Budd

NV Access Software Developer


Re: In-Process AND a beta both out today

Robert Mendoza
 

Quentin ,

One thing I noticed when reading of my mother's tongue:
Tagalog is very clear and crisp.
I am using the default Voice: English (Great Britain) and Variant: Max
for the speach engine e-Speak ng.
I know you are not fun of the variant max though. LOL!
But, I was so impressed with the narration even a little dialects of my language is so clear.
Just to give you overview from the time I used NVDA max and alternately used variant quenzy as my choice.

I tested this out of curiosity as portable to my machine.
Cheers,
Robert Mendoza

On 6/16/2022 2:07 PM, Quentin Christensen wrote:
Our latest In-Process blog is now available!
Highlights from this issue:
- Spotlight on several new features and fixes you might have missed from NVDA 2022.1
- Info on the first beta of the upcoming NVDA 2022.2
- NV Access going to RSB Tech Fest, we hope to see you there next week!
- We chat with Vision Australia Radio's Focal Point program
- We have refreshed our LinkedIn page, come follow us!
- #NVeofy and more!

Read it now at: https://www.nvaccess.org/post/in-process-16th-june-2022/ 

--
Quentin Christensen
Training and Support Manager


Re: holding off on 2022.1 due to Code Factory dragging their feet

Ravindran V.S.
 

Dear Mike,

If my understanding is correct of your message,

Please note, ever since NVDA released as a free screen reader millions of Blind users have got into some kind of technical or computer literacy and use of technology.

If not still a vast majority would not be able to access computers due to the high cost of the commercial products.

Also, NVDA has created many job opportunities to many Visually Impaired Persons in several countries.

So, I urge that this should continue as the current way it is as an open source product and accessible to all Blind people.

People in the poor countries, and the developing countries are mainly depending on this screen reader. Who may be heavily using the product, but may not be in a position or afford to donate towards this cause.

Therefore, I kindly request to all the developers and contributors to keep  and continue this as an open source and free product, or at least to the people in the poor countries.

We even get the computers through donations, under this circumstances how could we spend hundreds or thousands of Dollars to the commercial Screen Readers?

I live in Sri Lanka, and now even we almost starving , under this situation cannot think of purchasing any screen reader or anything other than considered to be essential items.

Which some time may cost the job of the Blind people as well, who are depending on NVDA for their work .

So, for delay of any Add-Ons should not deny access of a screen reader for many Blind people.

Thank you in advance for understanding. NVDA is a blessing to many Blind.

Ravi.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of mike mcglashon
Sent: Thursday, June 16, 2022 9:44 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

Quoting:

My own view is that these add-ons should be updated in the Alpha or Beta stages, not after release. Either that, or NVDA should not keep breaking compatibility with them.

End quote:

 

Amen to this.

If NVDA were a commercial software instead of “charitable open source code”, these practices might not be tolerated as easily.

I wish sometimes that NVDA would “actually charge” for its software instead of hiding behind “donations” then we could demand excellence.

It is strictly my belief that we as a society give too much leeway to “charitable” products.

 

I say these things as a “donor” to NVDA.

 

 

Please advise as you like.

 

Mike M.

 

Mike mcglashon

Email: Michael.mcglashon@...

Ph: 618 783 9331

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Steve Nutt
Sent: Thursday, June 16, 2022 12:06 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

No, you’re not alone. It makes work also for the average user, who gets their NVDA just right with add-ons, only to find them broken in the next version.

 

My own view is that these add-ons should be updated in the Alpha or Beta stages, not after release. Either that, or NVDA should not keep breaking compatibility with them.

 

All the best


Steve

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Tyler Wood
Sent: 23 May 2022 20:16
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

As a random interjection I find it quite disturbing how easily add ons are losing compatibility from one minor version to the next. This is a trend I as a user am not a fan of. It means more work for developers, more issues by the end user if add ons become unsupported, or at least, unsupported according to NVDA itself, and less time to actually make improvements for the developers who are already placing their doubtlessly limited and free time into this wonderful hobby of creating resources for NVDA to take advantage of.

I am truly curious to know what I, as a user, am benefiting from with this so called fragmentation. Previously add ons would work without issue, now it’s a guessing game as to which add ons will be disabled and stop working when I’d like to update NVDA from, again, one minor version to the next.

 

As it stands right now, I’m running a portable version of the latest NVDA due to the above, with my main install remaining an older version. Am I alone in viewing this slightly worrying trend?

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of mattias
Sent: Monday, May 23, 2022 10:38 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

Lol we got the same answer..

 

Skickades från E-post för Windows

 

Från: Supanut Leepaisomboon
Skickat: den 23 maj 2022 12:18
Till: nvda@nvda.groups.io
Ämne: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

So I just got a reply from Codefactory, to a ticket regarding compatibility with NVDA 2022.1 that I submitted way back in April. Below is their response:
Good morning,
We are aware that a breaking NVDA update was released today.
We've been working on the addon, but unfortunately our update will take a few more days to complete.
Thank you for your patience.
The Code Factory technical team.

 


Re: "Recognition failed" whenever I try to use NVDA+R

Joshua Tubbs
 

Oh... yes, I am using NVDA+R, completely missed the typo in my message. As for screen curtain, yes it is off. NVDA says Recognition failed every time though, and it wouldn't say it if it was on and would instead instruct the user to turn screen curtain off.
I'm just trying to figure out what would cause it to fail like this. Maybe I'll grab a portable version and see if it works but I doubt it.


On Thu, Jun 16, 2022 at 5:59 AM Luke Davis <luke@...> wrote:
Joshua Tubbs wrote:
> It worked for the longest time.
> Would recognition failed message be because the OCR engine isn't able
> to be ran?

Maybe. Have you recently started using screen curtain? I believe it doesn't
work when the curtain is on.

Brian's Mail list account via groups.io wrote:

> I'm a bit puzzled by the actual meaning of Cloud pc in this context.

Presumably he's remoting into a virtual server somewhere.

Luke







Re: Does NVDA have this feature that Window-eyes has?

Luke Davis
 

Brian Vogel wrote:

this is the regular expression one would use:(\+|-|\*|\=){3,}--
Brian, I have not tested the above, nor what I am going to say next, but I'm curious why you are re-inventing the bracket expression?

AFAIK, the Re above could be more efficiently, and clearly, written as:

[-*\+\=]{3,}

https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html#tag_09_03_05

A more complete separator line catcher might be:

[-*\+\=._]{4,}

I used 4 as the minimum, so it does not catch a non-UTF-8 ellipsis (...).

Luke


Re: Recommendations for NVDA Add-Ons

Bob Cavanaugh
 

It all depends on what you're using NVDA for. Personally, I only run
three addons, and am probably going to remove one. They are Numpad Nav
Mode, Addon Updater, and NV Speech Player, though that's the one I'm
thinking of removing as I don't like its voice. Addon Updater is the
essential one if you're running any addons, otherwise it really
depends on how you use the program.

On 6/16/22, Mo Khan <mk3386751@...> wrote:
Which nvda addons would you recommend please? much appreciated. thank you.
Mo.






Re: Recommendations for NVDA Add-Ons

 

Mo,

There are just too many, covering an awful lot of territory, to be able to make broad general recommendations.

That being said, the following add-ons are "must haves" because of how they enhance NVDA's core code or applications you may be using:
1.  Add-On Updater.
2.  Add-Ons Documentation
3. Mozilla Apps Enhancements  (if you use Thunderbird and/or Firefox)
4.  Windows App Essentials

You can explore, and obtain, NVDA add-ons from the following two sites:

NVDA Community Add-Ons Site

NVDA Add-Ons Directory (hosted by the Spanish-Speaking NVDA Community Association)

--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The real art of conversation is not only to say the right thing in the right place but to leave unsaid the wrong thing at the tempting moment.

        ~ Dorothy Nevill


Re: Recommendations for NVDA Add-Ons

Chris Smart
 

That is a rather open-ended question. What do you want NVDA to do for you that it does not currently?

 

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Mo Khan
Sent: June 16, 2022 2:37 PM
To: nvda@nvda.groups.io
Subject: [nvda] Recommendations for NVDA Add-Ons

 

Which nvda addons would you recommend please? much appreciated. thank you. Mo.


Recommendations for NVDA Add-Ons

Mo Khan
 

Which nvda addons would you recommend please? much appreciated. thank you. Mo.


Re: holding off on 2022.1 due to Code Factory dragging their feet

 

On Thu, Jun 16, 2022 at 12:14 PM, mike mcglashon wrote:
My own view is that these add-ons should be updated in the Alpha or Beta stages, not after release. Either that, or NVDA should not keep breaking compatibility with them.
-
NVAccess is not the owner or maintainer of the vast majority of add-ons.  Thus, they logically have zero responsibility for them.

The compatibility-breaking releases are announced many months in advance and the developer community (including add-on developers) are on notice that tweaking, even if it's just manifest tweaking, will be necessary.

This is not the slightest bit different than what happens with commercial software, Windows being the perfect example.  Microsoft announces when a new version (or feature update) is coming well in advance and all third-parties (equivalent of the add-on developers) are on notice that they need to update to keep pace.  This is not optional.

There is core code and there is ancillary code.  Ancillary code follows core code, or should.

There have been times, and there are some add-on developers, who are consistently proactive and whose add-ons are always updated before actual release date, often by the time the beta comes out.  We've had a couple of rough years with backwards-compatibility breaking NVDA releases.  But NVDA absolutely has to keep pace with Windows and all the software it is meant to give you access to.  That's far more critical in the big picture than the occasional add-on breakage (much of which could be avoided, but sometimes not if an add-on has been dropped by its original developer and there was no transition plan for someone else to pick it up).
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The real art of conversation is not only to say the right thing in the right place but to leave unsaid the wrong thing at the tempting moment.

        ~ Dorothy Nevill


Re: Does NVDA have this feature that Window-eyes has?

 

Oops, a typo in my first description.  I am only looking for plus signs, hyphens, and asterisks, in any combination, repeated a minimum of 3 times.  I did not include the equal sign.  If one wished to, this is the regular expression one would use:

(\+|-|\*|\=){3,}

--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The real art of conversation is not only to say the right thing in the right place but to leave unsaid the wrong thing at the tempting moment.

        ~ Dorothy Nevill


Re: Does NVDA have this feature that Window-eyes has?

 

My solution to this is to create default dictionary entries to handle common "separator line" repetitions and actually have NVDA say, "separator line."  I don't care what, precisely, the chosen character sequence is.

Here is the regular expression I use for a "long" separator line of 3 or more characters in sequence.  Additional characters could be added with the or (pipe) operator if you have someone who uses something else in combination with + or = or -, etc.

(\+|-|\*){3,}

and my replacement is "Separator line."  

For common short, 2-character separators, I use this regular expression:   (-|\*|\+){2}\s+$

And that regular expression captures 2 characters that are hyphens, asterisks, or plus signs followed by any number of white space characters anchored by the end of the line.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The real art of conversation is not only to say the right thing in the right place but to leave unsaid the wrong thing at the tempting moment.

        ~ Dorothy Nevill


Re: Does NVDA have this feature that Window-eyes has?

Sarah k Alawami
 

I hear 9 equals 9 equals etc. sounds like it does have this to my ear.  Is that not what you mean?

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ron Canazzi
Sent: Thursday, June 16, 2022 9:01 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Does NVDA have this feature that Window-eyes has?

 

Hi Gene,

It does have it for single character strings. I believe what they are asking is if there are multiple character repetitions whether that feature is active.

Here's an example of what I mean.

9=9=9=9=9=9=9=9=9=

NVDA doesn't have a setting for such strings as does JAWS sand Window-Eyes.


Re: holding off on 2022.1 due to Code Factory dragging their feet

Tyler Wood
 

Hard agree here.

While I appreciate the effort maintaining add ons from version to version and announcing when fixes have been implemented from version to version, I also feel like this shouldn’t strictly be needed and, again, is taking time away from limited development time.

Just my view. I feel like it’s a huge regression and step backwards with very little benefit apart from more questions re: addon support, fragmentation and add ons that will slowly but surely lose support and force a user who relies on it to continue using an older version of NVDA.

Very unfortunate, but I’m just a user, not a developer.

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of mike mcglashon
Sent: Thursday, June 16, 2022 11:14 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

Quoting:

My own view is that these add-ons should be updated in the Alpha or Beta stages, not after release. Either that, or NVDA should not keep breaking compatibility with them.

End quote:

 

Amen to this.

If NVDA were a commercial software instead of “charitable open source code”, these practices might not be tolerated as easily.

I wish sometimes that NVDA would “actually charge” for its software instead of hiding behind “donations” then we could demand excellence.

It is strictly my belief that we as a society give too much leeway to “charitable” products.

 

I say these things as a “donor” to NVDA.

 

 

Please advise as you like.

 

Mike M.

 

Mike mcglashon

Email: Michael.mcglashon@...

Ph: 618 783 9331

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Steve Nutt
Sent: Thursday, June 16, 2022 12:06 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

No, you’re not alone. It makes work also for the average user, who gets their NVDA just right with add-ons, only to find them broken in the next version.

 

My own view is that these add-ons should be updated in the Alpha or Beta stages, not after release. Either that, or NVDA should not keep breaking compatibility with them.

 

All the best


Steve

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Tyler Wood
Sent: 23 May 2022 20:16
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

As a random interjection I find it quite disturbing how easily add ons are losing compatibility from one minor version to the next. This is a trend I as a user am not a fan of. It means more work for developers, more issues by the end user if add ons become unsupported, or at least, unsupported according to NVDA itself, and less time to actually make improvements for the developers who are already placing their doubtlessly limited and free time into this wonderful hobby of creating resources for NVDA to take advantage of.

I am truly curious to know what I, as a user, am benefiting from with this so called fragmentation. Previously add ons would work without issue, now it’s a guessing game as to which add ons will be disabled and stop working when I’d like to update NVDA from, again, one minor version to the next.

 

As it stands right now, I’m running a portable version of the latest NVDA due to the above, with my main install remaining an older version. Am I alone in viewing this slightly worrying trend?

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of mattias
Sent: Monday, May 23, 2022 10:38 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

Lol we got the same answer..

 

Skickades från E-post för Windows

 

Från: Supanut Leepaisomboon
Skickat: den 23 maj 2022 12:18
Till: nvda@nvda.groups.io
Ämne: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

So I just got a reply from Codefactory, to a ticket regarding compatibility with NVDA 2022.1 that I submitted way back in April. Below is their response:
Good morning,
We are aware that a breaking NVDA update was released today.
We've been working on the addon, but unfortunately our update will take a few more days to complete.
Thank you for your patience.
The Code Factory technical team.

 


Re: holding off on 2022.1 due to Code Factory dragging their feet

mike mcglashon
 

Quoting:

My own view is that these add-ons should be updated in the Alpha or Beta stages, not after release. Either that, or NVDA should not keep breaking compatibility with them.

End quote:

 

Amen to this.

If NVDA were a commercial software instead of “charitable open source code”, these practices might not be tolerated as easily.

I wish sometimes that NVDA would “actually charge” for its software instead of hiding behind “donations” then we could demand excellence.

It is strictly my belief that we as a society give too much leeway to “charitable” products.

 

I say these things as a “donor” to NVDA.

 

 

Please advise as you like.

 

Mike M.

 

Mike mcglashon

Email: Michael.mcglashon@...

Ph: 618 783 9331

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Steve Nutt
Sent: Thursday, June 16, 2022 12:06 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

No, you’re not alone. It makes work also for the average user, who gets their NVDA just right with add-ons, only to find them broken in the next version.

 

My own view is that these add-ons should be updated in the Alpha or Beta stages, not after release. Either that, or NVDA should not keep breaking compatibility with them.

 

All the best


Steve

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Tyler Wood
Sent: 23 May 2022 20:16
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

As a random interjection I find it quite disturbing how easily add ons are losing compatibility from one minor version to the next. This is a trend I as a user am not a fan of. It means more work for developers, more issues by the end user if add ons become unsupported, or at least, unsupported according to NVDA itself, and less time to actually make improvements for the developers who are already placing their doubtlessly limited and free time into this wonderful hobby of creating resources for NVDA to take advantage of.

I am truly curious to know what I, as a user, am benefiting from with this so called fragmentation. Previously add ons would work without issue, now it’s a guessing game as to which add ons will be disabled and stop working when I’d like to update NVDA from, again, one minor version to the next.

 

As it stands right now, I’m running a portable version of the latest NVDA due to the above, with my main install remaining an older version. Am I alone in viewing this slightly worrying trend?

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of mattias
Sent: Monday, May 23, 2022 10:38 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

Lol we got the same answer..

 

Skickades från E-post för Windows

 

Från: Supanut Leepaisomboon
Skickat: den 23 maj 2022 12:18
Till: nvda@nvda.groups.io
Ämne: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

So I just got a reply from Codefactory, to a ticket regarding compatibility with NVDA 2022.1 that I submitted way back in April. Below is their response:
Good morning,
We are aware that a breaking NVDA update was released today.
We've been working on the addon, but unfortunately our update will take a few more days to complete.
Thank you for your patience.
The Code Factory technical team.

 


Re: Does NVDA have this feature that Window-eyes has?

Rui Fontes
 

Not only presents information differently...

In NVDA you can not configure how many characters untill starting to announce x equals...


If I remember correctly, in Jaws you could configure that...


Rui Fontes


Às 16:35 de 16/06/2022, Chris Mullins escreveu:

Hi

The answer to the question is yes, NVDA does have the feature that identifies repeating characters, it just delivers the information in a different way to Window Eyes.

 

Cheers

                Chris

 

Sent from Mail for Windows

 

From: Sarah k Alawami
Sent: 16 June 2022 16:25
To: nvda@nvda.groups.io
Subject: Re: [nvda] Does NVDA have this feature that Window-eyes has?

 

I like 9 equals rather than equals repeats 9 times, but that's just me. It's faster  verbiage IMHO.

 

-----Original Message-----

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Steve Nutt

Sent: Thursday, June 16, 2022 4:49 AM

To: nvda@nvda.groups.io

Subject: Re: [nvda] Does NVDA have this feature that Window-eyes has?

 

Which is quite bad, because what if you get the string 9= in a file, maybe for programming?

 

It should say Equals repeats nine times.

 

All the best

 

Steve

 

-----Original Message-----

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Jackie

Sent: 22 May 2022 08:51

To: nvda@nvda.groups.io

Subject: Re: [nvda] Does NVDA have this feature that Window-eyes has?

 

NVDA says the number then the symbol, ie, if I write 9 consecutive equal signs, NVDA says 9 equals.

 

On 5/22/22, Sim Kah Yong <simkahyong@...> wrote:

> Hi all, I just received an email from Amazon and it contains a string

> of "equal sign" (about 22) in part of the email. Window-eyes will read

> "equal, equal,  repeated 22 times".

> NVDA and JAWS will read 22 times of the "equal sign". Obviously,

> Window-eyes is is the better option here. Does anyone know if NVDA or

> JAWS has such feature? Thank you.

>

 

 

--

Subscribe to a WordPress for Newbies Mailing List by sending a message to:

wp4newbs-request@... with 'subscribe' in the Subject field OR by visiting the list page at http://www.freelists.org/list/wp4newbs

& check out my sites at www.brightstarsweb.com & www.mysitesbeenhacked.com

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


Re: holding off on 2022.1 due to Code Factory dragging their feet

Steve Nutt
 

No, you’re not alone. It makes work also for the average user, who gets their NVDA just right with add-ons, only to find them broken in the next version.

 

My own view is that these add-ons should be updated in the Alpha or Beta stages, not after release. Either that, or NVDA should not keep breaking compatibility with them.

 

All the best


Steve

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Tyler Wood
Sent: 23 May 2022 20:16
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

As a random interjection I find it quite disturbing how easily add ons are losing compatibility from one minor version to the next. This is a trend I as a user am not a fan of. It means more work for developers, more issues by the end user if add ons become unsupported, or at least, unsupported according to NVDA itself, and less time to actually make improvements for the developers who are already placing their doubtlessly limited and free time into this wonderful hobby of creating resources for NVDA to take advantage of.

I am truly curious to know what I, as a user, am benefiting from with this so called fragmentation. Previously add ons would work without issue, now it’s a guessing game as to which add ons will be disabled and stop working when I’d like to update NVDA from, again, one minor version to the next.

 

As it stands right now, I’m running a portable version of the latest NVDA due to the above, with my main install remaining an older version. Am I alone in viewing this slightly worrying trend?

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of mattias
Sent: Monday, May 23, 2022 10:38 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

Lol we got the same answer..

 

Skickades från E-post för Windows

 

Från: Supanut Leepaisomboon
Skickat: den 23 maj 2022 12:18
Till: nvda@nvda.groups.io
Ämne: Re: [nvda] holding off on 2022.1 due to Code Factory dragging their feet

 

So I just got a reply from Codefactory, to a ticket regarding compatibility with NVDA 2022.1 that I submitted way back in April. Below is their response:
Good morning,
We are aware that a breaking NVDA update was released today.
We've been working on the addon, but unfortunately our update will take a few more days to complete.
Thank you for your patience.
The Code Factory technical team.

 


Re: Does NVDA have this feature that Window-eyes has?

Ron Canazzi
 

Hi Gene,

It does have it for single character strings. I believe what they are asking is if there are multiple character repetitions whether that feature is active.

Here's an example of what I mean.

9=9=9=9=9=9=9=9=9=

NVDA doesn't have a setting for such strings as does JAWS sand Window-Eyes.


On 6/16/2022 11:31 AM, Gene wrote:
It does have it.  If it didn't, you would hear something like equal repeated as many times as it appears on a line.  Instead you hear twenty equals, if there are twenty equals uninterrupted on a line.

If your punctuation isn't set at a level where the sign is spoken, you will hear nothing.  So with equal, if punctuation is set to none, you won't hear anything.  With punctuation set to some or higher, you will hear the announcement.  However, I know of no way to turn the feature  off or on and I don't know if that matters.

Gene
On 6/16/2022 10:25 AM, Sarah k Alawami wrote:
You might want to maybe put that issue in as a github issue, or if you can code, make an add on if one does not exist. 

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Steve Nutt
Sent: Thursday, June 16, 2022 4:49 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Does NVDA have this feature that Window-eyes has?

Hi,

JAWS has it, it's called Filter Repeated Characters, and is under Text Processing.

As far as I can see, NVDA doesn't have it.

All the best

Steve

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Sim Kah Yong
Sent: 22 May 2022 08:31
To: nvda@nvda.groups.io
Subject: [nvda] Does NVDA have this feature that Window-eyes has?

Hi all, I just received an email from Amazon and it contains a string of "equal sign" (about 22) in part of the email. Window-eyes will read "equal, equal,  repeated 22 times".

NVDA and JAWS will read 22 times of the "equal sign". Obviously, Window-eyes is is the better option here. Does anyone know if NVDA or JAWS has such feature? Thank you.






















-- 
Signature:
For a nation to admit it has done grievous wrongs and will strive to correct them for the betterment of all is no vice;
For a nation to claim it has always been great, needs no improvement  and to cling to its past achievements is no virtue!


Re: Does NVDA have this feature that Window-eyes has?

Chris Mullins
 

Hi

The answer to the question is yes, NVDA does have the feature that identifies repeating characters, it just delivers the information in a different way to Window Eyes.

 

Cheers

                Chris

 

Sent from Mail for Windows

 

From: Sarah k Alawami
Sent: 16 June 2022 16:25
To: nvda@nvda.groups.io
Subject: Re: [nvda] Does NVDA have this feature that Window-eyes has?

 

I like 9 equals rather than equals repeats 9 times, but that's just me. It's faster  verbiage IMHO.

 

-----Original Message-----

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Steve Nutt

Sent: Thursday, June 16, 2022 4:49 AM

To: nvda@nvda.groups.io

Subject: Re: [nvda] Does NVDA have this feature that Window-eyes has?

 

Which is quite bad, because what if you get the string 9= in a file, maybe for programming?

 

It should say Equals repeats nine times.

 

All the best

 

Steve

 

-----Original Message-----

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Jackie

Sent: 22 May 2022 08:51

To: nvda@nvda.groups.io

Subject: Re: [nvda] Does NVDA have this feature that Window-eyes has?

 

NVDA says the number then the symbol, ie, if I write 9 consecutive equal signs, NVDA says 9 equals.

 

On 5/22/22, Sim Kah Yong <simkahyong@...> wrote:

> Hi all, I just received an email from Amazon and it contains a string

> of "equal sign" (about 22) in part of the email. Window-eyes will read

> "equal, equal,  repeated 22 times".

> NVDA and JAWS will read 22 times of the "equal sign". Obviously,

> Window-eyes is is the better option here. Does anyone know if NVDA or

> JAWS has such feature? Thank you.

>

 

 

--

Subscribe to a WordPress for Newbies Mailing List by sending a message to:

wp4newbs-request@... with 'subscribe' in the Subject field OR by visiting the list page at http://www.freelists.org/list/wp4newbs

& check out my sites at www.brightstarsweb.com & www.mysitesbeenhacked.com

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


Re: Does NVDA have this feature that Window-eyes has?

Gene
 

It does have it.  If it didn't, you would hear something like equal repeated as many times as it appears on a line.  Instead you hear twenty equals, if there are twenty equals uninterrupted on a line.

If your punctuation isn't set at a level where the sign is spoken, you will hear nothing.  So with equal, if punctuation is set to none, you won't hear anything.  With punctuation set to some or higher, you will hear the announcement.  However, I know of no way to turn the feature  off or on and I don't know if that matters.

Gene

On 6/16/2022 10:25 AM, Sarah k Alawami wrote:
You might want to maybe put that issue in as a github issue, or if you can code, make an add on if one does not exist. 

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Steve Nutt
Sent: Thursday, June 16, 2022 4:49 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Does NVDA have this feature that Window-eyes has?

Hi,

JAWS has it, it's called Filter Repeated Characters, and is under Text Processing.

As far as I can see, NVDA doesn't have it.

All the best

Steve

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Sim Kah Yong
Sent: 22 May 2022 08:31
To: nvda@nvda.groups.io
Subject: [nvda] Does NVDA have this feature that Window-eyes has?

Hi all, I just received an email from Amazon and it contains a string of "equal sign" (about 22) in part of the email. Window-eyes will read "equal, equal,  repeated 22 times".

NVDA and JAWS will read 22 times of the "equal sign". Obviously, Window-eyes is is the better option here. Does anyone know if NVDA or JAWS has such feature? Thank you.





















3121 - 3140 of 99615