Date   
locked Re: blank line reading by NVDA

Luke Davis
 

On Tue, 8 Oct 2019, Brian Vogel wrote:

This conversation interests me because it seems to me that two different things are being talked about.Luke's solution uses a regular expression where the
word "blank" itself must be matched, using anchors at each end.  But the original question seems to me to be about lines that contain nothing but a return,
that is, a completely blank line, so that if someone typed line one, followed by two hits of Enter, followed by line two it would be read as, "Line one
blank blank line two," by NVDA.It does not seem to me to have anything to do with the word "blank" or its equivalent in any language, so I don't know what
I'm missing, if anything at all.
What you appear to be missing, are the dynamics of the available solutions.

Sure, if we had the option of running some kind of preprocessing filter on the text before NVDA converted it to speech, we could use a regexp like the one you suggest. But have you actually tried it? I suspect if you had, you would have found that it has no effect what so ever.
That is because we don't have that preprocessing option, short of writing an add-on for this strange purpose.

What we do have available, are speech dictionaries. But with that we have a problem, because by the time the dictionaries get applied, it's far too late in the process to even see the original text. All we get to work with is a layer between the text that is going to be sent to a synth, and the text that actually arrives at a synth.

We are doing post-processing transforms on *output* not input.

How does one tell a synth to indicate a blank line? If you just send \n, or \r\n, or their ASCII control code equivalents, it will likely say nothing. The way you (NVDA) get it to say something, is to substitute the word "blank", or the locale equivalent. So that, and only that, is what we are left with intercepting and modifying or suppressing.

Now using the regular expression:  ^\s*$with nothing substituted for it should find any line that is blank, whether it's just someone having hit Enter, or any whitespace character followed by enter, and would say nothing if that's found.
Of course, if we were able to preprocess the text before NVDA's translation layers got their hooks into it, but we can't.

If the literal word "blank" were to
appear all by its lonesome on a single line it would be read, correctly, as blank.One would definitely not want to be using this method when proofreading
something written in a text editor, as you'd never know if you'd put in paragraph breaks or how many times you'd hit enter when trying to create vertical
separation.
To be clear, I was answering the question, not stating an opinion on the advisability of doing this. Which opinion is: don't, it's not worth it. But hey, to each his own.

Luke

locked Re: blank line reading by NVDA

 

Luke,

            I am not going to get into a technical argument.   But it makes no sense to say that you don't process text that gets passed to a synth prior to its being passed to it.  None of the dictionaries, to my knowledge, post process text after it goes to the synth, but are used to decide what, exactly, gets passed to the synth.

            I don't even know what is referenced by "translation layer" and that may be the problem.  But the final part of the process has to be handing off that which is to be spoken to the synthesizer that speaks it.  All changes to same must occur prior to that step.

--

Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362  

The color of truth is grey.

           ~ André Gide

 

 

locked Re: blank line reading by NVDA

Luke Davis
 

On Wed, 9 Oct 2019, Shaun Everiss wrote:

I actually like blank lines being announced when moving up and down some files.
Agreed.

I guess it could be an issue when reading a large book but you can turn the announcements of blank lines being announced in nvda preffs speech I think
anyway.
I have looked for this, twice, in all of NVDA's default settings screens, and can't find it. Can you verify please?

Luke

locked Re: blank line reading by NVDA

Luke Davis
 

On Tue, 8 Oct 2019, Brian Vogel wrote:

Luke,            I am not going to get into a technical argument.   But it makes no sense to say that you don't process text that gets passed to a synth
prior to its being passed to it.  None of the dictionaries, to my knowledge, post process text after it goes to the synth, but are used to decide what,
exactly, gets passed to the synth.
When did I say anything post processes text *after* it goes to the synth? That would be ridiculous.
What I said was:

"
What we do have available, are speech dictionaries. But with that we have a problem, because by the time the dictionaries get applied, it's far too late in the process to even see the original text. All we get to work with is a layer between the text that is going to be sent to a synth, and the text that actually arrives at a synth.
"

Since that seems unclear to you, I will try to say it another way.

1. NVDA takes the contents of the (in Notepad, for example) multi line edit field.
It will see a blank line as just an empty line.
It is at this point that your regexp matching empty lines would work.

2. NVDA does whatever internal things it needs to to the text in question (in this case nothing), to figure out if it needs to report fonts, underlining, indenting, etc.

3. A bunch of other stuff that is irrelevant to the discussion at hand.

4. By now, if this was a text string like "hello world", that was indented, underlined, and with font announcements turned on, the text NVDA planned to speak, would probably look like this:

Arial 15 point indent 2.0 underlined Hello world

In our case, we still have empty text. Since NVDA knows the synth needs to actually say something, instead of sending it empty text, the text will be:

blank

Either way, that is now what I called "the text that is going to be sent to a synth".

5. Apply any dictionaries that are to be applied to transform the text. This will be default, temporary, and if appropriate, synth. I have no idea in which order.

6. Send the text to be spoken, as revised by the dictionaries, to the synth. This is what I called "the text that actually arrives at a synth"

So the bottom line of what I'm telling you, is that in order for your regexp to work, the dictionaries would need to be applied all the way down at step 1 or 2. In fact they are applied very late in the process, long after the original text has been turned into a synth-friendly form.
Note that I am ignoring translation into languages in this process.

          I don't even know what is referenced by "translation layer" and that may be the problem.  But the final part
of the process has to be handing off that which is to be spoken to the synthesizer that speaks it.  All changes to same must occur prior to that step.
Obviously. But there is a big difference in applying those changes at the start of processing of incoming text, and applying them right at the end of the processing chain.

At the start, the text has the nature of input. You can view it as input, and if you had a hook that early, you could manipulate the raw input. But the average user has no such hook. The only hook we have, is to process the text after it has been converted into speech-style output, by running it through speech dictionaries.

The point I was trying to make to you, was that we are not pre-processing text as it enters NVDA.
We are post-processing text, as it is leaving NVDA and on its way into the synth.

Dictionaries are (very nearly if not actually) the last step in the processing chain for text. The text might have little resemblance to the actual input by that point, it is mainly made up of words that NVDA wants the user to hear--we are processing the text right before it becomes audio.
By then an empty line isn't the empty string, it is the word "blank" which is what NVDA needs the user to hear.

Luke

locked Re: blank line reading by NVDA

 

On Tue, Oct 8, 2019 at 06:37 PM, Luke Davis wrote:
By then an empty line isn't the empty string, it is the word "blank" which is what NVDA needs the user to hear.
After all that precedes what's quoted above (which, by the way, I appreciate), this is the crux of the matter.  I had not realized that NVDA was doing anywhere near to this level of "massaging" to the straight text before passing it to the synthesizer, particularly when all one is looking for is for the text to be read in the manner I presume I'd read it were I reading it to someone.

I understand why, when doing line by line, the blank lines get announced as blank as, to me, that's part and parcel of why one is going line by line - to pick up just this sort of thing.  What I didn't realize was that during NVDA's pre-processing of a blank line it had actually substituted the word "blank" to pass to the synthesizer.  I would have thought that if reading line by line the first thing that would happen is checking the custom dictionaries for the line to be passed, and that line alone, and if it were substituted with nothing, as in there is no replacement string, that nothing would be passed to the synth.

I don't code NVDA, clearly, and it appears that you do.   Information such as you've offered, and clearly, makes the process much more transparent, if convoluted, to me.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362  

The color of truth is grey.

           ~ André Gide

 

 

locked Re: blank line reading by NVDA

Luke Davis
 

On Tue, 8 Oct 2019, Luke Davis wrote:

At the start, the text has the nature of input. You can view it as input, and if you had a hook that early, you could manipulate the raw input. But the average user has no such hook. The only hook we have, is to process the text after it has been converted into speech-style output, by running it through speech dictionaries.
Maybe a more real world example will help:

On the NVDAHelp list, someone recently asked how to get NVDA to stop saying "edit multi line" when he went into Notepad or similar.
I.E. currently, when you open Notepad, it says:

Untitled - Notepad. Text editor edit multi line. Blank.

He found this two verbose.

In a debug level log (could have been done with input-output logging as well), we can see the following (abbreviated):

Speaking [LangChangeCommand ('en_GB'), u'Untitled - Notepad']
Speaking [LangChangeCommand ('en_GB'), u'Text Editor edit multi line']
Speaking [LangChangeCommand ('en_GB'), u'blank']

The solution to his problem, was to create a dictionary entry containing " edit multi line"
With no replacement.

But most of that text isn't on the screen at all (except probably "Notepad - untitled").

The strings that are going to be sent to the synth, and thus the only strings the speech dictionaries get to operate on, are the strings that NVDA wants to SAY, not the strings that it actually got from the screen. Yes, screen strings will probably be incorporated in some way, but by the time the dictionaries get them, they are strings to be verbalized, and thus might look very different than the way they actually look on screen.

That's what I meant by saying that the dictionaries are processing output, not processing input.

I hope that clarifies what I've been trying to explain.

Luke

locked Re: blank line reading by NVDA

 

Well when I have a blank line its a space and a couple of linefeed chars.

I know a few older programs use carage return, in fact when I was in dos you had cr, lf and cr/lf, but its all lf now.

Now you can turn blank lines off if you don't want them, but be aware that if you need em, you will have to turn them back on.

You could make a profile for whatever program you don't want the blanks announced, in configuration profiles on nvda preffs and then you can just use that, when you open a program that setting will trigger and you will be ok.

If you have to frequently read a text file especially if its done for you, ie its not needed to handle it via say the computer and you don't say need to edit it, say a book, I'd use the daisy hardware reader of choice.

Or daisy software, some can read text files via sapi or something.

As I said there are many ways to handle this.



On 9/10/2019 11:48 am, Brian Vogel wrote:
On Tue, Oct 8, 2019 at 06:37 PM, Luke Davis wrote:
By then an empty line isn't the empty string, it is the word "blank" which is what NVDA needs the user to hear.
After all that precedes what's quoted above (which, by the way, I appreciate), this is the crux of the matter.  I had not realized that NVDA was doing anywhere near to this level of "massaging" to the straight text before passing it to the synthesizer, particularly when all one is looking for is for the text to be read in the manner I presume I'd read it were I reading it to someone.

I understand why, when doing line by line, the blank lines get announced as blank as, to me, that's part and parcel of why one is going line by line - to pick up just this sort of thing.  What I didn't realize was that during NVDA's pre-processing of a blank line it had actually substituted the word "blank" to pass to the synthesizer.  I would have thought that if reading line by line the first thing that would happen is checking the custom dictionaries for the line to be passed, and that line alone, and if it were substituted with nothing, as in there is no replacement string, that nothing would be passed to the synth.

I don't code NVDA, clearly, and it appears that you do.   Information such as you've offered, and clearly, makes the process much more transparent, if convoluted, to me.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362  

The color of truth is grey.

           ~ André Gide

 

 

locked Re: blank line reading by NVDA

Luke Davis
 

On Tue, 8 Oct 2019, Luke Davis wrote:

That's what I meant by saying that the dictionaries are processing output, not processing input.
This conversation has made apparent something I, and probably most others, never actually thought about: the reason these are called "Speech Dictionaries", and not just "Dictionaries" or some other thing. They are, quite literally, dictionaries that do replacements of "speech"--speech strings in, speech strings out. Not screen strings in, speech strings out.

locked Re: blank line reading by NVDA

George McCoy
 

I don't find anything in preferences that turns off pronunciation of blank lines.


George

On 10/8/2019 5:58 PM, Shaun Everiss wrote:

Well when I have a blank line its a space and a couple of linefeed chars.

I know a few older programs use carage return, in fact when I was in dos you had cr, lf and cr/lf, but its all lf now.

Now you can turn blank lines off if you don't want them, but be aware that if you need em, you will have to turn them back on.

You could make a profile for whatever program you don't want the blanks announced, in configuration profiles on nvda preffs and then you can just use that, when you open a program that setting will trigger and you will be ok.

If you have to frequently read a text file especially if its done for you, ie its not needed to handle it via say the computer and you don't say need to edit it, say a book, I'd use the daisy hardware reader of choice.

Or daisy software, some can read text files via sapi or something.

As I said there are many ways to handle this.



On 9/10/2019 11:48 am, Brian Vogel wrote:
On Tue, Oct 8, 2019 at 06:37 PM, Luke Davis wrote:
By then an empty line isn't the empty string, it is the word "blank" which is what NVDA needs the user to hear.
After all that precedes what's quoted above (which, by the way, I appreciate), this is the crux of the matter.  I had not realized that NVDA was doing anywhere near to this level of "massaging" to the straight text before passing it to the synthesizer, particularly when all one is looking for is for the text to be read in the manner I presume I'd read it were I reading it to someone.

I understand why, when doing line by line, the blank lines get announced as blank as, to me, that's part and parcel of why one is going line by line - to pick up just this sort of thing.  What I didn't realize was that during NVDA's pre-processing of a blank line it had actually substituted the word "blank" to pass to the synthesizer.  I would have thought that if reading line by line the first thing that would happen is checking the custom dictionaries for the line to be passed, and that line alone, and if it were substituted with nothing, as in there is no replacement string, that nothing would be passed to the synth.

I don't code NVDA, clearly, and it appears that you do.   Information such as you've offered, and clearly, makes the process much more transparent, if convoluted, to me.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362  

The color of truth is grey.

           ~ André Gide

 

 

locked Re: blank line reading by NVDA

Tony Malykh
 

I am now working on a new add-on called Phonetic Punctuation - I hope to release a stable version in the next couple of weeks - it will allow you to accomplish that. It can also replace the word blank with a configurable auditory icon, or just with silence. The catch is that this add-on is only going to work with NVDA versions 2019.3 and above.

If you're interested - so far a not very stable version available:

https://github.com/mltony/nvda-phonetic-punctuation

But if you're looking to completely remove the word "blank" from speech - you can also do what others have suggested and do it in speech dictionary.


--Tony



On 10/8/2019 12:35 AM, Afik Souffir wrote:

 

Hi,

 

My name is Afik, from Israel, I’m almost 21 years old.

 

I want to ask, how can I stop NVDA to read or show in braille blank lines, such in emails, websites, or other platforms?

 

Thanks

 

Afik Souffir

 

 

locked Re: blank line reading by NVDA

 

what should i do?
the best version of nvda is 2017.2 that i wish to use it forever!
can you please guide me step by step what should i do in this regard?

On 10/10/19, Tony Malykh <anton.malykh@...> wrote:
I am now working on a new add-on called Phonetic Punctuation - I hope to
release a stable version in the next couple of weeks - it will allow you
to accomplish that. It can also replace the word blank with a
configurable auditory icon, or just with silence. The catch is that this
add-on is only going to work with NVDA versions 2019.3 and above.

If you're interested - so far a not very stable version available:

https://github.com/mltony/nvda-phonetic-punctuation

But if you're looking to completely remove the word "blank" from speech
- you can also do what others have suggested and do it in speech
dictionary.


--Tony



On 10/8/2019 12:35 AM, Afik Souffir wrote:

Hi,

My name is Afik, from Israel, I’m almost 21 years old.

I want to ask, how can I stop NVDA to read or show in braille blank
lines, such in emails, websites, or other platforms?

Thanks

Afik Souffir



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

locked Re: blank line reading by NVDA

Sarah k Alawami
 

Yeh, updte to the latest NVDA. Why do you want to ue a version that might one day cease working. After you update install the add on and read any including documentation if any.

Sarah Alawami, owner of TFFP. . For more info go to our website. This is also our libsyn page as well.
For stuff we sell, mac training materials and  tutorials go here.
and for hosting options go here
to subscribe to the feed click here

Our telegram channel is also a good place for an announce only in regard to podcasts, contests, etc.

Our discord is where you will know when we go live on youtube, twitch and mixer. Thanks Restream staff.

Finally, to become a patron and help support the podcast go here

On 9 Oct 2019, at 20:47, zahra wrote:

what should i do?
the best version of nvda is 2017.2 that i wish to use it forever!
can you please guide me step by step what should i do in this regard?

On 10/10/19, Tony Malykh anton.malykh@... wrote:

I am now working on a new add-on called Phonetic Punctuation - I hope to
release a stable version in the next couple of weeks - it will allow you
to accomplish that. It can also replace the word blank with a
configurable auditory icon, or just with silence. The catch is that this
add-on is only going to work with NVDA versions 2019.3 and above.

If you're interested - so far a not very stable version available:

https://github.com/mltony/nvda-phonetic-punctuation

But if you're looking to completely remove the word "blank" from speech
- you can also do what others have suggested and do it in speech
dictionary.

--Tony

On 10/8/2019 12:35 AM, Afik Souffir wrote:

Hi,

My name is Afik, from Israel, I’m almost 21 years old.

I want to ask, how can I stop NVDA to read or show in braille blank
lines, such in emails, websites, or other platforms?

Thanks

Afik Souffir

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

locked Re: blank line reading by NVDA

Arlene
 

I know you don’t want to hear it! You have to update your computer and NVDA. If you like what you like then stay with it.

 

Sent from Mail for Windows 10

 

From: zahra
Sent: October 9, 2019 8:47 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] blank line reading by NVDA

 

what should i do?

the best version of nvda is 2017.2 that i wish to use it forever!

can you please guide me step by step what should i do in this regard?

 

On 10/10/19, Tony Malykh <anton.malykh@...> wrote:

> I am now working on a new add-on called Phonetic Punctuation - I hope to

> release a stable version in the next couple of weeks - it will allow you

> to accomplish that. It can also replace the word blank with a

> configurable auditory icon, or just with silence. The catch is that this

> add-on is only going to work with NVDA versions 2019.3 and above.

> If you're interested - so far a not very stable version available:

> https://github.com/mltony/nvda-phonetic-punctuation

> But if you're looking to completely remove the word "blank" from speech

> - you can also do what others have suggested and do it in speech

> dictionary.

> --Tony

> On 10/8/2019 12:35 AM, Afik Souffir wrote:

>> 

>> Hi,

>> 

>> My name is Afik, from Israel, I’m almost 21 years old.

>> 

>> I want to ask, how can I stop NVDA to read or show in braille blank

>> lines, such in emails, websites, or other platforms?

>> 

>> Thanks

>> 

>> Afik Souffir

>> 

>> 

>

 

 

--

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

 

 

 

locked Re: blank line reading by NVDA

Rosemarie Chavarria
 

Hi, Zara,

 

Get a new computer with windows 10 and update to the latest version of NVDA. One of these days that old clunker of yours will stop working and you’ll wonder why. I’m not trying to be mean but you can’t keep an old system that’s out of date now.

 

Rosemarie

 

 

 

Sent from Mail for Windows 10

 

From: zahra
Sent: Wednesday, October 9, 2019 8:47 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] blank line reading by NVDA

 

what should i do?

the best version of nvda is 2017.2 that i wish to use it forever!

can you please guide me step by step what should i do in this regard?

 

On 10/10/19, Tony Malykh <anton.malykh@...> wrote:

> I am now working on a new add-on called Phonetic Punctuation - I hope to

> release a stable version in the next couple of weeks - it will allow you

> to accomplish that. It can also replace the word blank with a

> configurable auditory icon, or just with silence. The catch is that this

> add-on is only going to work with NVDA versions 2019.3 and above.

> If you're interested - so far a not very stable version available:

> https://github.com/mltony/nvda-phonetic-punctuation

> But if you're looking to completely remove the word "blank" from speech

> - you can also do what others have suggested and do it in speech

> dictionary.

> --Tony

> On 10/8/2019 12:35 AM, Afik Souffir wrote:

>> 

>> Hi,

>> 

>> My name is Afik, from Israel, I’m almost 21 years old.

>> 

>> I want to ask, how can I stop NVDA to read or show in braille blank

>> lines, such in emails, websites, or other platforms?

>> 

>> Thanks

>> 

>> Afik Souffir

>> 

>> 

>

 

 

--

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

 

 

 

locked Re: blank line reading by NVDA

 

hi.i really hate windows ten and keep xp or maybe seven forever.
nvda 2017.2 is the best version for me and i promised several times in
many places to use it forever.

On 10/10/19, Rosemarie Chavarria <knitqueen2007@...> wrote:
Hi, Zara,

Get a new computer with windows 10 and update to the latest version of NVDA.
One of these days that old clunker of yours will stop working and you’ll
wonder why. I’m not trying to be mean but you can’t keep an old system
that’s out of date now.

Rosemarie



Sent from Mail for Windows 10

From: zahra
Sent: Wednesday, October 9, 2019 8:47 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] blank line reading by NVDA

what should i do?
the best version of nvda is 2017.2 that i wish to use it forever!
can you please guide me step by step what should i do in this regard?

On 10/10/19, Tony Malykh <anton.malykh@...> wrote:
I am now working on a new add-on called Phonetic Punctuation - I hope to
release a stable version in the next couple of weeks - it will allow you
to accomplish that. It can also replace the word blank with a
configurable auditory icon, or just with silence. The catch is that this
add-on is only going to work with NVDA versions 2019.3 and above.

If you're interested - so far a not very stable version available:

https://github.com/mltony/nvda-phonetic-punctuation

But if you're looking to completely remove the word "blank" from speech
- you can also do what others have suggested and do it in speech
dictionary.


--Tony



On 10/8/2019 12:35 AM, Afik Souffir wrote:

Hi,

My name is Afik, from Israel, I’m almost 21 years old.

I want to ask, how can I stop NVDA to read or show in braille blank
lines, such in emails, websites, or other platforms?

Thanks

Afik Souffir




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







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

locked Re: blank line reading by NVDA

 

To be honest, with the state of the windows 1903 shell as of late, I am seriously thinking about getting something that will be using xp or win7 for offline  shell work, the shell has got a lot better but go deep enough into a folder tree, say 2-5 levels down and things may not read because of a partial crash with explorer.

I don't use shell work to much but when I do it can be really annoying at times.

I really hope with 1909 update that now things are going to all be part of search that we don't get the issue where we get search breaking again with updates like happened before.

I am seriously not interested on restoring/roling back/ restoring/ reformatting to get rid of and to fix a problem that I never made in the first place.

Now I will always use the latest version of windows for online work but I am starting to wander, if maybe I should use if not older windows another shell for my file work if one actually exists.



On 10/10/2019 5:07 pm, Arlene wrote:

I know you don’t want to hear it! You have to update your computer and NVDA. If you like what you like then stay with it.

 

Sent from Mail for Windows 10

 

From: zahra
Sent: October 9, 2019 8:47 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] blank line reading by NVDA

 

what should i do?

the best version of nvda is 2017.2 that i wish to use it forever!

can you please guide me step by step what should i do in this regard?

 

On 10/10/19, Tony Malykh <anton.malykh@...> wrote:

> I am now working on a new add-on called Phonetic Punctuation - I hope to

> release a stable version in the next couple of weeks - it will allow you

> to accomplish that. It can also replace the word blank with a

> configurable auditory icon, or just with silence. The catch is that this

> add-on is only going to work with NVDA versions 2019.3 and above.

> If you're interested - so far a not very stable version available:

> https://github.com/mltony/nvda-phonetic-punctuation

> But if you're looking to completely remove the word "blank" from speech

> - you can also do what others have suggested and do it in speech

> dictionary.

> --Tony

> On 10/8/2019 12:35 AM, Afik Souffir wrote:

>> 

>> Hi,

>> 

>> My name is Afik, from Israel, I’m almost 21 years old.

>> 

>> I want to ask, how can I stop NVDA to read or show in braille blank

>> lines, such in emails, websites, or other platforms?

>> 

>> Thanks

>> 

>> Afik Souffir

>> 

>> 

>

 

 

--

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: Clipspeak addon compatibility status

Larry Wang
 

According to the license of NVDA,all code other than some paid synthesizers that runs under NVDA, should be GPL v2. So it is not necessary to obtain permission as long as you release full source code. Joseph's message about needing to obtain permission only applies to addons on community site.I guess for the sake of avoiding version conflict and wasting time of developer and reviewer.

On 2019/10/7 5:43, Gene wrote:

I'm not saying that this problem will occur regarding this add-on, I don't think it will, but the possible situation should be discussed.
 
I saw Joseph's message about needing to obtain permission before making the add-on compatible.  This raises the question of providing, in some sort of agreement regarding add-ons, that under specified conditions an add-on will be considered to be in the public domain.  An add-on that is abandoned but not in the public domain is in danger of not being updated and becoming useless or significantly degraded as NVDA or the program it works with changes. 
 
Of course, the rights of those who provide add-ons for profit should be protected but it is, in my opinion, a serious violation of the spirit of NVDA that an add-on can be abandoned by its developer, and still not be able to be modified to keep it current.
 
Gene
----- Original Message -----
Sent: Sunday, October 06, 2019 4:35 PM
Subject: Re: [nvda] Clipspeak addon compatibility status

I just looked at the website listing the compatibility of add-ons with python 3.  It says clipspeak isn't compatible. Here's the link

https://addons.nvda-project.org/addons/nvdapy3.en.html

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Kevin Cussick via Groups.Io
Sent: Sunday, October 6, 2019 5:11 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Clipspeak addon compatibility status

this addon does not work with the latest alpha snaps.   i suppose this
is because it is not compatible with python3 yet?   Joseph or someone
else can answer.

On 06/10/2019 16:04, Brian Vogel wrote:
> Well, Clipspeak
> <https://addons.nvda-project.org/addons/clipspeak.en.html> is still
> downloadable from the NVDA Stable Add-Ons Page
> <https://addons.nvda-project.org/index.en.html>, and so long as it
> remains there I presume it works.  Things generally get removed if
> they become incompatible with the current version of NVDA.
>
> Damien Garwood is the author, and is a member of this group.  In the
> case of Add-Ons, consulting with their respective authors is the best
> way to find out whether they're being actively maintained and whether
> they are slated to work with the Python 3 code base.
> --
>
> Brian *-*Windows 10 Pro, 64-Bit, Version 1903, Build 18362
>
> *The color of truth is grey.*
>
>             ~ André Gide
>
>






locked Re: blank line reading by NVDA

 

On Thu, Oct 10, 2019 at 01:38 AM, zahra wrote:
i really hate windows ten and keep xp or maybe seven forever.
Then, please have some respect for those who do keep up.

You know very well that no one is going to be trying to make things backward compatible with XP nor with now long out of support versions of NVDA.

Your choices have consequences.  And those choices are, without question, not wise.  You are literally digging yourself into a very deep technology hole.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362  

The color of truth is grey.

           ~ André Gide

 

 

Suggestion for creating a portable copy

Giles Turnbull
 

Hello, mainly for the attention of NVDA developers, but may be of interest to others :)

Usually when I want to install NVDA on a new machine (for my use) I create a portable copy with my current user configuration and install NVDA on my new machine from that. This is not a task I have to do often ... in fact I've done it twice, once last year when I installed it on a laptop I got for my university work and I'm just doing it again for the replacement laptop I got after the university machine broke (I dropped it and it wasn't repairable but thankfuly I had insurance that covered the cost of replacing it).

In creating both portable copies I've made the mistake of assuming, when choosing the directory path for the portable copy, that it would create a folder for the files ... it doesn't so I have ended up with over 100 separate files loose in the directory path plus half a dozen folders.

My suggestion would be to create a folder in the directory path for something like NVDA_Portable, or to add a note before the Browse for Path button that reminds whoever is creating the portable copy that the files and folders will be created in that directory so if you want them in their own folder, then such a folder should be created first and then selected as the destination path.

Whenever a new program is installed it usualy gets put into its own folder inside Program Files (x86). That is where NVDA goes when installed. I always assume a program is going to be put into its own folder whatever the directory path.

I can understand the rationale that if it's a portable copy being installed on a thumb drive you need to be able to run it before NVDA is active, but I'd have thought that if you've found a means of navigating to the thumb drive using Narrator, for example, then navigating into an NVDA_Portable folder to find NVDA.exe should be do-able.

Just a suggestion :)

Giles

Re: Suggestion for creating a portable copy

 

Put this on the git hub page. Make a pull request. This may seem like such a small thing, but I've forgotten about this many times and it has cluttered up the root folder of my flash drive. I'd also like to add it to the portableapps directory, where their team can host the file and future updates, possibly?