Date   
Microsoft word: determine bullet shapes with NVDA

Vincent Le Goff
 

Hi everyone,


I'm working with Microsoft Word a lot these days.  I like to have consistent documents and try to create visually-attracting ones when I can, with headers and footers and nice tables and so on. I'm following the guide to Microsoft Word with NVDA, which is very useful.  However, one thing I can't figure out how to do: when in a bulleted list, how do you know what bullet is used?  I like to use the same kind for all my ordered list.  As far as I know, when trying to avoid standard bullets (I personally like the "filled square" one), Word relies on numbers (like bullet 318) when you try to insert.  But does NVDA reports the kind of bullet used? And if so, how?  This information doesn't seem to be present in NVDA+F.  On the other hand, I think one cannot focus the bullets to "see" what they are, though I might be mistaken about that.


As someone who doesn't and can't use the speech output, relying on just auditory indications isn't going to work, though I can still use the speech viewer if needed.


Thanks for your help,


Vincent

Re: Creating a new synthesizer

Quentin Christensen
 

Thank you Reece,

This is an excellent set of resources!

And yes, developing a TTS is a very extensive job, which is pretty much the main reason we didn't get to polishing speech player.

The code is freely available and it is open source if anyone is interested in working on it.

Kind regards

Quentin.

On Fri, Sep 13, 2019 at 5:04 PM Reece H. Dunn <msclrhd@...> wrote:

I'll have more later, but here is a start (welcome to the rabbit hole).

A speech synthesizer voice typically consists of two parts:
1.  the text to phonemes part;
2.  the phonemes to audio part.

The text to phonemes part typically consists of a dictionary mapping words to phonemes and a set of rules for how to pronounce certain word patterns (like "EE" in English).

Phonemes (General)
1.  https://en.wikipedia.org/wiki/International_Phonetic_Alphabet -- used by linguists for transcribing languages (see also all the references from this for phoneme theory)
1.  https://en.wikipedia.org/wiki/Lexical_set (English)
1.  https://en.wikipedia.org/wiki/International_Phonetic_Alphabet_chart_for_English_dialects -- see also the different IPA references for a given language

Phoneme Transcription Schemes
1.  https://www.phon.ucl.ac.uk/home/sampa/ -- Language-specific SAMPA transcriptions; used by MBROLA voices
1.  https://en.wikipedia.org/wiki/ARPABET -- Used as the basis of the CMU/FestVox voices
1.  https://github.com/espeak-ng/espeak-ng/blob/master/docs/phonemes/cxs.md -- Conlang X-SAMPA
1.  https://github.com/espeak-ng/espeak-ng/blob/master/docs/phonemes/kirshenbaum.md -- Kirshenbaum / ASCII-IPA
1.  https://github.com/espeak-ng/espeak-ng/blob/master/docs/phonemes/xsampa.md -- X-SAMPA

Pronunciation Dictionaries
1.  https://github.com/rhdunn/cmudict-tools -- python tools for working with CMU dictionary like pronunciation dictionaries
1.  https://github.com/rhdunn/cmudict -- historical view of the CMU pronunciation dictionary for American English
1.  https://github.com/rhdunn/amepd -- my attempts to clean up and extend the cmudict to make it more consistent

Formant Synthesizers
1.  http://www.fon.hum.uva.nl/david/ma_ssp/2010/Klatt-1980-JAS000971.pdf -- Dennis Klatt's original 1980 paper
1.  http://www.fon.hum.uva.nl/david/ma_ssp/doc/Klatt-1990-JAS000820.pdf -- Dennis Klatt's follow up 1990 paper

Creating a Voice
1.  http://festvox.org/cmu_arctic/ -- A set of 7 English voices with US, Canadian, Indian, and Scottish accents
1.  http://festvox.org/festvox/festvox_toc.html -- FestVox documentation on building a voice
1.  https://github.com/numediart/MBROLATOR -- MBROLA documentation on creating a voice
1.  https://github.com/espeak-ng/espeak-ng/blob/master/docs/add_language.md -- eSpeak NG docs on adding a language; the other docs in the docs folder contains more information, and the documentation can definitely be improved



--
Quentin Christensen
Training and Support Manager

Re: NVDA command to copy a link

Chris Mullins
 

Hi

Just for the sake of clarity, I would like to point out that there is no NVDA command to perform this task, all the solutions proposed are Windows commands.

 

Cheers

Chris

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Pascal Lambert
Sent: 13 September 2019 01:58
To: nvda@nvda.groups.io
Subject: [nvda] NVDA command to copy a link

 

Hi,

Please is there an NVDA command to copy a link?

Many thanks

Blessings

Pascal

Re: Equalizer APO

Robert Doc Wright godfearer
 

I must have missed this thread. Where can I find this E Q?

 

 ******

Jesus says, follow me and I'll help you through the rough spots.

the world says, hey come with me. My way is broad and easy. So what if you get crap on your shoes. You can always wash it off, can't you!                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           Sent from Mail for Windows 10

 

From: Orlando Enrique Fiol via Groups.Io
Sent: Friday, September 13, 2019 12:54 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Equalizer APO

 

At 04:47 PM 9/8/2019, Jaffar Sidek wrote:

>Yes it is free.  You can download it hear:

 

 

Not only is it free, but there are two ways to configure equalizers

and filters. One is with the program's editor, which is a dialogue

with buttons and edit boxes. The other, which is much more powerful,

is simply to edit the text files in the Config directory. Yes, they

are plain text files. If you're editing and want to hear how things

sound while you tweak values, simply press save and the settings will

be instantly updated. Great stuff!

Orlando Enrique Fiol

 

 

 

 

Re: Creating a new synthesizer

Reece H. Dunn
 


I'll have more later, but here is a start (welcome to the rabbit hole).

A speech synthesizer voice typically consists of two parts:
1.  the text to phonemes part;
2.  the phonemes to audio part.

The text to phonemes part typically consists of a dictionary mapping words to phonemes and a set of rules for how to pronounce certain word patterns (like "EE" in English).

Phonemes (General)
1.  https://en.wikipedia.org/wiki/International_Phonetic_Alphabet -- used by linguists for transcribing languages (see also all the references from this for phoneme theory)
1.  https://en.wikipedia.org/wiki/Lexical_set (English)
1.  https://en.wikipedia.org/wiki/International_Phonetic_Alphabet_chart_for_English_dialects -- see also the different IPA references for a given language

Phoneme Transcription Schemes
1.  https://www.phon.ucl.ac.uk/home/sampa/ -- Language-specific SAMPA transcriptions; used by MBROLA voices
1.  https://en.wikipedia.org/wiki/ARPABET -- Used as the basis of the CMU/FestVox voices
1.  https://github.com/espeak-ng/espeak-ng/blob/master/docs/phonemes/cxs.md -- Conlang X-SAMPA
1.  https://github.com/espeak-ng/espeak-ng/blob/master/docs/phonemes/kirshenbaum.md -- Kirshenbaum / ASCII-IPA
1.  https://github.com/espeak-ng/espeak-ng/blob/master/docs/phonemes/xsampa.md -- X-SAMPA

Pronunciation Dictionaries
1.  https://github.com/rhdunn/cmudict-tools -- python tools for working with CMU dictionary like pronunciation dictionaries
1.  https://github.com/rhdunn/cmudict -- historical view of the CMU pronunciation dictionary for American English
1.  https://github.com/rhdunn/amepd -- my attempts to clean up and extend the cmudict to make it more consistent

Formant Synthesizers
1.  http://www.fon.hum.uva.nl/david/ma_ssp/2010/Klatt-1980-JAS000971.pdf -- Dennis Klatt's original 1980 paper
1.  http://www.fon.hum.uva.nl/david/ma_ssp/doc/Klatt-1990-JAS000820.pdf -- Dennis Klatt's follow up 1990 paper

Creating a Voice
1.  http://festvox.org/cmu_arctic/ -- A set of 7 English voices with US, Canadian, Indian, and Scottish accents
1.  http://festvox.org/festvox/festvox_toc.html -- FestVox documentation on building a voice
1.  https://github.com/numediart/MBROLATOR -- MBROLA documentation on creating a voice
1.  https://github.com/espeak-ng/espeak-ng/blob/master/docs/add_language.md -- eSpeak NG docs on adding a language; the other docs in the docs folder contains more information, and the documentation can definitely be improved

Re: Equalizer APO

Orlando Enrique Fiol
 

At 04:47 PM 9/8/2019, Jaffar Sidek wrote:
Yes it is free. You can download it hear:

Not only is it free, but there are two ways to configure equalizers and filters. One is with the program's editor, which is a dialogue with buttons and edit boxes. The other, which is much more powerful, is simply to edit the text files in the Config directory. Yes, they are plain text files. If you're editing and want to hear how things sound while you tweak values, simply press save and the settings will be instantly updated. Great stuff!
Orlando Enrique Fiol

Re: Creating a new synthesizer

 

I remember the site I'm about to give you form ages ago. They are still at it. This is from a slightly different angle than what you might be looking for. Here it is:

www.modeltalker.org





On 9/13/2019 12:23 AM, Quentin Christensen wrote:
Hi everyone,

We get asked about creating a new synthesizer from time to time - either simply for ANY synthesizer to support a particular language, or someone wants to create a brand new one, perhaps with their own voice.

Normally I suggest looking at the eSpeak NG project as a starting point.  I was wondering, does anyone have any useful links on how to go about this, that I can pass on when I get such inquiries, please?

I appreciate it's a very complex undertaking, which is why I'm asking here.  If I'm going to pass on anything, I'd rather pass on something of some quality, rather than just a random link off eBay.

Kind regards

Quentin.

--
Quentin Christensen
Training and Support Manager

Re: Creating a new synthesizer

Luke Davis
 

On Fri, 13 Sep 2019, Gene wrote:

JAWS and Window-eyes used almost identical synthesizers, among the largest in the business in earlier days.  JAWS used Eloquence, not its own developed
synthesizer.  Window-eyes used Via Voice, almost identical in sound and performance, whatever technical difference the two synthesizers had. 
Which was developed by IBM.

Ironically, the IBM Screenreader didn't even use their own speech, they used DEC hardware. The Myna palmtop, for example, back in the 90s, used the IBM screenreader and a torn-down DECTalk Express.

System Access to Go used Via Voice.  DOS screen-readers didn't have their own speech.  They supported a lot of synthesizers but they didn't come bundled
with one.
At least one did. Tiny Talk, by Eric Poelman (forgive me if I got his name wrong--it's been fifteen years since I had to remember that), could use the software speech available on a SB16 sound card. Remember Doctor Sbaitso, anyone? It could use that voice, which makes the worst robotic Espeak voice sound like silk.

https://en.wikipedia.org/wiki/Dr._Sbaitso

Luke

Re: Creating a new synthesizer

Luke Davis
 

On Fri, 13 Sep 2019, Shaun Everiss wrote:

Even though thats strictly no longer necessary anymore, some old habbits die hard.
Habit is no good reason to do a massive undertaking. As Gene said, unless we can make something worth having--I.E. better than Espeak in some fundamental way--what's the point? Bragging rights is not enough, if nobody actually wants what we're bragging about.

I would like us on nvda to have our own synth, because we started it and because we can and why not.
Gene already explained why not. It may not be a satisfactory answer--personally i would love for SpeechPlayer to be a viable synth that brings something interesting to the table--but the simple fact is that speech synth development takes a dedicated team of linguistic experts, audio experts, programmers, and years of effort dedicated to nothing else. NV Access has four people, and they have the task of overseeing the entire screen reader. If you can't give such an effort the development resources it deserves, you end up with an experiment and a novelty, which is what SpeechPlayer became.

It would be very nice if it could have been more, and maybe something will still happen one day, but there are so many good speech synth options right now, that the urgency and justification for dedicating the astonishingly limited resources available to such a project, just isn't there.

If someone wants to fund a team to do this development work, I'm sure NV Access would be happy to reconsider its priority; but until somebody does, it seems unlikely, for good reason, to continue at any kind of pleasing momentum.

Luke

Re: Creating a new synthesizer

Gene
 

JAWS and Window-eyes used almost identical synthesizers, among the largest in the business in earlier days.  JAWS used Eloquence, not its own developed synthesizer.  Window-eyes used Via Voice, almost identical in sound and performance, whatever technical difference the two synthesizers had. 
 
System Access to Go used Via Voice.  DOS screen-readers didn't have their own speech.  They supported a lot of synthesizers but they didn't come bundled with one.
 
Gene

----- Original Message -----
Sent: Friday, September 13, 2019 12:21 AM
Subject: Re: [nvda] Creating a new synthesizer

True, but my point was that just about every screen reader at least in the old days had their own flagship synth of choice right back to the dos days.

Just like every soundcard had an fm midi chip.

Even though thats strictly no longer necessary anymore, some old habbits die hard.

I would like us on nvda to have our own synth, because we started it and because we can and why not.

Just about everyone else had one, maybe not so much now but I remember the days when sound cards had fm midi chips and when you used x synth for x program.

Thats a bit more fluid now days but even so.



On 13/09/2019 5:15 pm, Sky Mundell wrote:

It would be wonderful if Speech Player could be developed again. I should also add that in the other comertial products you mentioned they did allow you to change the synthesizers and NVDA allows you to change the synthesizers as well.

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Shaun Everiss
Sent: Thursday, September 12, 2019 10:13 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Creating a new synthesizer

 

You know that really does bring up an interesting project which seems forgotton.

What happened to our own synth the one called speech player.

Why did we stop developing it or did nv access stop developing it.

It probably won't be compatible with 1903 but thats utterly useless if development has stopped, so maybe we should start doing that again.

I mean I like espeak ng but just about every screen reader company has their own synth.

Dolphin uses orpheus, jaws uses eloquence.

Windoweyes used dectalk, microsoft stuff used microsoft stuff.

Nuance used vocaliser and eloquence for talks.

True, we use espeak which is used with linux as well but the point we started our own synth, and I think we should continue.

For whatever reason it just stopped.

The synth was ok sounding, probably a bit outdated and crappy now but still we really should bring it back for bragging rights at least.

 

 

On 13/09/2019 4:23 pm, Quentin Christensen wrote:

Hi everyone,

 

We get asked about creating a new synthesizer from time to time - either simply for ANY synthesizer to support a particular language, or someone wants to create a brand new one, perhaps with their own voice.

 

Normally I suggest looking at the eSpeak NG project as a starting point.  I was wondering, does anyone have any useful links on how to go about this, that I can pass on when I get such inquiries, please?

 

I appreciate it's a very complex undertaking, which is why I'm asking here.  If I'm going to pass on anything, I'd rather pass on something of some quality, rather than just a random link off eBay.

 

Kind regards

 

Quentin.

 

--

Quentin Christensen
Training and Support Manager

 

Re: Creating a new synthesizer

 

Probably not, but still we started.

Why did we stop.



On 13/09/2019 5:17 pm, Gene wrote:
Bragging rites mean nothing unless the product is superior.  People don't care if NVDA has its own synthesizer or not and resources can be much better used.  It is a very specialized area to create a really good synthesizer and NVDA doesn't have the expertise or the resources to divert to such a product. 
 
JAWS never had its own voice.  Neither did Window-eyes nor does System Access.  Clearly, this is hardly something screen-reader developers or the consuming public are concerned about.
 
Gene
----- Original Message -----
Sent: Friday, September 13, 2019 12:12 AM
Subject: Re: [nvda] Creating a new synthesizer

You know that really does bring up an interesting project which seems forgotton.

What happened to our own synth the one called speech player.

Why did we stop developing it or did nv access stop developing it.

It probably won't be compatible with 1903 but thats utterly useless if development has stopped, so maybe we should start doing that again.

I mean I like espeak ng but just about every screen reader company has their own synth.

Dolphin uses orpheus, jaws uses eloquence.

Windoweyes used dectalk, microsoft stuff used microsoft stuff.

Nuance used vocaliser and eloquence for talks.

True, we use espeak which is used with linux as well but the point we started our own synth, and I think we should continue.

For whatever reason it just stopped.

The synth was ok sounding, probably a bit outdated and crappy now but still we really should bring it back for bragging rights at least.



On 13/09/2019 4:23 pm, Quentin Christensen wrote:
Hi everyone,

We get asked about creating a new synthesizer from time to time - either simply for ANY synthesizer to support a particular language, or someone wants to create a brand new one, perhaps with their own voice.

Normally I suggest looking at the eSpeak NG project as a starting point.  I was wondering, does anyone have any useful links on how to go about this, that I can pass on when I get such inquiries, please?

I appreciate it's a very complex undertaking, which is why I'm asking here.  If I'm going to pass on anything, I'd rather pass on something of some quality, rather than just a random link off eBay.

Kind regards

Quentin.

--
Quentin Christensen
Training and Support Manager

Re: Creating a new synthesizer

 

True, but my point was that just about every screen reader at least in the old days had their own flagship synth of choice right back to the dos days.

Just like every soundcard had an fm midi chip.

Even though thats strictly no longer necessary anymore, some old habbits die hard.

I would like us on nvda to have our own synth, because we started it and because we can and why not.

Just about everyone else had one, maybe not so much now but I remember the days when sound cards had fm midi chips and when you used x synth for x program.

Thats a bit more fluid now days but even so.



On 13/09/2019 5:15 pm, Sky Mundell wrote:

It would be wonderful if Speech Player could be developed again. I should also add that in the other comertial products you mentioned they did allow you to change the synthesizers and NVDA allows you to change the synthesizers as well.

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Shaun Everiss
Sent: Thursday, September 12, 2019 10:13 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Creating a new synthesizer

 

You know that really does bring up an interesting project which seems forgotton.

What happened to our own synth the one called speech player.

Why did we stop developing it or did nv access stop developing it.

It probably won't be compatible with 1903 but thats utterly useless if development has stopped, so maybe we should start doing that again.

I mean I like espeak ng but just about every screen reader company has their own synth.

Dolphin uses orpheus, jaws uses eloquence.

Windoweyes used dectalk, microsoft stuff used microsoft stuff.

Nuance used vocaliser and eloquence for talks.

True, we use espeak which is used with linux as well but the point we started our own synth, and I think we should continue.

For whatever reason it just stopped.

The synth was ok sounding, probably a bit outdated and crappy now but still we really should bring it back for bragging rights at least.

 

 

On 13/09/2019 4:23 pm, Quentin Christensen wrote:

Hi everyone,

 

We get asked about creating a new synthesizer from time to time - either simply for ANY synthesizer to support a particular language, or someone wants to create a brand new one, perhaps with their own voice.

 

Normally I suggest looking at the eSpeak NG project as a starting point.  I was wondering, does anyone have any useful links on how to go about this, that I can pass on when I get such inquiries, please?

 

I appreciate it's a very complex undertaking, which is why I'm asking here.  If I'm going to pass on anything, I'd rather pass on something of some quality, rather than just a random link off eBay.

 

Kind regards

 

Quentin.

 

--

Quentin Christensen
Training and Support Manager

 

Re: Creating a new synthesizer

Gene
 

Bragging rites mean nothing unless the product is superior.  People don't care if NVDA has its own synthesizer or not and resources can be much better used.  It is a very specialized area to create a really good synthesizer and NVDA doesn't have the expertise or the resources to divert to such a product. 
 
JAWS never had its own voice.  Neither did Window-eyes nor does System Access.  Clearly, this is hardly something screen-reader developers or the consuming public are concerned about.
 
Gene

----- Original Message -----
Sent: Friday, September 13, 2019 12:12 AM
Subject: Re: [nvda] Creating a new synthesizer

You know that really does bring up an interesting project which seems forgotton.

What happened to our own synth the one called speech player.

Why did we stop developing it or did nv access stop developing it.

It probably won't be compatible with 1903 but thats utterly useless if development has stopped, so maybe we should start doing that again.

I mean I like espeak ng but just about every screen reader company has their own synth.

Dolphin uses orpheus, jaws uses eloquence.

Windoweyes used dectalk, microsoft stuff used microsoft stuff.

Nuance used vocaliser and eloquence for talks.

True, we use espeak which is used with linux as well but the point we started our own synth, and I think we should continue.

For whatever reason it just stopped.

The synth was ok sounding, probably a bit outdated and crappy now but still we really should bring it back for bragging rights at least.



On 13/09/2019 4:23 pm, Quentin Christensen wrote:
Hi everyone,

We get asked about creating a new synthesizer from time to time - either simply for ANY synthesizer to support a particular language, or someone wants to create a brand new one, perhaps with their own voice.

Normally I suggest looking at the eSpeak NG project as a starting point.  I was wondering, does anyone have any useful links on how to go about this, that I can pass on when I get such inquiries, please?

I appreciate it's a very complex undertaking, which is why I'm asking here.  If I'm going to pass on anything, I'd rather pass on something of some quality, rather than just a random link off eBay.

Kind regards

Quentin.

--
Quentin Christensen
Training and Support Manager

Re: Creating a new synthesizer

Sky Mundell
 

It would be wonderful if Speech Player could be developed again. I should also add that in the other comertial products you mentioned they did allow you to change the synthesizers and NVDA allows you to change the synthesizers as well.

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Shaun Everiss
Sent: Thursday, September 12, 2019 10:13 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Creating a new synthesizer

 

You know that really does bring up an interesting project which seems forgotton.

What happened to our own synth the one called speech player.

Why did we stop developing it or did nv access stop developing it.

It probably won't be compatible with 1903 but thats utterly useless if development has stopped, so maybe we should start doing that again.

I mean I like espeak ng but just about every screen reader company has their own synth.

Dolphin uses orpheus, jaws uses eloquence.

Windoweyes used dectalk, microsoft stuff used microsoft stuff.

Nuance used vocaliser and eloquence for talks.

True, we use espeak which is used with linux as well but the point we started our own synth, and I think we should continue.

For whatever reason it just stopped.

The synth was ok sounding, probably a bit outdated and crappy now but still we really should bring it back for bragging rights at least.

 

 

On 13/09/2019 4:23 pm, Quentin Christensen wrote:

Hi everyone,

 

We get asked about creating a new synthesizer from time to time - either simply for ANY synthesizer to support a particular language, or someone wants to create a brand new one, perhaps with their own voice.

 

Normally I suggest looking at the eSpeak NG project as a starting point.  I was wondering, does anyone have any useful links on how to go about this, that I can pass on when I get such inquiries, please?

 

I appreciate it's a very complex undertaking, which is why I'm asking here.  If I'm going to pass on anything, I'd rather pass on something of some quality, rather than just a random link off eBay.

 

Kind regards

 

Quentin.

 

--

Quentin Christensen
Training and Support Manager

 

Re: Creating a new synthesizer

 

You know that really does bring up an interesting project which seems forgotton.

What happened to our own synth the one called speech player.

Why did we stop developing it or did nv access stop developing it.

It probably won't be compatible with 1903 but thats utterly useless if development has stopped, so maybe we should start doing that again.

I mean I like espeak ng but just about every screen reader company has their own synth.

Dolphin uses orpheus, jaws uses eloquence.

Windoweyes used dectalk, microsoft stuff used microsoft stuff.

Nuance used vocaliser and eloquence for talks.

True, we use espeak which is used with linux as well but the point we started our own synth, and I think we should continue.

For whatever reason it just stopped.

The synth was ok sounding, probably a bit outdated and crappy now but still we really should bring it back for bragging rights at least.



On 13/09/2019 4:23 pm, Quentin Christensen wrote:
Hi everyone,

We get asked about creating a new synthesizer from time to time - either simply for ANY synthesizer to support a particular language, or someone wants to create a brand new one, perhaps with their own voice.

Normally I suggest looking at the eSpeak NG project as a starting point.  I was wondering, does anyone have any useful links on how to go about this, that I can pass on when I get such inquiries, please?

I appreciate it's a very complex undertaking, which is why I'm asking here.  If I'm going to pass on anything, I'd rather pass on something of some quality, rather than just a random link off eBay.

Kind regards

Quentin.

--
Quentin Christensen
Training and Support Manager

Creating a new synthesizer

Quentin Christensen
 

Hi everyone,

We get asked about creating a new synthesizer from time to time - either simply for ANY synthesizer to support a particular language, or someone wants to create a brand new one, perhaps with their own voice.

Normally I suggest looking at the eSpeak NG project as a starting point.  I was wondering, does anyone have any useful links on how to go about this, that I can pass on when I get such inquiries, please?

I appreciate it's a very complex undertaking, which is why I'm asking here.  If I'm going to pass on anything, I'd rather pass on something of some quality, rather than just a random link off eBay.

Kind regards

Quentin.

--
Quentin Christensen
Training and Support Manager

Re: NVDA command to copy a link

Gene
 

You don't have to use the mouse if you are in browse mode or in a list view in a program that supports this kind of thing.  and you only use the context menu if you are copying a link address where the link is words such as click here to see the article.  If the link is written out,
you copy it to the clipboard and paste it wherever you want.
 
If the link is words, Be on the link.  Open the application menu either with the application key or shift f10.  Look at the items in the menu.  Is there something like copy link location or copy link?  Please give a concrete example including telling us if you want to copy a written out link or a link as words, such as click here to see the article.  Also, tell us what program you are using.
 
Gene

----- Original Message -----
Sent: Thursday, September 12, 2019 8:21 PM
Subject: Re: [nvda] NVDA command to copy a link

Hi Quentin,

Thank you so much for your prompt reply.  My keyboard does not have an application key.

Sorry for being such a novice, how do you copy with the mouse?  Is there an alternative to using the application key?  Sometimes I used the shift-f9 which provides a menu that has a copy link command.  Unfortunately, for some reason it at times copies the link above the one I am interested in copying.

Many thanks for your help.

Blessings

Pascal

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen
Sent: Thursday, September 12, 2019 9:12 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA command to copy a link

 

Note that control+c doesn't work if you select the link (or anything) with the mouse - if you've used the mouse to select, then press the applications key to bring up the context menu, and choose "copy".

 

In many cases, if you navigate to a link, you can use the applications key to bring up the context menu and choose "copy link location" or "copy link address".

 

Regards

 

Quentin.

 

On Fri, Sep 13, 2019 at 11:01 AM Kerryn Gunness via Groups.Io <k_gunness=yahoo.ca@groups.io> wrote:

select the link, then copy control c

 

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

Sent: Thursday, September 12, 2019 8:58 PM

Subject: [nvda] NVDA command to copy a link

 

Hi,

Please is there an NVDA command to copy a link?

Many thanks

Blessings

Pascal


 

--

Quentin Christensen
Training and Support Manager

 

Re: NVDA command to copy a link

Gene
 

No.  What kind of link?  A written out link such as
http://www.microsoft.com or links as words such as click here to watch the report. 
NVdA can copy text such as in a dialog or anyplace there is no program cursor but that isn't a copy link command.  You can use it to copy a link or any other text where there is no application cursor.  The link must be a written out link such as the Microsoft link I used as an example.
 

Gene
----- Original Message -----
Sent: Thursday, September 12, 2019 7:58 PM
Subject: [nvda] NVDA command to copy a link

Hi,

Please is there an NVDA command to copy a link?

Many thanks

Blessings

Pascal

Re: Windows 10 Notifications?

Clement Chou
 

Great. Thanks Stephen!

On 9/12/19, Stephen W. Wise <bvitech1@...> wrote:
Hi,

?????? I have noticed this behavior on my system but haven't had enough
alerts to see if there is, indeed, a pattern. For example, Windows
Defender completed its scan in the background but NVDA didn't tell me
the alert that popped up indicating this. I had to use the Windows Key +
A method to tab over to the message in the alert. I am not sure the
reasoning yet why this is the case but have been trying to identify any
cause such as-too many alerts in the Action center display nullifying
any output from NVDA. It appears that it may be random as it will
announce changes from time to time and I just tested this by unplugging
my external My Passport drive and it worked normally. So, long story
short, I don't believe that this is normal behavior and I might look and
see if anybody else has filed a bug report or could be made aware
through this post.


Stephen



On 9/12/2019 10:16 PM, Clement Chou wrote:
Thanks. I am indeed running 1903. My NVDA has also stopped reading
notifications when they first appear. Is this normal as well and is
there a fix?

On 9/12/19, Stephen W. Wise <bvitech1@...> wrote:
Hi,

?????? Depending on the version of Windows you are using-Windows 10
1903
exhibits this behavior-the key has now been remapped by Microsoft in
1903 to allow the ability to view different things copied to the
clipboard, now. In this situation, it would appear that Windows Key + A
is the alternative to this change. If you aren't running this version of
windows perhaps you could indicate your version on your system since
some features change as Microsoft releases new feature sets and updates
for Windows.


Stephen


On 9/12/2019 9:01 PM, Clement Chou wrote:
Seems like my NVDA has stopped reading them out loud when they come up
with the latest update... and the windows+v shortcut no longer works
to bring up the popup. Anyne got any pointers here? I'm a little
mystified. Thanks!





Re: Windows 10 Notifications?

Stephen W. Wise
 

Hi,

?????? I have noticed this behavior on my system but haven't had enough alerts to see if there is, indeed, a pattern. For example, Windows Defender completed its scan in the background but NVDA didn't tell me the alert that popped up indicating this. I had to use the Windows Key + A method to tab over to the message in the alert. I am not sure the reasoning yet why this is the case but have been trying to identify any cause such as-too many alerts in the Action center display nullifying any output from NVDA. It appears that it may be random as it will announce changes from time to time and I just tested this by unplugging my external My Passport drive and it worked normally. So, long story short, I don't believe that this is normal behavior and I might look and see if anybody else has filed a bug report or could be made aware through this post.


Stephen

On 9/12/2019 10:16 PM, Clement Chou wrote:
Thanks. I am indeed running 1903. My NVDA has also stopped reading
notifications when they first appear. Is this normal as well and is
there a fix?

On 9/12/19, Stephen W. Wise <bvitech1@...> wrote:
Hi,

?????? Depending on the version of Windows you are using-Windows 10 1903
exhibits this behavior-the key has now been remapped by Microsoft in
1903 to allow the ability to view different things copied to the
clipboard, now. In this situation, it would appear that Windows Key + A
is the alternative to this change. If you aren't running this version of
windows perhaps you could indicate your version on your system since
some features change as Microsoft releases new feature sets and updates
for Windows.


Stephen


On 9/12/2019 9:01 PM, Clement Chou wrote:
Seems like my NVDA has stopped reading them out loud when they come up
with the latest update... and the windows+v shortcut no longer works
to bring up the popup. Anyne got any pointers here? I'm a little
mystified. Thanks!