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

 

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

 

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

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)

    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

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)

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

 

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

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

To: nvda@nvda.groups.io

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)

Hi,

No, but i have some other entries with brackets and they work perfectly.  This is the only one that isn't working.

Dan Beaver

Have you tried eliminating the brackets?

On 12/5/21, Dan Beaver <dbeaver888@...> 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)

Have you tried eliminating the brackets?

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

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)

I really like the bookworm interface, but the problem is sometimes it skips pages when I'm reading with read all command, and for me that is not acceptable. However, if it has been solved from the last time that I used the program, I think is really a good option.

An other option is a spanish program called ebookreader, is not translated to english as I know, but is easy to use.

Regards,

mk.

--

Músico (pianista) y ayuda a usuarios ciegos y con discapacidad visual en el uso de lectores de pantalla y tecnología. Experto certificado en el lector de pantalla NVDA.

Musician (pianist) and help to the blind people and with visual disability in use of screen readers and technology. Certified expert in the screen reader NVDA.

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

 

Out of interest, have you had win10 installed on that Asus and, if so, did it happen then too? I ask because I have a 17-inch Asus gaming laptop running Win10, and it has always done this for me, much to my annoyance! I don't get it as frequently as you do, maybe once every 20 minutes or so. I get it when I'm listening to an album of music using WinAmp, when at some random point all of a sudden, NVDA will read the winAmp title bar! I get it when watching The Chase quiz show in Chrome browser, and I get it if I leave my computer to do something else!

I did ask about this in this group once before, and was advised to turn the logging level up and send a private message with the NVDA log, but I didn't know how to send it! I did save a log, and scoured it for any likely triggers, but nothing seemed suspicious.
It does sound like it is something in the Asus system that is causing this, and it would make me think carefully about buying another Asus laptop, even though I have loved mine otherwise.
Giles