Date   

Re: Statement from Joseph Lee regarding NVDA add-ons and Windows XP support requests: no more, period

Brian's Mail list account
 

I'd like to add two things to this.
1. Outlook Express is still used by me, and can be modified to work on both windows 7 and 10, but I'd not expect anyone to add features to any screenreader to make it work better or differently as most of us who use it understand it could stop at any day, particularly in 10.
2 Windows XP most browsers work so slowly, if they work at all on many web sites, as to make them unusable.
Many third party software releases no longer work either including many anti virus solutions such as the Microsoft one, which only seems able to update one of its parts, and hence leaves gaps in protection. Many machines running the older AMD chipset cannot even run security essentials, or malwarebytes modern code and ccleaner either.
It is, sadly, time to relegate xp to simply a file server here, and then only on line for brief periods in case of drive by infection.

I also want to point out that Microsoft, though not officially supporting windows 7, did recently send me an update and continue to do so on security essentials and make their new Edge Browser work on 7, so we have a way to go yet here, but I expect the time will come to ditch that as well. If only Microsoft did not effectively do a reinstall every few months on windows 10, it would suit me fine, but as it is with so many legacy bits of software its a major pain to get everything back after an update.
OK I'm going back to sleep now!
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Joseph Lee" <@joslee>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Sunday, March 22, 2020 10:01 PM
Subject: [nvda-devel] Statement from Joseph Lee regarding NVDA add-ons and Windows XP support requests: no more, period


Hello NVDA users and add-on developers,



First, I would like to reiterate how important it is that everyone listen to
advice from reputable sources regarding COVID-19, including public health
officials recommending folks to exercise social distancing for a while. Even
if you do not feel sick, please help others by washing hands, practice
social distancing, and monitor the situation regarding the pandemic and
community spread. And since the NVDA community is a global movement, please
support each other.



Onto the matter at hand: for several days I have received requests about
NVDA add-ons and Windows XP support. Requests have included making add-ons
compatible with Windows XP again, compatibility issues, and backporting
newer NVDA bug fixes and features to users of NVDA 2017.3, the last version
compatible with Windows XP.



At the moment there is no community guidance on support for Windows XP, with
many people asking others to upgrade to newer Windows releases. But as an
individual add-on author and a contributor to NVDA screen reader project, I
would like to take this time to make the following personal announcement:



Effective April 15, 2020, if you ask me to do one or more of the following
for Windows XP users, the answer you will get is, "sorry, no more, period."
These include:



* Making add-ons compatible with Windows XP, Server 2003, Vista, and
Server 2008
* Fixing compatibility issues and non-working add-ons after you
knowingly install newer add-on releases on NVDA 2017.3 or earlier
* Backporting features and bug fixes from newer NVDA releases to NVDA
2017.3
* Maintaining a long-term support version of NVDA for Windows
XP/Server 2003/Vista/Server 2008 users



Most importantly, I will flatly say "no" if you ask me privately to ask NV
Access and/or add-on developers about Windows XP support. Many features
introduced in newer NVDA releases cannot be backported for various reasons,
including risk of crashing NVDA (grammar error announcement, for example),
incompatibility with Python 2 (broader Unicode support, for example),
features that will not work properly with XP (screen curtain, for example),
support for apps no longer recommended for wider use (outlook Express, for
example), and broad changes that alters how add-ons work (speech refactor
and multi-category settings dialog, for example). Several add-on authors
have indicated reluctance to support XP, and in case of add-ons I'm either
maintaining or have passed onto the community, none of them support NVDA
2019.2.1 or earlier, let alone Windows XP and friends.



My personal statement above will not be in effect until April so that you
can help others going through COVID-19 and for my statement as an individual
developer to sink in. Note that I'm not speaking on behalf of other
developers - others have their own policies regarding support for Windows
XP. NV Access does provide a download link for NVDA 2017.3, the last version
compatible with Windows XP.



I know my statement is a huge blow to many of you. As much as I wanted folks
to understand that end of support means end of support, and I understand
that many of you cannot afford newer equipment and software releases
(including moving to newer Windows releases), I felt it is time to make a
bold statement and say "no" to Windows XP support. In the past, I did note
on various NVDA forums that my add-ons will not and does not support Windows
XP, but didn't announce a statement like this then, hoping that folks will
understand the reality at last. But alas, it is time to officially close the
doors to Windows XP support from my end - once again, this is an individual
developer saying this, not on behalf of the community at large, knowing that
others will make statements on their own.



Thank you for understanding.

Cheers,

Joseph




Statement from Joseph Lee regarding NVDA add-ons and Windows XP support requests: no more, period

 

Hello NVDA users and add-on developers,

 

First, I would like to reiterate how important it is that everyone listen to advice from reputable sources regarding COVID-19, including public health officials recommending folks to exercise social distancing for a while. Even if you do not feel sick, please help others by washing hands, practice social distancing, and monitor the situation regarding the pandemic and community spread. And since the NVDA community is a global movement, please support each other.

 

Onto the matter at hand: for several days I have received requests about NVDA add-ons and Windows XP support. Requests have included making add-ons compatible with Windows XP again, compatibility issues, and backporting newer NVDA bug fixes and features to users of NVDA 2017.3, the last version compatible with Windows XP.

 

At the moment there is no community guidance on support for Windows XP, with many people  asking others to upgrade to newer Windows releases. But as an individual add-on author and a contributor to NVDA screen reader project, I would like to take this time to make the following personal announcement:

 

Effective April 15, 2020, if you ask me to do one or more of the following for Windows XP users, the answer you will get is, “sorry, no more, period.” These include:

 

  • Making add-ons compatible with Windows XP, Server 2003, Vista, and Server 2008
  • Fixing compatibility issues and non-working add-ons after you knowingly install newer add-on releases on NVDA 2017.3 or earlier
  • Backporting features and bug fixes from newer NVDA releases to NVDA 2017.3
  • Maintaining a long-term support version of NVDA for Windows XP/Server 2003/Vista/Server 2008 users

 

Most importantly, I will flatly say “no” if you ask me privately to ask NV Access and/or add-on developers about Windows XP support. Many features introduced in newer NVDA releases cannot be backported for various reasons, including risk of crashing NVDA (grammar error announcement, for example), incompatibility with Python 2 (broader Unicode support, for example), features that will not work properly with XP (screen curtain, for example), support for apps no longer recommended for wider use (outlook Express, for example), and broad changes that alters how add-ons work (speech refactor and multi-category settings dialog, for example). Several add-on authors have indicated reluctance to support XP, and in case of add-ons I’m either maintaining or have passed onto the community, none of them support NVDA 2019.2.1 or earlier, let alone Windows XP and friends.

 

My personal statement above will not be in effect until April so that you can help others going through COVID-19 and for my statement as an individual developer to sink in. Note that I’m not speaking on behalf of other developers – others have their own policies regarding support for Windows XP. NV Access does provide a download link for NVDA 2017.3, the last version compatible with Windows XP.

 

I know my statement is a huge blow to many of you. As much as I wanted folks to understand that end of support means end of support, and I understand that many of you cannot afford newer equipment and software releases (including moving to newer Windows releases), I felt it is time to make a bold statement and say “no” to Windows XP support. In the past, I did note on various NVDA forums that my add-ons will not and does not support Windows XP, but didn’t announce a statement like this then, hoping that folks will understand the reality at last. But alas, it is time to officially close the doors to Windows XP support from my end – once again, this is an individual developer saying this, not on behalf of the community at large, knowing that others will make statements on their own.

 

Thank you for understanding.

Cheers,

Joseph


Re: Broken phonetic spelling option in NVDA in the last few alpha snapshots

Cyrille
 

Hi Kostadin

 

IMO you should open an issue even if it is not critical for your usage. This would allow this issue to be tracked. And since it seems to be a regression on the last alpha, it would allow core dev to fix it before 2020.1 release. Of course, core dev will not break again character reading (at least not intentionnaly).

 

Cheers,

 

Cyrille

 

 

De : nvda-devel@groups.io <nvda-devel@groups.io> De la part de Kostadin Kolev
Envoyé : vendredi 20 mars 2020 11:10
À : NVDA screen reader development <nvda-devel@groups.io>
Objet : [nvda-devel] Broken phonetic spelling option in NVDA in the last few alpha snapshots

 

Hello all,

In NVDA's settings, in the "Speech" category, there is an option called "Use spelling functionality if supported". You all probably know what this option is supposed to do, so I'm not going to bother explaining it.

Before NVDA 2019.3, this option was not working correctly for the most used bulgarian SAPI5 speech synthesizer "SpeechLab" (the voice "Gergana"), so we were disabling it on a new NVDA installation when using that voice. After the speech refactor in NVDA 2019.3 however, the option started working correctly for our voice. And by "correctly" I mean that with it disabled, separately read consonant characters from our cyrillic alphabet were spoken by "SpeechLab" as de vocalized (hope I'm using the most correct term here - it is hard for me to explain it), which is not the default behavior. With the option enabled, the consonants are read normally when read separately. And I think that is how the option should work.

In recent alpha snapshots of NVDA however, this option got broken again for voice "SpeechLab". No matter if the option is enabled or disabled, the synthesizer reads separate consonants as if the option is enabled. I think the option got broken after fixing the issue which prevented NVDA from reading single characters when the Speech Viewer was enabled.

I'm not filing a bug for now, since the problem is not critical and most users prefer "SpeechLab" to read consonants as if the option "Use spelling functionality if supported" is enabled, which NVDA does like so now  anyway. But if there is a way to fix this without breaking character reading again, it would be nice.

Thanks much in advance!

______
Best wishes,
Kostadin Kolev


Broken phonetic spelling option in NVDA in the last few alpha snapshots

 

Hello all,

In NVDA's settings, in the "Speech" category, there is an option called "Use spelling functionality if supported". You all probably know what this option is supposed to do, so I'm not going to bother explaining it.

Before NVDA 2019.3, this option was not working correctly for the most used bulgarian SAPI5 speech synthesizer "SpeechLab" (the voice "Gergana"), so we were disabling it on a new NVDA installation when using that voice. After the speech refactor in NVDA 2019.3 however, the option started working correctly for our voice. And by "correctly" I mean that with it disabled, separately read consonant characters from our cyrillic alphabet were spoken by "SpeechLab" as de vocalized (hope I'm using the most correct term here - it is hard for me to explain it), which is not the default behavior. With the option enabled, the consonants are read normally when read separately. And I think that is how the option should work.

In recent alpha snapshots of NVDA however, this option got broken again for voice "SpeechLab". No matter if the option is enabled or disabled, the synthesizer reads separate consonants as if the option is enabled. I think the option got broken after fixing the issue which prevented NVDA from reading single characters when the Speech Viewer was enabled.

I'm not filing a bug for now, since the problem is not critical and most users prefer "SpeechLab" to read consonants as if the option "Use spelling functionality if supported" is enabled, which NVDA does like so now  anyway. But if there is a way to fix this without breaking character reading again, it would be nice.

Thanks much in advance!

______
Best wishes,
Kostadin Kolev


Re: nvda and hyper v servers issues

Marlon Brandão de Sousa
 

Hello,


I don't think this is the right forum to discuss these strategies.


You need to find a blind programming list and ask for help there, since from NVDA stand point of view there is nothing else we can do at this time.


Experienced blind programmers and network administrators can help you to find the best way to overcome whatever you are trying to do (supposedly learn something related to network admin based on what I was able to understand from your message). As for virtualization, the fact that vmware and virtualbox both offer virtual sound cards and hyper-v does not still is valid, so if you really really need a virtual machine with Widows running on a Windows host then you possibly will have to stick with one of these two options currently.


But here is the thing: do you really, really need a virtual machine? Perhaps you do, but perhaps not.

Other blind people can help you to further analyze this problem and help you to find out what works best on your scenarios.


I am currently out of English blind programming lists so I can't recommend any for you, but a search would probably show what you need in this regggard ...



On 16/03/2020 18:54, Marvin Hunkin wrote:
hi. okay will let my adaptive person know and also my institution and also the provider about this. yes, i tried vm ware work station player,and said i needed to turn off credential guard and when i tried that, well a no no with security. so what to suggest. get my college to set up microsoft azure. have you had success with that. tried virtual box and it kept either crashing or not giving me speech or audio either when i connected windows server. please let me know any other options. thanks... payap 


Re: nvda and hyper v servers issues

Marvin Hunkin
 

hi. okay will let my adaptive person know and also my institution and also the provider about this. yes, i tried vm ware work station player,and said i needed to turn off credential guard and when i tried that, well a no no with security. so what to suggest. get my college to set up microsoft azure. have you had success with that. tried virtual box and it kept either crashing or not giving me speech or audio either when i connected windows server. please let me know any other options. thanks... payap 


Re: nvda and hyper v servers issues

Marlon Brandão de Sousa
 

Hello, it is muted because once the connection is established then you are controlling the virtual machine. This is why it says input capture window, because from NVDA stand point of view you are operating something it (NVDA) has no control on its content.


When you control a virtual machine, from your operating system point of view that window is printing only graphics nothing that the system and thus NVDA have ways of extracting information from, thus becoming useless.


In order to run the virtual machine accessibly, that machine has to have a screen reader running and also a virtual sound card where the screen reader running on can output sound. Your virtualization engine then has to provide that virtual sound card for the virtual machine and link the sound from that card into some real sound card on your physical device. It happens though that hyper-v does not provide a virtual sound card device, as far as I can remember. So, unless you use other strategies, you won't be able to control a VM in an accessible way using hyper-v. Other strategies might include use braille through a virtual usb adapter (not sure if hyper-v provide these though, possibly not) or ask someone to install your virtual machine, install nvda, configure nvda remote and latter use nvda remote on your physical device to control nvda on the virtual machine.


I suggest you use vmware or virtualBox ... however be prepared to have a very sluge experience, as Windows VMs running on Windows hosts are usually very slow.


On 13/03/2020 03:58, Marvin Hunkin wrote:

Hi. I use windows 10 pro 64 bit on a assus laptop. Doing a it networking course and using the remote connection wizard. Put in the ip address, user name and password, click connect. Hear it say connecting to the ip address, then I hear input capture window. Then I hear nothing. The audio kills. Do have windows audio and windows audio end points enabled automatically in admin tools in control panel. So just need to use hyper v under windows 10, so I can then install other os on this virtual machine, windows server, hyper v and other servers, system centre, docker, etc. so how do I fix this. Do have the nvda remote add-on enabled and installed. So maybe quentin has run into this issue before and maybe a fix or work around.

Thanks.

Ps: have the same issue with jaws home 64 bit 2020, and maybe I need to purchase the jaws remote support. But not sure how much it costs. Whether I need to purchase or my educational institution needs to purchase. Annoying.


nvda and hyper v servers issues

Marvin Hunkin
 

Hi. I use windows 10 pro 64 bit on a assus laptop. Doing a it networking course and using the remote connection wizard. Put in the ip address, user name and password, click connect. Hear it say connecting to the ip address, then I hear input capture window. Then I hear nothing. The audio kills. Do have windows audio and windows audio end points enabled automatically in admin tools in control panel. So just need to use hyper v under windows 10, so I can then install other os on this virtual machine, windows server, hyper v and other servers, system centre, docker, etc. so how do I fix this. Do have the nvda remote add-on enabled and installed. So maybe quentin has run into this issue before and maybe a fix or work around.

Thanks.

Ps: have the same issue with jaws home 64 bit 2020, and maybe I need to purchase the jaws remote support. But not sure how much it costs. Whether I need to purchase or my educational institution needs to purchase. Annoying.


Re: I'm curious about a styling choice in NVDA's code

Reef Turner
 

> At least with Espeak, though, a comma between two words isn't spoken or indicated at all if no space is between it and the following word. This makes argument or parameter lists run together as a single, unbroken sentence with no pauses at all.

 

I assume this is with punctuation set to “most”. If you want to force this to be handled differently, you could change the rule in the symbol pronunciation dialog. To do so, find ‘comma’ (use the filter to make this faster), set the level to ‘most’. I think generally, for reading code people have the punctuation level set to “all”, since it’s important not to miss symbols.

 

From: nvda-devel@groups.io On Behalf Of Alex Hall
Sent: Tuesday, 10 March 2020 3:52 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] I'm curious about a styling choice in NVDA's code

 

I use a customized version of "most". Normally, when I'm coding, I rely on the pause Espeak inserts to know where commas are. I find "all" to be too verbose, preferring the easily-distinguished pause to having to hear "comma" aloud. At least with Espeak, though, a comma between two words isn't spoken or indicated at all if no space is between it and the following word. This makes argument or parameter lists run together as a single, unbroken sentence with no pauses at all.

 

On Tue, Mar 10, 2020 at 9:19 AM Reef Turner <reef@...> wrote:

Hi Alex,

 

What is your “Punctuation/symbol level” set to? You can use NVDA+p to toggle through the options, or check the option in the NVDA settings, speech category.

 

When set to all, the comma should be announced.

 

Regards,

Reef (NV Access)

 

From: nvda-devel@groups.io On Behalf Of Alex Hall
Sent: Thursday, 5 March 2020 12:32 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] I'm curious about a styling choice in NVDA's code

 

Makes sense. Thanks for the explanation.

 

On Thu, Mar 5, 2020 at 3:07 AM Julien Cochuyt <j.cochuyt@...> wrote:

Dear Alex,

 

Code styling has been enforced in the last few month with a proper linting of all new contributions merged into the code base of NVDA.

Indeed, a whitespace between the comma and the next call argument is now the rule.

It has nevertheless been decided not to lint existing code, mainly for two reasons:

 - Allow for an easier tracking of contribution history

 - Avoid the risk of causing regressions

 

 

Best regards,

 

Julien Cochuyt

Accessolutions

 

Le mer. 4 mars 2020 à 23:50, Alex Hall <ahall@...> a écrit :

All,

I've noticed that many function calls in NVDA don't place spaces between the comma of one argument and the start of the next argument. Using Espeak, this makes it very hard to read these argument lists, as this synthesizer runs everything together as a single sentence. It basically skips the commas unless there are spaces between them.

 

Given that NVDA's long-time default synthesizer, and one of the best synths for speaking quickly yet precisely, can't articulate without spaces, why was this styling choice made? Is it a hold-over that the team plans to clean up one day, but isn't important enough to bother with? Or is it intentional, and something the developers want contributors to continue to do?

 

It just strikes me as odd, so I figured I'd ask the experts. Thanks for indulging my curiosity.


--

Alex Hall

Automatic Distributors, IT department

ahall@...



--

Alex Hall

Automatic Distributors, IT department

ahall@...



--

Alex Hall

Automatic Distributors, IT department

ahall@...


Re: Strange behavior in class overlay

Alberto Buffolino
 

Michael Curran, il 11/03/2020 22.19, ha scritto:
The reason is because when an appModule or globalPlugin's chooseNVDAObjectOverlayClasses method is executed, other overlayClasses, such as List, have not yet been applied to the NVDAObject.
Alberto:
ok, understand. Thanks Mick for suggestion! :)
Alberto


Re: Strange behavior in class overlay

Michael Curran
 

Hi,


The reason is because when an appModule or globalPlugin's chooseNVDAObjectOverlayClasses method is executed, other overlayClasses, such as List, have not yet been applied to the NVDAObject. They should however already be in clsList, and you could check for that. E.g. if List in clsList.


Mick

On 11/03/2020 10:34 pm, Alberto Buffolino wrote:
Hi all,
refactoring my add-on ColumnsReview:
https://github.com/ABuffEr/columnsReview
according to an old Joseph's observation, I modified the chooseNVDAObjectOverlayClasses, changing these lines from:
***
        if announceEmptyList and obj.role == ct.ROLE_LIST and "listview" in obj.windowClassName.lower():
            clsList.insert(0, EmptyList)
***
to:
***
        if announceEmptyList and isinstance(obj, List):
            clsList.insert(0, EmptyList)
***
But, for some reason, it works only in the first way. I'm confused, because if I open NVDA console over the list object, and check manually the isinstance condition, this is true.
Can someone provide a explanation?
Thanks in advance.
Alberto


Re: RE : [nvda-devel] Saying Hello!

Shubham Jain
 

Hi Arnold!

That sounds like an awesome programme! I would love to hear more about it.
Excited to learn from, and work with you :)

regards,
Shubham Jain


Strange behavior in class overlay

Alberto Buffolino
 

Hi all,
refactoring my add-on ColumnsReview:
https://github.com/ABuffEr/columnsReview
according to an old Joseph's observation, I modified the chooseNVDAObjectOverlayClasses, changing these lines from:
***
if announceEmptyList and obj.role == ct.ROLE_LIST and "listview" in obj.windowClassName.lower():
clsList.insert(0, EmptyList)
***
to:
***
if announceEmptyList and isinstance(obj, List):
clsList.insert(0, EmptyList)
***
But, for some reason, it works only in the first way. I'm confused, because if I open NVDA console over the list object, and check manually the isinstance condition, this is true.
Can someone provide a explanation?
Thanks in advance.
Alberto


Re: Add-on Updater 20.03 is on its way

Brian's Mail list account
 

Well I guess if it just does not work then you will see it in the log.
The idea though is to attempt to stop old unsupported code from working to keep things stable I suppose, Its a shame that the writers of Python could not have somehow made certain bits still work as they used to, but I guess that could cause conflicts if multiple code paths used different methods and tried to run at the same time. Ouch.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Joseph Lee" <@joslee>
To: <nvda-devel@groups.io>
Sent: Tuesday, March 10, 2020 8:51 AM
Subject: Re: [nvda-devel] Add-on Updater 20.03 is on its way


Hi,
It's really up to NVDA to check for things like that - manifests can fool
users, but it can't fool Python sometimes.
Cheers,
Joseph

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Brian's Mail
list account via Groups.Io
Sent: Tuesday, March 10, 2020 12:54 AM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Add-on Updater 20.03 is on its way

How will the compatibility check be done for existing add ons if somebody
updates a python 2 version later to the next python 3 and only adds the add
on updater at that time, will it then disable the old add ons or just fall
over?
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users
----- Original Message -----
From: "Joseph Lee" <@joslee>
To: <nvda-devel@groups.io>
Sent: Monday, March 09, 2020 9:45 PM
Subject: [nvda-devel] Add-on Updater 20.03 is on its way


Hi all,



Add-on Updater 20.03 is on its way - to be released within the next 24
hours. This release is important (and mandatory): from now on, NVDA
2019.3.1
or later will be required. Also, starting from this release, Add-on
Updater
will no longer check for compatibility range - the add-on will defer to
NVDA
when it comes to checking add-on compatibility.



Cheers,

Joseph









Re: I'm curious about a styling choice in NVDA's code

Alex Hall
 

I use a customized version of "most". Normally, when I'm coding, I rely on the pause Espeak inserts to know where commas are. I find "all" to be too verbose, preferring the easily-distinguished pause to having to hear "comma" aloud. At least with Espeak, though, a comma between two words isn't spoken or indicated at all if no space is between it and the following word. This makes argument or parameter lists run together as a single, unbroken sentence with no pauses at all.

On Tue, Mar 10, 2020 at 9:19 AM Reef Turner <reef@...> wrote:

Hi Alex,

 

What is your “Punctuation/symbol level” set to? You can use NVDA+p to toggle through the options, or check the option in the NVDA settings, speech category.

 

When set to all, the comma should be announced.

 

Regards,

Reef (NV Access)

 

From: nvda-devel@groups.io On Behalf Of Alex Hall
Sent: Thursday, 5 March 2020 12:32 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] I'm curious about a styling choice in NVDA's code

 

Makes sense. Thanks for the explanation.

 

On Thu, Mar 5, 2020 at 3:07 AM Julien Cochuyt <j.cochuyt@...> wrote:

Dear Alex,

 

Code styling has been enforced in the last few month with a proper linting of all new contributions merged into the code base of NVDA.

Indeed, a whitespace between the comma and the next call argument is now the rule.

It has nevertheless been decided not to lint existing code, mainly for two reasons:

 - Allow for an easier tracking of contribution history

 - Avoid the risk of causing regressions

 

 

Best regards,

 

Julien Cochuyt

Accessolutions

 

Le mer. 4 mars 2020 à 23:50, Alex Hall <ahall@...> a écrit :

All,

I've noticed that many function calls in NVDA don't place spaces between the comma of one argument and the start of the next argument. Using Espeak, this makes it very hard to read these argument lists, as this synthesizer runs everything together as a single sentence. It basically skips the commas unless there are spaces between them.

 

Given that NVDA's long-time default synthesizer, and one of the best synths for speaking quickly yet precisely, can't articulate without spaces, why was this styling choice made? Is it a hold-over that the team plans to clean up one day, but isn't important enough to bother with? Or is it intentional, and something the developers want contributors to continue to do?

 

It just strikes me as odd, so I figured I'd ask the experts. Thanks for indulging my curiosity.


--

Alex Hall

Automatic Distributors, IT department

ahall@...



--

Alex Hall

Automatic Distributors, IT department

ahall@...



--
Alex Hall
Automatic Distributors, IT department
ahall@...


Re: I'm curious about a styling choice in NVDA's code

Reef Turner
 

Hi Alex,

 

What is your “Punctuation/symbol level” set to? You can use NVDA+p to toggle through the options, or check the option in the NVDA settings, speech category.

 

When set to all, the comma should be announced.

 

Regards,

Reef (NV Access)

 

From: nvda-devel@groups.io On Behalf Of Alex Hall
Sent: Thursday, 5 March 2020 12:32 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] I'm curious about a styling choice in NVDA's code

 

Makes sense. Thanks for the explanation.

 

On Thu, Mar 5, 2020 at 3:07 AM Julien Cochuyt <j.cochuyt@...> wrote:

Dear Alex,

 

Code styling has been enforced in the last few month with a proper linting of all new contributions merged into the code base of NVDA.

Indeed, a whitespace between the comma and the next call argument is now the rule.

It has nevertheless been decided not to lint existing code, mainly for two reasons:

 - Allow for an easier tracking of contribution history

 - Avoid the risk of causing regressions

 

 

Best regards,

 

Julien Cochuyt

Accessolutions

 

Le mer. 4 mars 2020 à 23:50, Alex Hall <ahall@...> a écrit :

All,

I've noticed that many function calls in NVDA don't place spaces between the comma of one argument and the start of the next argument. Using Espeak, this makes it very hard to read these argument lists, as this synthesizer runs everything together as a single sentence. It basically skips the commas unless there are spaces between them.

 

Given that NVDA's long-time default synthesizer, and one of the best synths for speaking quickly yet precisely, can't articulate without spaces, why was this styling choice made? Is it a hold-over that the team plans to clean up one day, but isn't important enough to bother with? Or is it intentional, and something the developers want contributors to continue to do?

 

It just strikes me as odd, so I figured I'd ask the experts. Thanks for indulging my curiosity.


--

Alex Hall

Automatic Distributors, IT department

ahall@...



--

Alex Hall

Automatic Distributors, IT department

ahall@...


RE : [nvda-devel] Saying Hello!

Arnold Loubriat
 

Hi Shubham, and welcome here!

I’m Arnold, one of the many small contributors to the NVDA project. I’m currently enrolled in an AI programme at Epitech Paris, France.

I also had a similar idea in the past, but was lacking knowledge on the topic of image recognition. Helping you implementing such feature in NVDA would allow me to practice my newly acquired skills.

Looking forward to working with you!

Kind regards,

 

Arnold

 

De : shubhamdjain7@...
Envoyé le :mardi 10 mars 2020 10:21
À : nvda-devel@groups.io
Objet :[nvda-devel] Saying Hello!

 

Hello Everyone!
I'm Shubham Jain from Bengaluru, India.

I am a prospective student for the Google Summer of Code 2020 program and would like to work with this wonderful community over the course of this summer!

For my project proposal, I suggested an AI model that generates captions for input images which can then be communicated to the user via the various mechanisms NVDA already has in place. Michael Curran also suggested I add a feature that allows touch-screen users to move their finger over images and be prompted with any recognized object that they slide their finger over.

If you have any suggestions, doubts, ideas, tips or anything else, please do reply! I am looking forward to getting to know and working with all of you :)

regards,
Shubham Jain

 


NVDA reading math contents

=?ISO-2022-JP?Q?=1B$B9b=4082=22=1B=28J?=
 

Hi developers

I found NVDA can read math contents in Microsoft Word without MathPlayer.
And braille output is same as speech text.
Is it possible to let it output as Nemeth braille?
Cheers


Saying Hello!

Shubham Jain
 

Hello Everyone!
I'm Shubham Jain from Bengaluru, India.

I am a prospective student for the Google Summer of Code 2020 program and would like to work with this wonderful community over the course of this summer!

For my project proposal, I suggested an AI model that generates captions for input images which can then be communicated to the user via the various mechanisms NVDA already has in place. Michael Curran also suggested I add a feature that allows touch-screen users to move their finger over images and be prompted with any recognized object that they slide their finger over.

If you have any suggestions, doubts, ideas, tips or anything else, please do reply! I am looking forward to getting to know and working with all of you :)

regards,
Shubham Jain


Re: Add-on Updater 20.03 is on its way

 

Hi,
It's really up to NVDA to check for things like that - manifests can fool
users, but it can't fool Python sometimes.
Cheers,
Joseph

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Brian's Mail
list account via Groups.Io
Sent: Tuesday, March 10, 2020 12:54 AM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Add-on Updater 20.03 is on its way

How will the compatibility check be done for existing add ons if somebody
updates a python 2 version later to the next python 3 and only adds the add
on updater at that time, will it then disable the old add ons or just fall
over?
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users
----- Original Message -----
From: "Joseph Lee" <@joslee>
To: <nvda-devel@groups.io>
Sent: Monday, March 09, 2020 9:45 PM
Subject: [nvda-devel] Add-on Updater 20.03 is on its way


Hi all,



Add-on Updater 20.03 is on its way - to be released within the next 24
hours. This release is important (and mandatory): from now on, NVDA
2019.3.1
or later will be required. Also, starting from this release, Add-on
Updater
will no longer check for compatibility range - the add-on will defer to
NVDA
when it comes to checking add-on compatibility.



Cheers,

Joseph