Date   

Remotely controlling a computer with zoom while using NVDA

mohammad suliman
 

Hello all,
Hope all are doing well!

I have some question regarding zoom and NVDA: I am interested to remotely control a computer with zoom, but I have a problem doing so because to do this, I need to click with the mouse in the shared screen area of the person I want to control his / her machine. So I am wondering if there is a way to do this with NVDA accessibly? Has anyone done this successfully?

Any tip will be appreciated!
thank you!
Mohammad


Re: Switching between 6 and 8 dot UEB: is this possible?

Doug Lawlor
 

Well, this is interesting. Even though I have UEB enabled with both input and output tables i’m still seeing 8 dot braille. When i see something in all capitals, the letters are displayed with capital signs underneath them in the dot 7 position with a single dot 6 in front for a singgle capital letter and a double dot 6 for a word in all capitals. If UEB is only a 6 dot code, should I only see 6 dot braille? I’m really not sure what is going on here. 

Hope to get more light shed on this. 

Best, 

Doug


Re: NVDA and speaking Capital letter

 

On Tue, Jun 2, 2020 at 12:49 AM, zahra wrote:
do you mean that all people including me, should mention our windows
and nvda version when we ask something about nvda, for example: how to
use specific feature of nvda or how to change nvda according to our
desires?
Yep.   As lovely as it would be if we could all read minds, we can't.  If you look at the signature that comes along with every message I write, immediately after my name is the Windows 10 Edition, bit-depth (which is optional, but I would want to know really if someone is still using 32-bit), Version and Build numbers.  In your case for XP that would be service pack level.  If I'm asking a question about NVDA, and I have, I always mention the NVDA version I'm running.  If I have a question in regard to MS-Office, I always mention that I'm using Office 2016 (or Word 2016, etc.).  That's essential information.

When anyone is asking technical questions, the only way that both the person asking and answering can be certain that they're talking about the same things is if those very things are explicitly laid out.

It needn't be long and flowery, just there.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Science has become just another voice in the room; it has lost its platform.  Now, you simply declare your own truth.

      ~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment Took Hold in the United States, September 23, 2019

 

 


Re: NVDA and speaking Capital letter

 

brian, thanks so much for your supports and helps as always.
do you mean that all people including me, should mention our windows
and nvda version when we ask something about nvda, for example: how to
use specific feature of nvda or how to change nvda according to our
desires?
and many new members of this list, dont know me and dont know my history.
and other members may forget my case and i should recall everytime
that i post comment and request or ask something about nvda?

On 6/1/20, Brian Vogel <@britechguy> wrote:
On Mon, Jun 1, 2020 at 01:38 PM, zahra wrote:


as i always mentioned and emphasized, 2017.2 is the best version for me!
Zahra,

First, and most importantly, there are always new members reading you for
the first time that have no idea of your history. Even though I do, even I
didn't recall that it was specifically NVDA 2017.2 where you stopped
upgrading, though I know you continue to use Windows XP. That's why it's
really important for you to repeat, when asking any question, that you are
using NVDA 2017.2 and Windows XP.

There will not be many others, if any, who read here who are in your
situation, but there may be. They would really be the only ones who could
help you with "the details" because most of us long ago went off of NVDA
2017.x and Window XP. You are using an unsupported version of both the
screen reader and Windows operating system, so what you have is what you've
got, and will continue to have, unless some existing setting that you
haven't tweaked (and may not have known about) is identified by someone else
to assist you.

But when you post without any information regarding what you are actually
using, it is the typical expectation that you are using a supported version
of NVDA and Windows by those who do not know or recall otherwise. When you
ask questions omitting that information you are going to end up getting a
lot of answers that will not be applicable to you, which is why I implore
you to routinely include the opening line: Using NVDA 2017.2 on Windows
XP

And this applies generally to everyone. It's really, really important when
asking questions on software that the software version number being used,
and the operating system it's being used under, are included.

--

Brian *-* Windows 10 Pro, 64-Bit, Version 1909, Build 18363

*Science has become just another voice in the room; it has lost its
platform. Now, you simply declare your own truth.*

~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment
Took Hold in the United States (
https://www.nytimes.com/2019/09/23/health/anti-vaccination-movement-us.html
) , September 23, 2019



--
By God,
were I given all the seven heavens
with all they contain
in order that
I may disobey God
by depriving an ant
from the husk of a grain of barley,
I would not do it.
imam ali


Re: SoundForge Users On This List

Angelo Sonnesso
 

You can go to a free option Audacity, or you can use Reaper, which is every bit as good as sonar.
I believe it is $60.00, but I purchased my copy a while ago.
I use both, and they work well.


73 N2DYN Angelo

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Curtis Delzer
Sent: Monday, June 1, 2020 4:23 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] SoundForge Users On This List

sound forge is not a multi-track editor, including sf14 which I own.

Curtis Delzer
HS
K 6 V F O
Rialto, CA

curtis@...

On 5/6/2020 7:44 AM, Fresh Start wrote:
I am currently using version 11 and have used nine for years and didn’t
have any issues. However, I do have a few questions as well.

I had to move to a Windows ten pro. Computer. A program called Sonar
and cake walk don’t work in that environment. It it possible to do
multi-track recordings in Soundforge 11 and above? I would be very
greatful to carry on this conversation off line if allowed so as not to
clog up this list with too many questions. Thanks in advance.

*From:*nvda@nvda.groups.io <nvda@nvda.groups.io> *On Behalf Of *Sean
*Sent:* Tuesday, May 05, 2020 3:12 PM
*To:* nvda@nvda.groups.io
*Subject:* Re: [nvda] SoundForge Users On This List

I'm using version 14 and I had no problem with this.

On 05/05/2020 10:52, Andrea Sherry wrote:

Any users of this program care to comment. When I attemp to change
some of the checkboxes in the menu NVDA does not recognise them as
checkboxes. Has anyone else had this experience? Is there a work round?
Andrea


--


Sean

* Twitter: Friedrich Sargon <https://twitter.com/FriedrichSargon>
* Email: seantolstoyevski@...
<mailto:seantolstoyevski@...>
* GitHub: SeanTolstoyevski <https://github.com/SeanTolstoyevski/>

I’m student and programmer. I write often Python, sometimes Go and rare C++.
I can understand Turkish and English.


Re: SoundForge Users On This List

Curtis Delzer
 

sound forge is not a multi-track editor, including sf14 which I own.

Curtis Delzer
HS
K 6 V F O
Rialto, CA

curtis@...

On 5/6/2020 7:44 AM, Fresh Start wrote:
I am currently using version 11 and have used nine for years and didn’t have any issues.  However, I do have a few questions as well.
I had to move to a Windows ten pro. Computer.  A program called Sonar and cake walk don’t work in that environment.  It it possible to do multi-track recordings in Soundforge 11 and above?  I would be very greatful to carry on this conversation off line if allowed so as not to clog up this list with too many questions.  Thanks in advance.
*From:*nvda@nvda.groups.io <nvda@nvda.groups.io> *On Behalf Of *Sean
*Sent:* Tuesday, May 05, 2020 3:12 PM
*To:* nvda@nvda.groups.io
*Subject:* Re: [nvda] SoundForge Users On This List
I'm using version 14 and I had no problem with this.
On 05/05/2020 10:52, Andrea Sherry wrote:
Any users of this program care to comment. When I attemp to change
some of the checkboxes in the menu NVDA does not recognise them as
checkboxes. Has anyone else had this experience? Is there a work round?
Andrea
--
Sean
* Twitter: Friedrich Sargon <https://twitter.com/FriedrichSargon>
* Email: seantolstoyevski@...
<mailto:seantolstoyevski@...>
* GitHub: SeanTolstoyevski <https://github.com/SeanTolstoyevski/> I’m student and programmer. I write often Python, sometimes Go and rare C++.
I can understand Turkish and English.


Re: NVDA and speaking Capital letter

 

On Mon, Jun 1, 2020 at 01:38 PM, zahra wrote:
as i always mentioned and emphasized, 2017.2 is the best version for me!
Zahra,

         First, and most importantly, there are always new members reading you for the first time that have no idea of your history.  Even though I do, even I didn't recall that it was specifically NVDA 2017.2 where you stopped upgrading, though I know you continue to use Windows XP.   That's why it's really important for you to repeat, when asking any question, that you are using NVDA 2017.2 and Windows XP.

          There will not be many others, if any, who read here who are in your situation, but there may be.  They would really be the only ones who could help you with "the details" because most of us long ago went off of NVDA 2017.x and Window XP.   You are using an unsupported version of both the screen reader and Windows operating system, so what you have is what you've got, and will continue to have, unless some existing setting that you haven't tweaked (and may not have known about) is identified by someone else to assist you.

           But when you post without any information regarding what you are actually using, it is the typical expectation that you are using a supported version of NVDA and Windows by those who do not know or recall otherwise.  When you ask questions omitting that information you are going to end up getting a lot of answers that will not be applicable to you, which is why I implore you to routinely include the opening line:   Using NVDA 2017.2 on Windows XP

            And this applies generally to everyone.  It's really, really important when asking questions on software that the software version number being used, and the operating system it's being used under, are included.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Science has become just another voice in the room; it has lost its platform.  Now, you simply declare your own truth.

      ~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment Took Hold in the United States, September 23, 2019

 

 


Re: NVDA and speaking Capital letter

 
Edited

On Mon, Jun 1, 2020 at 01:36 PM, Marquette, Ed wrote:
I didn’t mean to complain, and I wouldn’t have brought it up separately, but since another brought it up …
Ed,

             Thanks for your kind and measured response.  I want to make clear that it isn't the complaining/venting that's the issue, it's that very often it's the only thing that's happening (and this is addressed to the readership, not you specifically).

             Software development has certain conventions.  We are lucky here because there are actually a couple of members "high up" on the NVAccess team that read regularly, but that's a rare exception rather than the rule, and I'm sure that reading is constrained by more pressing commitments.  One of those conventions is the use of systems such as GitHub to track and respond to issues and suggestions.  In most cases, end users don't even have the ability to touch said systems, there's a middle-man such as the Microsoft Feedback Hub under Windows 10, where that input is then later filtered by others and entered into the actual systems used to track and prioritize issues.

              It is critically important that those reading this list realize just how lucky they are to have a method to go "straight to the source" when they encounter an issue or have a suggestion, then check if it has already been entered by someone else, in which case they should add a comment on to the end of the existing issue as appropriate, even if it's as simple as, "I'm having precisely the same problem/I would like to see this feature implemented as well," or to open a new one.  That's where the proverbial rubber meets the road.

               I have no idea what it may, or may not accomplish, but I went to that very GitHub ticket a short while ago and mentioned that traffic requesting the functionality has been very high recently here on the NVDA Group and that the issue has now been open for six years.  It has has a lot of in-depth comments regarding possible implementation options over that time, but little input from end users regarding the desire/need for said functionality.  Going on record by those who actually do need it bumps up the visibility of "old tickets," and particularly if there is a sudden increase in activity on said tickets.

                I also hadn't recalled that I already put these instructions on my Google Drive so anyone who needs them can download them, but here they are:  Creating a Github Account

 

 
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Science has become just another voice in the room; it has lost its platform.  Now, you simply declare your own truth.

      ~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment Took Hold in the United States, September 23, 2019

 

 


Re: NVDA and speaking Capital letter

 

thanks brian for your comments.
as i always mentioned and emphasized, 2017.2 is the best version for me!
but, u p e n d etc, are pronunced by espeak as single letters rather
than complete word, for me because i use SayAll for reading.
if i navigate word by word, espeak reads capitalized words like the
way which it reads them if they are in small letters!
but i am comfortable reading using SayAll, and its very enjoyable and
pleasant even if i read hundreds or at least tens of pages!

On 6/1/20, Brian Vogel <@britechguy> wrote:
Zahra,

You do not mention the version of NVDA you are using, but I have to presume,
absent any updates, that it's an ancient one. It would still help to know.

NVDA does not generally appear to be case sensitive, and the word up,
rendered in full uppercase as UP, should still be pronounced just like
lowercase up is. Using your example: UP arrow, ENd, TAB

NVDA 2020.1 reads it as up arrow, E N d, tab. I can get why the mixed case
might do this, as the use of multiple capitals mixed with lower case is
difficult to interpret as to whether something's being styled to be read as
separate letters or not. If I change the capital E N followed by lowercase
d to uppercase E, lowercase n, uppercase D, then NVDA says En D, since En is
pronouncable, just like the letter N itself is pronounced, in English.

PhD is pronounced as P H D, just as I'd expect, and just as most readers who
see such after an individual's name would say it.
--

Brian *-* Windows 10 Pro, 64-Bit, Version 1909, Build 18363

*Science has become just another voice in the room; it has lost its
platform. Now, you simply declare your own truth.*

~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment
Took Hold in the United States (
https://www.nytimes.com/2019/09/23/health/anti-vaccination-movement-us.html
) , September 23, 2019



--
By God,
were I given all the seven heavens
with all they contain
in order that
I may disobey God
by depriving an ant
from the husk of a grain of barley,
I would not do it.
imam ali


Re: NVDA and speaking Capital letter

Marquette, Ed
 

Thank you.

I didn’t mean to complain, and I wouldn’t have brought it up separately, but since another brought it up …

But you are right about GitHub, and I’ll try the GitHub site again.  I just have not had the time.

I did try to log into GitHub once before, but something went wrong.  It was not straightforward.  I’ll give it another try when I can focus.   

I saved Quentin’s instructions.

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel via groups.io
Sent: Monday, June 1, 2020 11:29 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA and speaking Capital letter

 

[ CAUTION - EXTERNAL SENDER ]

On Mon, Jun 1, 2020 at 09:47 AM, Marquette, Ed wrote:

The whole interpretation of a contract can turn on the presence of a capital letter, but now one has to stop reading by sentence and manually check the potentially suspect word to see if it is or is not capitalized. This is not just a good thing, it is a crucial thing.

Ed,

          Not that I'm disagreeing with your point, because I'm not, but I will say this again:  Complaining on a user group is not the way to register the need for these changes such that they will be made.

          This very issue was just discussed within the last couple of weeks.  Someone else gave the direct link to the NVDA issue on GitHub regarding same.  Those of you who want this, and I know why you want it, would be spending your time far more effectively by adding a comment to that very issue rather than complaining here.  The number of comments on a given issue in an issue tracking system is one of the primary metrics used to determine how important something is to the user community.  And the NVDA user community has the absolute luxury, and it is one, of having direct access to the issue tracking system used by NVAccess for the product.

          I am no longer going to post links to the results of archive searches.  The membership of this group must, yes, must, learn how to do effective archive searches themselves.  Searching the NVDA Group Archive. A search on the phrase "Capital Letter Recognition" gets you straight to Quentin Christensen's post giving the link to the NVDA issue.  If this is important enough to pursue, then do that search, set up a GitHub account if you don't already have one (and I'll be happy to supply step by step instructions if you need those), and click through to that issue and add your comment.  This is how things get done, and it's up to those who want them done to undertake the steps necessary.  You, in fact, were the individual to whom Quentin was responding, so this should not be news to you.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Science has become just another voice in the room; it has lost its platform.  Now, you simply declare your own truth.

      ~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment Took Hold in the United States, September 23, 2019

 

 

 




This E-mail message is confidential, is intended only for the named recipients above and may contain information that is privileged, attorney work product or otherwise protected by applicable law. If you have received this message in error, please notify the sender at 402-346-6000 and delete this E-mail message. Thank you.


Re: NVDA and speaking Capital letter

 

On Mon, Jun 1, 2020 at 09:47 AM, Marquette, Ed wrote:
The whole interpretation of a contract can turn on the presence of a capital letter, but now one has to stop reading by sentence and manually check the potentially suspect word to see if it is or is not capitalized. This is not just a good thing, it is a crucial thing.
Ed,

          Not that I'm disagreeing with your point, because I'm not, but I will say this again:  Complaining on a user group is not the way to register the need for these changes such that they will be made.

          This very issue was just discussed within the last couple of weeks.  Someone else gave the direct link to the NVDA issue on GitHub regarding same.  Those of you who want this, and I know why you want it, would be spending your time far more effectively by adding a comment to that very issue rather than complaining here.  The number of comments on a given issue in an issue tracking system is one of the primary metrics used to determine how important something is to the user community.  And the NVDA user community has the absolute luxury, and it is one, of having direct access to the issue tracking system used by NVAccess for the product.

          I am no longer going to post links to the results of archive searches.  The membership of this group must, yes, must, learn how to do effective archive searches themselves.  Searching the NVDA Group Archive. A search on the phrase "Capital Letter Recognition" gets you straight to Quentin Christensen's post giving the link to the NVDA issue.  If this is important enough to pursue, then do that search, set up a GitHub account if you don't already have one (and I'll be happy to supply step by step instructions if you need those), and click through to that issue and add your comment.  This is how things get done, and it's up to those who want them done to undertake the steps necessary.  You, in fact, were the individual to whom Quentin was responding, so this should not be news to you.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Science has become just another voice in the room; it has lost its platform.  Now, you simply declare your own truth.

      ~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment Took Hold in the United States, September 23, 2019

 

 


Re: NVDA and speaking Capital letter

 

Zahra,

             You do not mention the version of NVDA you are using, but I have to presume, absent any updates, that it's an ancient one.  It would still help to know.

              NVDA does not generally appear to be case sensitive, and the word up, rendered in full uppercase as UP, should still be pronounced just like lowercase up is.  Using your example:  UP arrow, ENd, TAB

NVDA 2020.1 reads it as up arrow, E N d, tab.  I can get why the mixed case might do this, as the use of multiple capitals mixed with lower case is difficult to interpret as to whether something's being styled to be read as separate letters or not.  If I change the capital E N followed by lowercase d to uppercase E, lowercase n, uppercase D, then NVDA says En D, since En is pronouncable, just like the letter N itself is pronounced, in English.

PhD is pronounced as P H D, just as I'd expect, and just as most readers who see such after an individual's name would say it.
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Science has become just another voice in the room; it has lost its platform.  Now, you simply declare your own truth.

      ~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment Took Hold in the United States, September 23, 2019

 

 


Re: NVDA and speaking Capital letter

Marquette, Ed
 

This is inaccurate. Whether a group of letters is pronounced as a word is a function of the rules of phonetics, as Brian says. Capitalization is irrelevant.
For instance, spx and SPX are pronounced the same way, even though one is in capital letters and one is not.
I hate to sound like a broken record, but what NVDA needs is not a rule about enunciating letters when words are in solid caps, but instead, capital recognition when reading by line, sentence, or paragraph. For instance, I do not care how spx is pronounced, but I would like to know when SPX is in all caps.
Presently, there is no way to distinguish between the two in NVDA, except by reading by character.
Similarly, when reading a legal document, a "Party" with a capital letter is likely a signatory to the contract; a "party" in lower case often is not. The whole interpretation of a contract can turn on the presence of a capital letter, but now one has to stop reading by sentence and manually check the potentially suspect word to see if it is or is not capitalized. This is not just a good thing, it is a crucial thing.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of zahra via groups.io
Sent: Monday, June 1, 2020 12:57 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA and speaking Capital letter

[ CAUTION - EXTERNAL SENDER ]

brian, in espeak, how can i set it to pronunce capital letters as small letters?
for example: if all or most letters in words are in capital letters, nvda reads them letter by letter.
for example:
UP arrow, ENd, TAB, etc.

On 6/1/20, Brian Vogel <@britechguy> wrote:
Although I can't speak definitively, I'd have to guess that what
determines whether an acronym in all capital letters gets spoken as a
word is whether the letters in the sequence can be pronounced under
the rules of English phonotactics or not. Using your example D A X
together can be spoken as dacks. There is no way, under the rules of
English phonotactics that SPX can be pronounced as a word. It has to be rendered letter by letter.
Another example is NASA, which can be pronounced as a word, versus
LPG, which cannot.

I know of regular expressions you could use to recognize all capital
letter acronyms in a fixed number of characters, say 3 or 4 or 5, and
pronounce those as their individual letters, but I do not know how to
do this for an indeterminate number of sequential capital letters.
You'd also have to be somewhat careful about this, since it can
quickly drive you crazy if you're reading a document that has lots of
pronouncable acronyms and you end up having them broken into letters
every time. It would drive me insane to hear NASA pronounced as N A S
A were I reading anything that refers to the U.S. National
Aeronautical and Space Administration repeatedly by its well-known acronym.
--

Brian *-* Windows 10 Pro, 64-Bit, Version 1909, Build 18363

*Science has become just another voice in the room; it has lost its
platform. Now, you simply declare your own truth.*

~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine
Sentiment Took Hold in the United States (
https://www.nytimes.com/2019/09/23/health/anti-vaccination-movement-us.html
s.com
) , September 23, 2019




--
By God,
were I given all the seven heavens
with all they contain
in order that
I may disobey God
by depriving an ant
from the husk of a grain of barley,
I would not do it.
imam ali






This E-mail message is confidential, is intended only for the named recipients above and may contain information
that is privileged, attorney work product or otherwise protected by applicable law. If you have received this
message in error, please notify the sender at 402-346-6000 and delete this E-mail message.
Thank you.


Monthly Group Rules Reminder for the NVDA Group (nvda@nvda.groups.io)

nvda@nvda.groups.io Group Moderators <nvda@...>
 

NVDA Group Description:  NonVisual Desktop Access (NVDA) is screen reader software.  The central purpose of this group is discussing how to use NVDA, either configuring NVDA's settings or familiarizing oneself with its modes and commands.  Discussions about which programs are accessible using NVDA, NVDA add-ons, NVDA tutorials and documentation, and configuring synthesizers or Braille displays for use with NVDA are also permitted.

What follows is the NVDA Group Monthly Reminder Notice, which is meant to reacquaint members with the NVDA Group Rules.

Although the following rule has almost never needed to be applied, the Group Owner and Moderators reserve the right to block, edit, or remove any message at any time at our sole discretion.  Messages that have content that violates the Groups.io Terms of Service are not permitted, are subject to immediate removal, and the member posting same to be placed on moderated status or banned, at the sole discretion of the Group Owner or Moderator. 

It is presumed that the majority of members will be using NVDA, and possibly other screen readers, as part of their daily routine.  This being the case, before you post a message you have to consider whether the question you are about to ask is actually about NVDA itself, or about the program you’re using it to access.  Questions of the form, How do I use . . . with NVDA?, are very seldom about NVDA, but are almost always about the program being accessed with NVDA.

The NVDA Group has a Chat Subgroup (see: https://nvda.groups.io/g/chat, Group Email Addresses section) that has as its purpose the asking of virtually any “off-topic” question about anything you can think of, including just socializing.  It should be used for exactly that purpose. The Chat Subgroup has generally had technically focused topics related to using features of the programs that one is using NVDA to access or about other programs that have proven helpful.  Only those who are already members of the NVDA Group can subscribe to the Chat Subgroup.  

Before choosing where to post, please ask yourself the question, “Is what I’m about to ask or offer directly related to controlling or using NVDA, or whether a specific program is accessible with NVDA?”  If that can be answered, “Yes,” then post to the NVDA Group, and if the answer is, “No,” then the topic belongs in the NVDA Chat Subgroup.

In order to make your experience, and those of all other members, as pleasant as they can be, please follow these practices:

1.  Use threaded or conversation view in your e-mail client program or webmail and reading through the entirety of a topic before replying.  It gets you completely up to speed and avoids a lot of repetition.  If you choose not to use threaded/conversation view, please take the time to read through all messages from the group that are in your inbox prior to adding any reply to the group.  It’s the only way you can be sure you’re up to speed on any topic when not using threaded/conversation view.

2.  Reading through all new topics before replying, as topics have a tendency to get split upon occasion and often an answer ends up being in a separate topic.

3. If you have reason to believe your question has likely been asked and answered in the past please search the Group Archive first before asking it again.  Step-by-Step instructions for searching the group archive using the Groups.io search or a web search engine of your choosing: Searching_the_NVDA_Group_Archive.docx.  Please consider using a web search first for questions that have almost certainly been asked frequently and for which myriad answers, often in the form of tutorials, already exist.

4.  Think very carefully about the title you are going to give any topic you post.  The topic is the first (and, sometimes, only) thing a member sees and that may be how they decide if they’re going to look further.   Generic titles, such as “Help Me!,” are not helpful because they give no idea about what.  Compare that to something like, “NVDA not reading Excel cell contents,” or, “NVDA setting for pronouncing numbers,” where the exact issue where help is needed is front and center.   Even something like, “Need help with the following . . .,” lets the reader know that you are going to present a list of issues.

5.  Please avoid, “What is the best . . .?,” topics, because what qualifies as “best” is entirely subjective.   Topics of this sort are also always chat topics.  If you know you have specific needs then asking, “What {insert program type here} has the following features . . .,” is much more descriptive.   If you want to know what programs people like for a specific task, asking, “What’s your favorite . . . and why?,” is far more likely to get you the details you want to have.  Notice that none of the above questions ask about whether a program is accessible with NVDA.  If you’re asking something like, “Which {insert program class here} is accessible with NVDA?,” then it’s a main group topic.

6.  Any topic that is not about using NVDA to accomplish a task, or how to control NVDA, belongs in the chat subgroup, not the main group.  All questions about how to use the specific features of a program that you’re using NVDA to access, but not about NVDA itself, belong in the chat subgroup.

 

Respectful, even if slightly heated, disagreements will occur occasionally and will be tolerated provided what is described next does not occur.  Flaming, name calling, instigating arguments for their own sake that do nothing to advance anyone’s knowledge, pointed rudeness, and similar boorish behavior will not be tolerated.  If at any point one of you happens upon a message anywhere in the NVDA Group sphere, main or chat, that fits the preceding description then please report it to the group owner either via e-mail at, nvda+owner@nvda.groups.io, or, if you read via the web interface at https://nvda.groups.io/g/nvda/topics, then use the Report this message option that’s a part of the More button at the end of each message.  Please don’t add a protest message the topic.  If we receive a report and agree with it, the issue will be taken care of promptly.

 

If you find the amount of traffic from this Group, or any Groups.io group, overwhelming, then please download and read:

Controlling the Messages You Receive via E-Mail from Groups.io (docx)

Controlling the Messages You Receive via E-Mail from Groups.io (PDF)

Each of you has the ability to mute topics that don’t interest you, get digests instead of individual messages, or to set up topic preview for yourself via the Following Only and First Messages Also features used in conjunction with each other.  It is up to you to use those to manage your e-mail as you see fit.  It’s almost certain that there will be plenty of topics on the chat subgroup that will not be of the least interest to you as an individual. Setting up topic preview lets you pick and choose what you want to continue to see, and this function can be used on any Groups.io group.

A recap of the specific e-mail addresses for the NVDA Group:

 

To see and modify all of the groups you are subscribed to, go to https://groups.io 

 

Sincerely,

Nimer Jaber                                     Brian Vogel

NVDA Group Owner                      NVDA Group Moderator

 

To learn more about the NVDA Group, please visit https://nvda.groups.io/g/nvda

To start sending messages to members of this group, send email to nvda@nvda.groups.io 

If you do not wish to belong to the NVDA Group, you may unsubscribe by sending an email to nvda+unsubscribe@nvda.groups.io 

To see and modify all of your groups, go to https://groups.io 


Speak On in the Cloud

David Griffith
 

Further to Isaac’s update of the Add on and Speech Hub I have completed 2 Podcasts showing Cloud application of Speak On.

The next 2 Speak On Podcasts focusing on Cloud application. These will eventually appear on the Talking Computer Feed but advance listening is available below.

 

10 Speak On in the Cloud Part 1

In this Podcast we see how to create a Portable version of Speak On which , when applied to DropBox and OneDrive allows the synchronisation of reading of media across multiple Windows devices.

 

https://www.sendspace.com/pro/dl/rnbhp3

https://www.dropbox.com/s/3lzjrnu6dnzb40c/10%20Speak%20On%20in%20the%20Cloud%20Part%201.mp3?dl=1

 

Speak On Portable Install - With TTS change to Sapi 5 and media folders created ready to receive content.

https://www.dropbox.com/sh/4q4g8vgkk8eb1tk/AAAYwrnDHg3aRcmredfefttVa?dl=1

11 Speak On in the Cloud Part 2

In this Podcast we demonstrate how our cloud version of Speak On can perform on both DropBox and OneDrive from another Windows device. It shows how reading is synchronised across devices.  The podcast  covers the particular settings needed in OneDrive for the cloud based version of Speak ON to work.

 

https://www.sendspace.com/pro/dl/6fzsx1

https://www.dropbox.com/s/lrwjck28b5zeg0b/11%20Speak%20On%20in%20the%20Cloud%20Part%202.mp3?dl=1

 

 

 


Re: Switching between 6 and 8 dot UEB: is this possible?

Ikrami
 

UEB is a 6-dot braille code only, there is no 8-dot version of it. You can though switch to the US 8-dot computer braille.

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Doug Lawlor via groups.io
Sent: Monday, June 1, 2020 1:56 PM
To: nvda@nvda.groups.io
Subject: [nvda] Switching between 6 and 8 dot UEB: is this possible?

 

Hello all,

I want to switch between 6 and 8 dot Unified English Braille. Is this possible to do? I took a look at the table list in NVDA’S braille settings but can only find 6 dot tables for computer braille. I’m looking for literary braille.


Thanks in advance all,

Doug


Switching between 6 and 8 dot UEB: is this possible?

Doug Lawlor
 

Hello all,

I want to switch between 6 and 8 dot Unified English Braille. Is this possible to do? I took a look at the table list in NVDA’S braille settings but can only find 6 dot tables for computer braille. I’m looking for literary braille.


Thanks in advance all,

Doug


Re: NVDA and speaking Capital letter

 

brian, in espeak, how can i set it to pronunce capital letters as small letters?
for example: if all or most letters in words are in capital letters,
nvda reads them letter by letter.
for example:
UP arrow, ENd, TAB, etc.

On 6/1/20, Brian Vogel <@britechguy> wrote:
Although I can't speak definitively, I'd have to guess that what determines
whether an acronym in all capital letters gets spoken as a word is whether
the letters in the sequence can be pronounced under the rules of English
phonotactics or not. Using your example D A X together can be spoken as
dacks. There is no way, under the rules of English phonotactics that SPX
can be pronounced as a word. It has to be rendered letter by letter.
Another example is NASA, which can be pronounced as a word, versus LPG,
which cannot.

I know of regular expressions you could use to recognize all capital letter
acronyms in a fixed number of characters, say 3 or 4 or 5, and pronounce
those as their individual letters, but I do not know how to do this for an
indeterminate number of sequential capital letters. You'd also have to be
somewhat careful about this, since it can quickly drive you crazy if you're
reading a document that has lots of pronouncable acronyms and you end up
having them broken into letters every time. It would drive me insane to
hear NASA pronounced as N A S A were I reading anything that refers to the
U.S. National Aeronautical and Space Administration repeatedly by its
well-known acronym.
--

Brian *-* Windows 10 Pro, 64-Bit, Version 1909, Build 18363

*Science has become just another voice in the room; it has lost its
platform. Now, you simply declare your own truth.*

~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment
Took Hold in the United States (
https://www.nytimes.com/2019/09/23/health/anti-vaccination-movement-us.html
) , September 23, 2019



--
By God,
were I given all the seven heavens
with all they contain
in order that
I may disobey God
by depriving an ant
from the husk of a grain of barley,
I would not do it.
imam ali


Re: speechhub add-on installation error

Robert Mendoza
 

Sorry if interrupted this thread but, just curious.

What exactly does with SpeechHub differs from eSpeak?

Do they have other voices as well?

On 5/31/2020 11:43 PM, Isaac Porat wrote:
Hello

I am glad it works now for you.

The NVDA add-on installation page:
http://www.speakon.org.uk/SpeechHub/public/docs/NVDAClient/NVDADownloadInstallation.html

States clearly that SpeechHub (there is a link to the installer on the same page as well) needs to be installed first.

When you install the SpeechHub NVDA add-on it checks that SpeechHub is there it runs a test on it and if all is well it completes the add-on installation.

Installed in the above sequence I did not receive a single report on an add-on failure.

Regarding it's synthesizers, I am not sure I understand your question about finding these:
Press [NVDA + Ctrl + s] and the list is there, there are five SpeechHub synthesizers by default group together clearly distinguished by the word 'SpeechHub'.

Regards
Isaac


On 31/05/2020 06:14, Aschalew Byness wrote:
I am now able to install it! I was stupid that I didn’t install
SpeechHub exe first. This was the cause for the problem.
I have another question though. I didn’t find SpeechHub synthesizer as
fast as eSpeak or eloquence synthesizer. Anything I should do for
this?



On 5/31/20, Aschalew Byness via groups.io
<gakidan.ashagre235=gmail.com@groups.io> wrote:
No, I couldn't find it in the installed add-on list.

On 5/31/20, Brian Vogel <@britechguy> wrote:
Double check in Add-Ons Manager (NVDA+N,T,A,Enter) to see whether it's
actually not there.

I received a message to the same effect about Speech History when I tried
to
install it two days ago (I think) and mentioned that here on the group.
Even though I got that error it appears to have been spurious, as the
Speech
History add-on is shown as installed and enabled in Add-Ons Manager.

Please report back on your findings.
--

Brian *-* Windows 10 Pro, 64-Bit, Version 1909, Build 18363

*Science has become just another voice in the room; it has lost its
platform.  Now, you simply declare your own truth.*

~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine
Sentiment
Took Hold in the United States (
https://www.nytimes.com/2019/09/23/health/anti-vaccination-movement-us.html
) , September 23, 2019






Re: NVDA and speaking Capital letter

 

Yes, that would be the regex, and the replacement would be \1 \2 \3
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Science has become just another voice in the room; it has lost its platform.  Now, you simply declare your own truth.

      ~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment Took Hold in the United States, September 23, 2019