Date   

NVDA not always reading cell contents in MS Excel?

Sally Kiebdaj
 

Hello all,

Normally, I can press F2 on a cel in MS Excel and NVDA will allow me to read and edit the cell contents. Today, this has stopped working. In a spreadsheet I've been using for a week with no problems, I now cannot hear any cell contents after pressing F2. The contents are there and if I make edits and hit enter I can read my edits.However, this is not sufficient for editing prose. 

I'm running:


NVDA 2021.2
Microsoft® Excel® 2019 MSO (16.0.10380.20037) 64-bit 
Windows 10 Pro: Version 2004 (OS Build 19041.1348)

Any ideas? 

Thank you!
Sally 


Re: NVDA2022.1 news

Quentin Christensen
 

Hi Eduardo,

We haven't released NVDA 2021.3 yet!  But yes, we are already planning what will be going in to NVDA 2022.1.

If you are not familiar with the release candidate for NVDA 2021.3, that is the first place to start: https://www.nvaccess.org/post/nvda-2021-3rc1/

There are lots of exciting things coming in NVDA 2021.3.  There is a "snapshots" page with alpha builds, which themselves contain what's new files which get updated as things get fixed and added, but for now, nothing is finalized in those builds.

Kind regards

Quentin.

On Mon, Dec 6, 2021 at 4:04 PM Eduardo Fermiano Luccas <25102008luccas@...> wrote:
hi friends, i heard that NVDA 2022.1 is running, is this true? if so, i would like to know what will be new... i know it's too strenuous for that, but if you don't want to talk, i'll understand!


sorry for the translation errors



--
Quentin Christensen
Training and Support Manager


Bengali / Bangla translator wanted

Quentin Christensen
 

Good afternoon,

As we all know, one of NVDA's strengths has always been the community, and worldwide availability.  To that end, I wanted to reach out as we do not have a Bangla / Bengali translation of NVDA.  As one of the most widely spoken languages in the world, we would be interested in addressing this.

As with our other languages, we are looking for a community-minded volunteer  or group of people to first setup the Bengali / Bangla translation, and then to keep the language updated moving forward.  If anyone is interested, or knows anyone, please do let me know.

Kind regards

Quentin.

--
Quentin Christensen
Training and Support Manager


NVDA2022.1 news

Eduardo Fermiano Luccas
 

hi friends, i heard that NVDA 2022.1 is running, is this true? if so, i would like to know what will be new... i know it's too strenuous for that, but if you don't want to talk, i'll understand!


sorry for the translation errors


Re: a problem with speech dictionaries again.

 

And I found two more, now listed above the prior three:

BlindTech-2

 

blindtechnology

 

blind-techies

 

blind-tech-talk / Blind tech talk

 

blind-t

 

I imagine that blind-t is what's got [blind-t] as its prefix.
--

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

The difference between a top-flight creative man and the hack is his ability to express powerful meanings indirectly.

         ~ Vance Packard

 


Re: a problem with speech dictionaries again.

Gene
 

Then the list isn’t the Blindtech list I thought was being discussed.  I thought it was because the person asking the question wants NVDA to say Blindtech, a completely different list.  So what I thought was a problem isn’t.  The subject line is being displayed correctly.
 
Gene

-----Original Message-----
Sent: Sunday, December 05, 2021 6:17 PM
Subject: Re: [nvda] a problem with speech dictionaries again.
 
It really, really helps if there is certainty about what group is being referred to.  I stopped after these three, but if I search groups.io for "blind" these three are a part of the first 150 out of 357 results:

blind-techies

 

blind-tech-talk / Blind tech talk

 

blind-t


--

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

The difference between a top-flight creative man and the hack is his ability to express powerful meanings indirectly.

         ~ Vance Packard

 


Re: eBook Readers with NVDA

 

Hi all,
For my class textbooks I'm using Kindle and I must say it's pretty accessible, that is, if the books themselves support screen readers. The good thing is that you can get a free sample before buying the book, so you can try reading it with NVDA and see if it is accessible.
For reading PDFs, I'm using both Adobe Reader 11 and Bookworm.
Bookworm is pretty nice and I really like it, though I haven't heard news of any new betas or releases recently.


Re: a problem with speech dictionaries again.

 

It really, really helps if there is certainty about what group is being referred to.  I stopped after these three, but if I search groups.io for "blind" these three are a part of the first 150 out of 357 results:

blind-techies

 

blind-tech-talk / Blind tech talk

 

blind-t


--

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

The difference between a top-flight creative man and the hack is his ability to express powerful meanings indirectly.

         ~ Vance Packard

 


Re: a problem with speech dictionaries again.

Dan Beaver
 

All I know is that if I use the NVDA key and then press the cursor right key and move through the subject line it shows a space then [blind-t] and then another space.  The remainder of the subject follows and doesn't appear to be truncated or anything.


It appears to me that it is being handled differently as anywhere than it is as whole word.  I have been out of the software programming arena so long I can't say why it is doing this.


Dan Beaver

On 12/5/2021 5:17 PM, Gene wrote:
Something is being truncated.  I see the name of the list, written in full as follows:
[BlindTech]
 
If you aren’t seeing that, are you seeing the rest of the subject line in full?  I don’t know how to solve the problem you have but there may be another problem.
 
Gene
-----Original Message-----
From: Dan Beaver
Sent: Sunday, December 05, 2021 3:22 PM
Subject: Re: [nvda] a problem with speech dictionaries again.
 

Hi Gene,


I thought about that and did check it and triple checked it. 


This occurs in the subject of emails from the blind tech mailing list.  I looked and it is showing up exactly as I typed it.  I checked the case of letters, made sure there weren't spaces in the string and other things.


The other instances of bracketed strings I have entries for are from other mailing lists and they work perfectly but this one does not.


Thanks.


Dan Beaver

On 12/5/2021 4:16 PM, Gene wrote:
where does this text occur?  Can you chec it, or have you, for spelling and punctuation?  There is probably something in the way it is written that differs from how you are writing it.
 
Gene
-----Original Message-----
From: Dan Beaver
Sent: Sunday, December 05, 2021 3:02 PM
Subject: [nvda] a problem with speech dictionaries again.
 

I have tried adding a dictionary entry for "[blind-t]" and gave "blind tech" as the replacement string.  I have added this to the default and the voice dictionaries.  NVDA still pronounces "[blind-t]" as though it doesn't see my dictionary entries.

 

I also set case sensitivity to unchecked and type to anywhere and whole word.

 

I am running the latest RC and am running Windows [Version 10.0.19043.1348].

 

Any ideas why NVDA won't recognize that I have a dictionary entry for this?

 

Thanks.

 

 

-- 
Dan Beaver (KA4DAN)
-- 
Dan Beaver (KA4DAN)
-- 
Dan Beaver (KA4DAN)


Re: a problem with speech dictionaries again.

Gene
 

Also, there is no dash as I see Blindtech in the subject line.  That isn’t how the name is written in the address and it shouldn’t be shown in the subject line.  The ;problem, whatever it is, may not need correcting since you have solved the dictionary problem and are satisfied with what is said, but the question still remains why you see an improper statement.
 
Gene

-----Original Message-----
From: Gene
Sent: Sunday, December 05, 2021 4:20 PM
Subject: Re: [nvda] a problem with speech dictionaries again is now fixed partly
 
I’m not sure why the line is shown as it is.  While this might not make sense, perhaps since it is being truncated, somehow your dictionary is being shown something different. 
 
Gene
-----Original Message-----
From: Dan Beaver
Sent: Sunday, December 05, 2021 3:33 PM
Subject: Re: [nvda] a problem with speech dictionaries again is now fixed partly
 

    OK, I am sure I tried setting the type field to anywhere and testing it but apparently not.  I just did again on a hunch and it works correctly.  However, if I set the type to whole word it does not work.  Seems to me it should work in either case since there are no spaces in the pattern string.


Why would it not work for whole word?


Dan Beaver

On 12/5/2021 4:02 PM, Dan Beaver via groups.io wrote:

I have tried adding a dictionary entry for "[blind-t]" and gave "blind tech" as the replacement string.  I have added this to the default and the voice dictionaries.  NVDA still pronounces "[blind-t]" as though it doesn't see my dictionary entries.

 

I also set case sensitivity to unchecked and type to anywhere and whole word.

 

I am running the latest RC and am running Windows [Version 10.0.19043.1348].

 

Any ideas why NVDA won't recognize that I have a dictionary entry for this?

 

Thanks.

 

 

-- 
Dan Beaver (KA4DAN)
-- 
Dan Beaver (KA4DAN)


Re: a problem with speech dictionaries again.

Gene
 

I’m not sure why the line is shown as it is.  While this might not make sense, perhaps since it is being truncated, somehow your dictionary is being shown something different. 
 
Gene

-----Original Message-----
From: Dan Beaver
Sent: Sunday, December 05, 2021 3:33 PM
Subject: Re: [nvda] a problem with speech dictionaries again is now fixed partly
 

    OK, I am sure I tried setting the type field to anywhere and testing it but apparently not.  I just did again on a hunch and it works correctly.  However, if I set the type to whole word it does not work.  Seems to me it should work in either case since there are no spaces in the pattern string.


Why would it not work for whole word?


Dan Beaver

On 12/5/2021 4:02 PM, Dan Beaver via groups.io wrote:

I have tried adding a dictionary entry for "[blind-t]" and gave "blind tech" as the replacement string.  I have added this to the default and the voice dictionaries.  NVDA still pronounces "[blind-t]" as though it doesn't see my dictionary entries.

 

I also set case sensitivity to unchecked and type to anywhere and whole word.

 

I am running the latest RC and am running Windows [Version 10.0.19043.1348].

 

Any ideas why NVDA won't recognize that I have a dictionary entry for this?

 

Thanks.

 

 

-- 
Dan Beaver (KA4DAN)
-- 
Dan Beaver (KA4DAN)


Re: a problem with speech dictionaries again.

Gene
 

Something is being truncated.  I see the name of the list, written in full as follows:
[BlindTech]
 
If you aren’t seeing that, are you seeing the rest of the subject line in full?  I don’t know how to solve the problem you have but there may be another problem.
 
Gene

-----Original Message-----
From: Dan Beaver
Sent: Sunday, December 05, 2021 3:22 PM
Subject: Re: [nvda] a problem with speech dictionaries again.
 

Hi Gene,


I thought about that and did check it and triple checked it. 


This occurs in the subject of emails from the blind tech mailing list.  I looked and it is showing up exactly as I typed it.  I checked the case of letters, made sure there weren't spaces in the string and other things.


The other instances of bracketed strings I have entries for are from other mailing lists and they work perfectly but this one does not.


Thanks.


Dan Beaver

On 12/5/2021 4:16 PM, Gene wrote:
where does this text occur?  Can you chec it, or have you, for spelling and punctuation?  There is probably something in the way it is written that differs from how you are writing it.
 
Gene
-----Original Message-----
From: Dan Beaver
Sent: Sunday, December 05, 2021 3:02 PM
Subject: [nvda] a problem with speech dictionaries again.
 

I have tried adding a dictionary entry for "[blind-t]" and gave "blind tech" as the replacement string.  I have added this to the default and the voice dictionaries.  NVDA still pronounces "[blind-t]" as though it doesn't see my dictionary entries.

 

I also set case sensitivity to unchecked and type to anywhere and whole word.

 

I am running the latest RC and am running Windows [Version 10.0.19043.1348].

 

Any ideas why NVDA won't recognize that I have a dictionary entry for this?

 

Thanks.

 

 

-- 
Dan Beaver (KA4DAN)
-- 
Dan Beaver (KA4DAN)


Re: a problem with speech dictionaries again.

 

This can be fixed with a regex match.
--

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

The difference between a top-flight creative man and the hack is his ability to express powerful meanings indirectly.

         ~ Vance Packard

 


Re: a problem with speech dictionaries again.

Cearbhall O'Meadhra
 

Hi Dan,

 

I agree with you.

I tried out your “[Blind-t] and found it just as you describe. When set to “Whole word”, the dictionary ignores the entry and converts it exactly when set to “Anywhere”!

 

I found a declaration that a hyphenated word is always treated as a whole word.

 

 

All the best,

 

Cearbhall

 

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@...

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Dan Beaver
Sent: Sunday, December 5, 2021 9:23 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] a problem with speech dictionaries again.

 

Hi Gene,

 

I thought about that and did check it and triple checked it. 

 

This occurs in the subject of emails from the blind tech mailing list.  I looked and it is showing up exactly as I typed it.  I checked the case of letters, made sure there weren't spaces in the string and other things.

 

The other instances of bracketed strings I have entries for are from other mailing lists and they work perfectly but this one does not.

 

Thanks.

 

Dan Beaver

On 12/5/2021 4:16 PM, Gene wrote:

where does this text occur?  Can you check it, or have you, for spelling and punctuation?  There is probably something in the way it is written that differs from how you are writing it.

 

Gene

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

From: Dan Beaver

Sent: Sunday, December 05, 2021 3:02 PM

Subject: [nvda] a problem with speech dictionaries again.

 

I have tried adding a dictionary entry for "[blind-t]" and gave "blind tech" as the replacement string.  I have added this to the default and the voice dictionaries.  NVDA still pronounces "[blind-t]" as though it doesn't see my dictionary entries.

 

I also set case sensitivity to unchecked and type to anywhere and whole word.

 

I am running the latest RC and am running Windows [Version 10.0.19043.1348].

 

Any ideas why NVDA won't recognize that I have a dictionary entry for this?

 

Thanks.

 

 

-- 
Dan Beaver (KA4DAN)
-- 
Dan Beaver (KA4DAN)




Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com



Re: a problem with speech dictionaries again.

 

In most pattern matching, a word is defined by white space after it.

If your close square bracket is not followed by white space in the thing being matched, it won't match if whole word matching is used.

If how NVDA does this is different, then someone who knows this will certainly speak up.

Also if something other than white space abuts the open square bracket.
--

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

The difference between a top-flight creative man and the hack is his ability to express powerful meanings indirectly.

         ~ Vance Packard

 


Re: a problem with speech dictionaries again.

Dan Beaver
 

Thanks Brian,


I just looked and the answer is no. 


I did find the cause of the issue which I reported in my previous posting.


Thanks though.


Dan Beaver

On 12/5/2021 4:32 PM, Brian Vogel wrote:
I'm not at my computer right now (I'm backstage, managing props) but do you have any entries in your dictionary priot to that one that match any part of it and substitute something else?

More later, but that is something to check.
--

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

The difference between a top-flight creative man and the hack is his ability to express powerful meanings indirectly.

         ~ Vance Packard

 

-- 
Dan Beaver (KA4DAN)


Re: a problem with speech dictionaries again.

Dan Beaver
 

    OK, I am sure I tried setting the type field to anywhere and testing it but apparently not.  I just did again on a hunch and it works correctly.  However, if I set the type to whole word it does not work.  Seems to me it should work in either case since there are no spaces in the pattern string.


Why would it not work for whole word?


Dan Beaver

On 12/5/2021 4:02 PM, Dan Beaver via groups.io wrote:

I have tried adding a dictionary entry for "[blind-t]" and gave "blind tech" as the replacement string.  I have added this to the default and the voice dictionaries.  NVDA still pronounces "[blind-t]" as though it doesn't see my dictionary entries.


I also set case sensitivity to unchecked and type to anywhere and whole word.


I am running the latest RC and am running Windows [Version 10.0.19043.1348].


Any ideas why NVDA won't recognize that I have a dictionary entry for this?


Thanks.



-- 
Dan Beaver (KA4DAN)
-- 
Dan Beaver (KA4DAN)


Re: a problem with speech dictionaries again.

 

I'm not at my computer right now (I'm backstage, managing props) but do you have any entries in your dictionary priot to that one that match any part of it and substitute something else?

More later, but that is something to check.
--

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

The difference between a top-flight creative man and the hack is his ability to express powerful meanings indirectly.

         ~ Vance Packard

 


Re: counting page and word on libra office.

Robert Portal
 

There is however a not entirely satisfactory work around to this problem possibly available from NVDA itself.

When in a Word document, if you select all (control A) NVDA will tell you how many key-strokes are in the document and if you divide that by 6 you will get a fairly precise estimate of the number of words. I think the document (or chunk of text selected) has to be over 1000 keystrokes (about 167 words) for the figure to be announced. I assume the same keystroke announcement is made in Libra Office Writer although I have never used it.

 

Of course it doesn’t help much with page numbers.

 

Best wishes

 

Robert

Da: nvda@nvda.groups.io Per conto di Brian Vogel
Inviato: dimanche 5 décembre 2021 17:43
A: nvda@nvda.groups.io
Oggetto: Re: [nvda] counting page and word on libra office.

 

On Sun, Dec 5, 2021 at 01:47 AM, farhan israk wrote:

So, I think this place is appropriate to discuss it here.

-
It is only appropriate insofar as it's accessibility with NVDA, which has been covered.

The commands to use any feature of Libre Office, Microsoft Office, or any program are not about NVDA, nor any screen reader for that matter.  They're about the program the screen reader is being used to access.

That being the case, it's not on-topic for the main NVDA group.  The Chat Subgroup is perfectly appropriate for questions regarding any software being used with NVDA.  There is also a Libre Office Accessibility group but I don't seem to have the addresses where I can easily find them.

If I knew the commands for word and page count in Libre Office I would have included them here, but I don't.  But any discussion of Libre Office programs and their functions is not on-topic for the NVDA main group.
--

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

The difference between a top-flight creative man and the hack is his ability to express powerful meanings indirectly.

         ~ Vance Packard

 


Re: a problem with speech dictionaries again.

Dan Beaver
 

Hi Gene,


I thought about that and did check it and triple checked it. 


This occurs in the subject of emails from the blind tech mailing list.  I looked and it is showing up exactly as I typed it.  I checked the case of letters, made sure there weren't spaces in the string and other things.


The other instances of bracketed strings I have entries for are from other mailing lists and they work perfectly but this one does not.


Thanks.


Dan Beaver

On 12/5/2021 4:16 PM, Gene wrote:
where does this text occur?  Can you chec it, or have you, for spelling and punctuation?  There is probably something in the way it is written that differs from how you are writing it.
 
Gene
-----Original Message-----
From: Dan Beaver
Sent: Sunday, December 05, 2021 3:02 PM
Subject: [nvda] a problem with speech dictionaries again.
 

I have tried adding a dictionary entry for "[blind-t]" and gave "blind tech" as the replacement string.  I have added this to the default and the voice dictionaries.  NVDA still pronounces "[blind-t]" as though it doesn't see my dictionary entries.


I also set case sensitivity to unchecked and type to anywhere and whole word.


I am running the latest RC and am running Windows [Version 10.0.19043.1348].


Any ideas why NVDA won't recognize that I have a dictionary entry for this?


Thanks.



-- 
Dan Beaver (KA4DAN)
-- 
Dan Beaver (KA4DAN)

9381 - 9400 of 99652