--

You're going to have to use not only your tab key, but your arrow keys
as well, Chris. Just FYI, this is pretty standard procedure.

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

Press NVDA+p until you get the level you want. The default is some.

I don't know what key stroke I accidentally might have hit, but I am now hearing all kinds of unwanted punctuation read, things like "bar" or "dash" or whatever else in places where I don't want them. I didn't change anything in the nvda settings, so I can't imagine what might have happened, but it is driving me to distraction.


Mary

Hello Quentin,

--

On Mon, Dec 6, 2021 at 05:57 PM, Deenadayalan Moodley wrote:

Authors: Ricardo M. Leonarczyk and Rui Fontes

-
Also something changed with this.  Mr. Leonarczyk is still listed as the first author but the second is Łukasz Golonka.

https://github.com/RickLeon/applicationDictionary 
--

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

 

NVDA Chat Subgroup Archive:  https://nvda.groups.io/g/chat/topics

NVDA Chat Subgroup Addresses

To join:  chat+subscribe@nvda.groups.io

To post:  chat@nvda.groups.io

To unsubscribe:  chat+unsubscribe@nvda.groups.io

To receive a message containing the group description, and a list of these commands:  chat+help@nvda.groups.io

To stop receiving messages via email (you may still read messages on the Web):  chat+nomail@nvda.groups.io

This can also be used to put a vacation stop on group messages, then use one of the addresses below to resume delivery in the format of your choice.

To receive each group messages individually:  chat+single@nvda.groups.io

This is the default delivery unless you send a message to one of the addresses that follows.

To receive group messages in an HTML formatted digest:  chat+fulldigest@nvda.groups.io

To receive group messages in a plain text digest:  chat+digest@nvda.groups.io

To receive a daily summary instead of individual messages:  chat+summary@nvda.groups.io

To receive only special messages:  chat+special@nvda.groups.io

To contact the group owner(s):  chat+owner@nvda.groups.io

--

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

 

I had not been aware of that add-on, and it is available via the NVDA Add-Ons Directory.

The latest version, however, is 1.4.  Download Link: https://nvda-addons.org/files/get.php?file=applicationdictionary 

I'd love to know how they implemented this "under the hood".
--

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

 

Thomas,

Given the level of sophistication you already seem to possess in regard to the dictionaries, could you not just create a "permanent" temporary voice or default dictionary file that you could move in to where it needs to be in the NVDA dictionary file hierarchy, unload NVDA, then reload it so that it has the entries you need for the given situation, then flip flop that with your original dictionary when you're done?

I get why you're asking what you're asking, but as far as NVDA being improved to allow it, that would likely be a long way off even if an issue were put in GitHub as I doubt the demand for such is very high.  That's not to say it wouldn't be useful, but it's not likely to be high priority.

A couple of simple batch files or powershell files would allow you to exit the running NVDA, move the existing dictionary to a storage spot, move the context specific dictionary to the necessary NVDA spot, then fire up NVDA again.  You would, of course, be reversing the swap in one (or more, depending on how many "specialty dictionaries" you have or need) of the batch files.

There seem to me to be ways to accomplish what you want using a single TTS, but they will involve workarounds that involve what NVDA itself loads when it's starting up as far as dictionaries go.

Just a thought.
--

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

 

On Mon, Dec 6, 2021 at 03:13 PM, Dan Beaver wrote:

Actually, I am trying to get it not to say the brackets.

-
What is your punctuation level set to?

NVDA is not reading the brackets, at all, for me.  It just says Blind Tee.

See section 12.2.2 of the NVDA user guide.  I strongly suspect this is linked somehow to your synth or, quoting from that section:  ""

The language for which symbol pronunciation is being edited will be shown in the dialog's title. Note that this dialog respects the "Trust voice's language for processing symbols and characters" option found in the Speech category of the NVDA Settings dialog; i.e. it uses the voice language rather than the NVDA global language setting when this option is enabled.
--

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

 

If I use anywhere instead of whole word and the replacement string is spelled out with no brackets then yes it works.  I just don't understand why it doesn't work with the type set to whole word.  The pattern string is definitely following a space and followed by a space.  Should work as a word.

Dan Beaver

Did the dictionary entry you made do that?  I’ve never tried to control punctuation with a dictionary entry.

 

Gene

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

From: Dan Beaver

Sent: Monday, December 06, 2021 3:45 PM

To: nvda@nvda.groups.io

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

 

Well, I really only want them suppressed when they are in the subject of emails.  Sounds dumb I know but I hate having to listen to brackets around things in subject lines because I get so many emails from mailing lists with them.

Dan Beaver

On 12/6/2021 3:33 PM, Gene wrote:

This is an example of why it is important for people to provide details of what they want to do and not just ask how to do something when trying to solve a problem.  The method may not be what the person thinks or there may be a much better one.  You can change punctuation levels sso a specific punctuation mark won’t be spoken at a certain level or so that it will.  For example, if you are using the most level and you don’t want brackets spoken, you can set the level to all.  That will mean that it won’t be spoken at the most level but will when you are using the all level. 

 

I’ll write a description later today if that is indeed what you want, to change the punctuation level for the brackets but leave everything else alone.

 

Gene

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

From: Dan Beaver

Sent: Monday, December 06, 2021 2:13 PM

To: nvda@nvda.groups.io

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

 

Actually, I am trying to get it not to say the brackets.  If I could get it to do that I would be happy to live with "blind-t".  It does not do this if I select whole word as the type. I just sort of randomly chose blind tech just because they discuss tech for the blind on that list.

 

Dan Beaver

On 12/6/2021 3:07 PM, Gene wrote:

Your screen-reader is saying blind-t correctly.  You evidently want it to say blindtech.  Of course, you may have it do so but that is a completely different list.

 

Gene

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

From: Dan Beaver

Sent: Monday, December 06, 2021 2:01 PM

To: nvda@nvda.groups.io

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

 

Here you go Brian,

 

posting 1:

Sender: blind-t@groups.io
Subject: Re: [blind-t] Another sort of, audible? question

 

 

posting 2:

Sender: blind-t@groups.io
Subject: Re: [blind-t] iPhone Status Bar

Dan Beaver

On 12/6/2021 12:32 PM, Brian Vogel wrote:

Dan,

It would be immensely helpful if you would post two items in relation to this issue:

1. The "From" address of one of the messages that is not being read as you'd like it to be.

2. The full, unaltered, Subject line from the same message.

Post two of each, though the From should be the same, if it's easy enough to do.  This is a problem that's not going to be solved in the abstract and where having concrete, actual examples helps in finding a solution.
--

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)

-- 
Dan Beaver (KA4DAN)

-- 
Dan Beaver (KA4DAN)

-- 
Dan Beaver (KA4DAN)

On Mon, Dec 6, 2021 at 05:01 PM, Gene wrote:

I think that mentioning the importance of listening for information about the control or structure you are in in unfamiliar settings is important.

-
It's not just important, it's critical!

Joseph Lee coined the term "information blackout" to describe the fact that there are parts of a screen (or dialog, or whatever) that the sighted just take in as a part of the whole that a screen reader user has no idea even exists unless the screen reader is allowed to go on for long enough to announce it.  This really cannot be fixed in any meaningful sense.

It's funny, but one of the problems I find I have when teaching those new to a screen reader, and particularly if a synth with a very human sounding voice is in use, is getting them to understand that it's perfectly OK to hit CTRL or ESC to shut the screen reader up.  They treat screen reader output as though a real human is reading it to them rather than software.  While I understand why that is, you also have to stop thinking that way or you end up wasting a ton of time.

But the converse is also true, particularly when someone is entering "new territory."  I know that for "old territory" you neither need nor want to listen to the screen reader blithely babble on about what you already know, and know well.  But when something is entirely fresh, and particularly if that something is likely to be repeatedly visited as time goes on, spending a bit of preliminary time to get the full lay of the land is time well spent.  Once you know what you're skipping/missing by interrupting the screen reader, that's fine, but not so much before.  I've had way more than one, "I never knew that was there," declaration because the user had never once allowed the screen reader to read through, from beginning to end.  And this was often after years of having used the venue where that previously unknown thing has always been present.

I guess this is a meta version of "tool to task."  When something's new, taking the time to listen more than you ever will again is often helpful.  When something's not new, shushing the screen reader and getting straight to where you want to be is most often the better course of action.
--

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)