Date   
Re: problems opening the task manager

ChrisLM
 

Hi,

I'm trying to understand more its behavior.
In practice, after open the task manager and press down arrow the speech synthesis stops speaking. All screen reader commands do not work, and often  NVDA needs to be restarted.
When I press ctrl+TAB to switch tabs NVDA announces unknown, sometimes NVDA says nothing.
I'm testing the latest alpha versions and running NVDA from source,
on Windows 10Ver1909 (64-bit) build 18363.592.

Cheers,


Chris.

James Scholes ha scritto il 06/02/2020 alle 22:22:

...the purpose of this thread isn't really clear. @ChrisLM, could you expand on the problems you're experiencing with the Task Manager, or opening it, or whatever specific area of functionality isn't working?  I've just pressed Ctrl+Shift+Escape, the Task Manager opened, so what next?

Re: problems opening the task manager

James Scholes
 

The task manager in Windows 10 is completely different to the one in Windows 7. It has some significant problems, and many people would probably say it was worse than the previous incarnation (myself included).

With that said, though, the purpose of this thread isn't really clear. @ChrisLM, could you expand on the problems you're experiencing with the Task Manager, or opening it, or whatever specific area of functionality isn't working? I've just pressed Ctrl+Shift+Escape, the Task Manager opened, so what next?

@Noelia, the Task Manager isn't written in Java, so I'm not sure what any Java issues have to do with it.

Regards,

James Scholes

On 06/02/2020 at 2:37 pm, Brian's Mail list account via Groups.Io wrote:
How come it works so well in Windows 7, though?
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: "Noelia Ruiz" <nrm1977@...>
To: <nvda-devel@groups.io>
Sent: Thursday, February 06, 2020 3:20 AM
Subject: Re: [nvda-devel] problems opening the task manager
Hi, me too. Maybe related to recent Java support?
This is listened and shown in speech viewer:
C:\Program Files\Java\jre1.8.0_211\bin\jabswitch.exe  terminal
The Java Access Bridge has been
If you run source master, not an installed copy, though Java support
is not enabled from NVDA itself, maybe affected by a previous try if
you didn't restart the computer?
David is mentioning some previous issues, but I think this can be different.
Also, years ago NV Access worked on performance issues also related to
task viewer:
https://github.com/nvaccess/nvda/issues/5293
https://github.com/nvaccess/nvda/commit/020e3f63349357f06ac1bf7f1c62ac4dd66e99d1 Hope this helps
2020-02-05 23:40 GMT+01:00, ChrisLM <@Christianlm>:
Hi,

before open a issue, can someone else try to open the windows task
manager with control+shift+escape, or run taskmgr?

I have encountered serious problems in the task manager dialog using
last NVDA rc3, last alpha and running the source master...


cheers,



--
Chris.




Re: problems opening the task manager

Brian's Mail list account
 

How come it works so well in Windows 7, though?
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: "Noelia Ruiz" <nrm1977@...>
To: <nvda-devel@groups.io>
Sent: Thursday, February 06, 2020 3:20 AM
Subject: Re: [nvda-devel] problems opening the task manager


Hi, me too. Maybe related to recent Java support?
This is listened and shown in speech viewer:
C:\Program Files\Java\jre1.8.0_211\bin\jabswitch.exe terminal
The Java Access Bridge has been

If you run source master, not an installed copy, though Java support
is not enabled from NVDA itself, maybe affected by a previous try if
you didn't restart the computer?
David is mentioning some previous issues, but I think this can be different.
Also, years ago NV Access worked on performance issues also related to
task viewer:

https://github.com/nvaccess/nvda/issues/5293
https://github.com/nvaccess/nvda/commit/020e3f63349357f06ac1bf7f1c62ac4dd66e99d1

Hope this helps


2020-02-05 23:40 GMT+01:00, ChrisLM <@Christianlm>:
Hi,

before open a issue, can someone else try to open the windows task
manager with control+shift+escape, or run taskmgr?

I have encountered serious problems in the task manager dialog using
last NVDA rc3, last alpha and running the source master...


cheers,



--
Chris.




make UIA object focusable and to a button #3030-advice

Christopher Pross
 

Hey guys,
at the moment I have a problem with some add-on code.
I have a element, wich is type "unknown", it is in fact a button, but also it isn't focusable.
The problem is, that I can't change the type or make it focusable. I don't know why, maybe I do somethink wrong?

First of all, the devInfo:

["name: ''", 'role: ROLE_UNKNOWN', 'roleText: None', 'states: ', 'isFocusable: False', 'hasFocus: False', 'Python object: <NVDAObjects.UIA.UIA object at 0x03D6B5F0>', "Python class mro: (<class 'NVDAObjects.UIA.UIA'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <class 'object'>)", "description: ''", 'location: RectLTWH(left=730, top=133, width=15, height=15)', 'value: None', "appModule: <'nordvpn' (appName 'nordvpn', process ID 11136) at address 758ae30>", "appModule.productName: 'NordVPN'", "appModule.productVersion: '6.26.15.0'", "TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>", 'windowHandle: 66774', "windowClassName: 'HwndWrapper[NordVPN.exe;;39c90ffe-7554-4757-a831-d0403c1908a7]'", 'windowControlID: 0', 'windowStyle: 382664704', 'extendedWindowStyle: 262400', 'windowThreadID: 11140', "windowText: 'NordVPN '", "displayText: ''", 'UIAElement: <POINTER(IUIAutomationElement) ptr=0x81a3a20 at d9cacb0>', 'UIA automationID: Sign', 'UIA frameworkID: WPF', 'UIA runtimeID: (7, 11136, 9930698)', 'UIA providerDescription: [pid:11136,providerId:0x0 Main(parent link):Unidentified Provider (managed:MS.Internal.Automation.ElementProxy, PresentationCore, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35)]', 'UIA className: CloseSign', 'UIA patterns available: LegacyIAccessiblePattern, SynchronizedInputPattern']

My add-on code was active in this case already..
In the event_NVDAObject_init, in some if-statements, I have this code:

ch.role = controlTypes.ROLE_BUTTON
ch.states.add(controlTypes.STATE_FOCUSABLE)
ch.isFocusable = True

In the protocol of nvda, is no traceback or exception, no warning or somethink else.
I don't know, why this element don't change his type and the state.
If I try to force to set the focus, I get a traceback, but I think because it isn't focuable:

>>> nav.next.setFocus() Traceback (most recent call last): File "<console>", line 1, in <module> File "NVDAObjects\UIA\__init__.pyc", line 1094, in setFocus File "comtypesMonkeyPatches.pyc", line 26, in __call__ _ctypes.COMError: (-2146233079, None, (None, None, None, 0, None))

Maybe you know what is wrong here?

all the best,
Christopher

Re: Where is CapsLock management?

Alberto Buffolino
 

Noelia Ruiz, il 06/02/2020 12.31, ha scritto:
Hi, I think you may look at keyboardHandler.py in different functions
including internal_keyDownEvent, internal_keyUpEvent and
_reportToggleKey, since there are things that maybe common to other
modifiers, not just capsLoc.
Alberto:
Yeah, found. Thanks Noelia, I forgot the other toggle keys, so I have no results in search previously.
Alberto

Re: Where is CapsLock management?

Noelia Ruiz
 

Hi, I think you may look at keyboardHandler.py in different functions
including internal_keyDownEvent, internal_keyUpEvent and
_reportToggleKey, since there are things that maybe common to other
modifiers, not just capsLoc.
Also you can use git grep -i -n capslock or toggle, etc, for a wider
context and get an idea about where to search.
Cheers

2020-02-06 9:41 GMT+01:00, Alberto Buffolino <a.buffolino@...>:

Hi,
I'm talking about NVDA sources and capsLock status management.
I'm quite sure to have seen it years ago, but I cannot find it today.
Where is it?
Thanks.
Alberto



Re: NVDA crashes if non-ASCII characters are in the path

zvonimir stanečić, 9a5dsz
 

Btw, can you merge all translations from beta to master?
Rc3 has no problems with them

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Reef Turner
Sent: Thursday, February 6, 2020 11:07 AM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] NVDA crashes if non-ASCII characters are in the path

One possible work-around (that I don't like very much) would be to detect the crash conditions on start up (espeak synth, path with non-ASCII), warn the user and set a different synth.

-----Original Message-----
From: nvda-devel@groups.io On Behalf Of Nikita
Sent: Wednesday, 5 February 2020 7:38 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] NVDA crashes if non-ASCII characters are in the path

Unfortunately, this is a rather serious problem, the danger of which is probably underestimated.
Because of this problem, it is impossible to run new NVDA if the path to unpacked version contains non-ASCII characters.
As a result, inexperienced users may not understand why the new NVDA portable does not start.
There are Non-ASCII characters in languages based on the Latin alphabet, for example, French, German, Spanish. The so-called diacritics.
It is also bad that the log of NVDA does not contain any errors. NVDA crashes before it has time to write something.
This is an old bug that manifested even in Python 2 versions. That is not a problem of Python 3 migration.

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Brian's Mail list account via Groups.Io
Sent: Wednesday, February 05, 2020 8:54 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] NVDA crashes if non-ASCII characters are in the path

I wonder how many people this might affect? If somebody likes espeak, one supposes this will be people who use other languages than the Latin based ones with this synth. I could not see the issue on the Espeak mail list, so suspect its been around for a while. Could an older version be used to temporarily fix this as it might make some people not want to switch, assuming of course the problem is not already in the current stable python 2. I'd not know.

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: "Reef Turner" <reef@...>
To: <nvda-devel@groups.io>
Sent: Wednesday, February 05, 2020 9:10 AM
Subject: Re: [nvda-devel] NVDA crashes if non-ASCII characters are in the path


Hi Nikita,

Thanks for pointing this out. It is a known issue [1]. We are confident this is caused by an issue in espeak and there is little we can do about it in the short term. We hope that the espeak maintainers will fix this issue, but unfortunately it is too late for a fix to be included in 2019.3.

[1] https://github.com/nvaccess/nvda/issues/10607

Re: NVDA crashes if non-ASCII characters are in the path

zvonimir stanečić, 9a5dsz
 

No, the second possible solution is to use original non modified espeak (last version from Jonathan Duddington.
The developer of espeak NG only uses Linux and all things are getting only worse.
As a workaround, I would like to try the oldest version possible, as it can also affect the user account paths that are written with accented characters or in other script.The problem is in espeak NG, but not on other synths like codefactory vocalizer or acapela.

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Reef Turner
Sent: Thursday, February 6, 2020 11:07 AM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] NVDA crashes if non-ASCII characters are in the path

One possible work-around (that I don't like very much) would be to detect the crash conditions on start up (espeak synth, path with non-ASCII), warn the user and set a different synth.

-----Original Message-----
From: nvda-devel@groups.io On Behalf Of Nikita
Sent: Wednesday, 5 February 2020 7:38 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] NVDA crashes if non-ASCII characters are in the path

Unfortunately, this is a rather serious problem, the danger of which is probably underestimated.
Because of this problem, it is impossible to run new NVDA if the path to unpacked version contains non-ASCII characters.
As a result, inexperienced users may not understand why the new NVDA portable does not start.
There are Non-ASCII characters in languages based on the Latin alphabet, for example, French, German, Spanish. The so-called diacritics.
It is also bad that the log of NVDA does not contain any errors. NVDA crashes before it has time to write something.
This is an old bug that manifested even in Python 2 versions. That is not a problem of Python 3 migration.

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Brian's Mail list account via Groups.Io
Sent: Wednesday, February 05, 2020 8:54 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] NVDA crashes if non-ASCII characters are in the path

I wonder how many people this might affect? If somebody likes espeak, one supposes this will be people who use other languages than the Latin based ones with this synth. I could not see the issue on the Espeak mail list, so suspect its been around for a while. Could an older version be used to temporarily fix this as it might make some people not want to switch, assuming of course the problem is not already in the current stable python 2. I'd not know.

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: "Reef Turner" <reef@...>
To: <nvda-devel@groups.io>
Sent: Wednesday, February 05, 2020 9:10 AM
Subject: Re: [nvda-devel] NVDA crashes if non-ASCII characters are in the path


Hi Nikita,

Thanks for pointing this out. It is a known issue [1]. We are confident this is caused by an issue in espeak and there is little we can do about it in the short term. We hope that the espeak maintainers will fix this issue, but unfortunately it is too late for a fix to be included in 2019.3.

[1] https://github.com/nvaccess/nvda/issues/10607

Re: NVDA crashes if non-ASCII characters are in the path

Reef Turner
 

One possible work-around (that I don't like very much) would be to detect the crash conditions on start up (espeak synth, path with non-ASCII), warn the user and set a different synth.

-----Original Message-----
From: nvda-devel@groups.io On Behalf Of Nikita
Sent: Wednesday, 5 February 2020 7:38 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] NVDA crashes if non-ASCII characters are in the path

Unfortunately, this is a rather serious problem, the danger of which is probably underestimated.
Because of this problem, it is impossible to run new NVDA if the path to unpacked version contains non-ASCII characters.
As a result, inexperienced users may not understand why the new NVDA portable does not start.
There are Non-ASCII characters in languages based on the Latin alphabet, for example, French, German, Spanish. The so-called diacritics.
It is also bad that the log of NVDA does not contain any errors. NVDA crashes before it has time to write something.
This is an old bug that manifested even in Python 2 versions. That is not a problem of Python 3 migration.

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Brian's Mail list account via Groups.Io
Sent: Wednesday, February 05, 2020 8:54 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] NVDA crashes if non-ASCII characters are in the path

I wonder how many people this might affect? If somebody likes espeak, one supposes this will be people who use other languages than the Latin based ones with this synth. I could not see the issue on the Espeak mail list, so suspect its been around for a while. Could an older version be used to temporarily fix this as it might make some people not want to switch, assuming of course the problem is not already in the current stable python 2. I'd not know.

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: "Reef Turner" <reef@...>
To: <nvda-devel@groups.io>
Sent: Wednesday, February 05, 2020 9:10 AM
Subject: Re: [nvda-devel] NVDA crashes if non-ASCII characters are in the
path


Hi Nikita,

Thanks for pointing this out. It is a known issue [1]. We are confident this
is caused by an issue in espeak and there is little we can do about it in
the short term. We hope that the espeak maintainers will fix this issue, but
unfortunately it is too late for a fix to be included in 2019.3.

[1] https://github.com/nvaccess/nvda/issues/10607

Where is CapsLock management?

Alberto Buffolino
 

Hi,
I'm talking about NVDA sources and capsLock status management.
I'm quite sure to have seen it years ago, but I cannot find it today.
Where is it?
Thanks.
Alberto

Re: problems opening the task manager

Brian's Mail list account
 

Yes they certainly do. I just tried it I blame Microsoft buggy UIA as usual.
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: "DaVid" <dhf360@...>
To: "nvda-devel" <nvda-devel@groups.io>
Sent: Wednesday, February 05, 2020 11:10 PM
Subject: Re: [nvda-devel] problems opening the task manager


You're talking about the slow response when opening the task manager?
Its a very known issue, but some people thought that is not relevant to
solve. I installed the task manager of windows 7, where all the tings work
properly.

Regards,
David CM
Ingeniero en computación (ITCR)
[image: Experto certificado en NVDA.] <https://certification.nvaccess.org/>
correo: dhf360@...

Encuentra mis proyectos libres en github. <https://github.com/davidacm/>
y las publicaciones en mi canal de youtube.
<https://www.youtube.com/channel/UCYnnJZQLYHd7g0R3UcJ9-lg>

Suscríbite y aprende en mis grupos de correo y facebook:
Programación accesible:
Envía un correo de suscripción a la dirección:
programacionaccesible+subscribe@...
O participa en Programación accesible en Facebook.
<https://facebook.com/groups/235117436637120>

tiflotronica: Si te gusta la electricidad y los chips ¡Aprende y aporta
sobre este tema tan apasionante!
Envía un correo de suscripción a la dirección:
tiflotronica+subscribe@...
Si te gusta la producción o ejecución de instrumentos musicales, participa
en Músicos ciegos y de baja visión en facebook.
<https://facebook.com/groups/590594451020594>
También puedes hacer tus consultas sobre tu lector de pantallas favorito en
la comunidad de NVDA en español (facebook)
<https://facebook.com/groups/298402187029900>


El mié., 5 feb. 2020 a las 16:40, ChrisLM (<@Christianlm>) escribió:

Hi,

before open a issue, can someone else try to open the windows task
manager with control+shift+escape, or run taskmgr?

I have encountered serious problems in the task manager dialog using
last NVDA rc3, last alpha and running the source master...


cheers,



--
Chris.




Re: problems opening the task manager

Noelia Ruiz
 

Hi, me too. Maybe related to recent Java support?
This is listened and shown in speech viewer:
C:\Program Files\Java\jre1.8.0_211\bin\jabswitch.exe terminal
The Java Access Bridge has been

If you run source master, not an installed copy, though Java support
is not enabled from NVDA itself, maybe affected by a previous try if
you didn't restart the computer?
David is mentioning some previous issues, but I think this can be different.
Also, years ago NV Access worked on performance issues also related to
task viewer:

https://github.com/nvaccess/nvda/issues/5293
https://github.com/nvaccess/nvda/commit/020e3f63349357f06ac1bf7f1c62ac4dd66e99d1

Hope this helps


2020-02-05 23:40 GMT+01:00, ChrisLM <@Christianlm>:

Hi,

before open a issue, can someone else try to open the windows task
manager with control+shift+escape, or run taskmgr?

I have encountered serious  problems in the task manager dialog using
last NVDA rc3, last alpha and running the source master...


cheers,



--
Chris.




Re: problems opening the task manager

DaVid
 

You're talking about the slow response when opening the task manager?
Its a very known issue, but some people thought that is not relevant to solve. I installed the task manager of windows 7, where all the tings work properly.

Regards,
David CM
Ingeniero en computación (ITCR)
Experto certificado en NVDA.
correo: dhf360@...

Encuentra mis proyectos libres en github.
y las publicaciones en mi canal de youtube.

Suscríbite y aprende en mis grupos de correo y facebook:
Programación accesible:
Envía un correo de suscripción a la dirección: programacionaccesible+subscribe@...
O participa en Programación accesible en Facebook.

tiflotronica: Si te gusta la electricidad y los chips ¡Aprende y aporta sobre este tema tan apasionante!
Envía un correo de suscripción a la dirección: tiflotronica+subscribe@...
Si te gusta la producción o ejecución de instrumentos musicales, participa en Músicos ciegos y de baja visión en facebook.
También puedes hacer tus consultas sobre tu lector de pantallas favorito en la comunidad de NVDA en español (facebook)


El mié., 5 feb. 2020 a las 16:40, ChrisLM (<llajta2012@...>) escribió:
Hi,

before open a issue, can someone else try to open the windows task
manager with control+shift+escape, or run taskmgr?

I have encountered serious  problems in the task manager dialog using
last NVDA rc3, last alpha and running the source master...


cheers,



--
Chris.




problems opening the task manager

ChrisLM
 

Hi,

before open a issue, can someone else try to open the windows task manager with control+shift+escape, or run taskmgr?

I have encountered serious  problems in the task manager dialog using last NVDA rc3, last alpha and running the source master...


cheers,



--
Chris.

Re: NVDA crashes if non-ASCII characters are in the path

Nikita
 

Unfortunately, this is a rather serious problem, the danger of which is probably underestimated.
Because of this problem, it is impossible to run new NVDA if the path to unpacked version contains non-ASCII characters.
As a result, inexperienced users may not understand why the new NVDA portable does not start.
There are Non-ASCII characters in languages based on the Latin alphabet, for example, French, German, Spanish. The so-called diacritics.
It is also bad that the log of NVDA does not contain any errors. NVDA crashes before it has time to write something.
This is an old bug that manifested even in Python 2 versions. That is not a problem of Python 3 migration.

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Brian's Mail list account via Groups.Io
Sent: Wednesday, February 05, 2020 8:54 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] NVDA crashes if non-ASCII characters are in the path

I wonder how many people this might affect? If somebody likes espeak, one
supposes this will be people who use other languages than the Latin based
ones with this synth. I could not see the issue on the Espeak mail list, so
suspect its been around for a while. Could an older version be used to
temporarily fix this as it might make some people not want to switch,
assuming of course the problem is not already in the current stable python
2. I'd not know.

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: "Reef Turner" <reef@...>
To: <nvda-devel@groups.io>
Sent: Wednesday, February 05, 2020 9:10 AM
Subject: Re: [nvda-devel] NVDA crashes if non-ASCII characters are in the
path


Hi Nikita,

Thanks for pointing this out. It is a known issue [1]. We are confident this
is caused by an issue in espeak and there is little we can do about it in
the short term. We hope that the espeak maintainers will fix this issue, but
unfortunately it is too late for a fix to be included in 2019.3.

[1] https://github.com/nvaccess/nvda/issues/10607

Re: NVDA crashes if non-ASCII characters are in the path

Brian's Mail list account
 

I wonder how many people this might affect? If somebody likes espeak, one supposes this will be people who use other languages than the Latin based ones with this synth. I could not see the issue on the Espeak mail list, so suspect its been around for a while. Could an older version be used to temporarily fix this as it might make some people not want to switch, assuming of course the problem is not already in the current stable python 2. I'd not know.

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: "Reef Turner" <reef@...>
To: <nvda-devel@groups.io>
Sent: Wednesday, February 05, 2020 9:10 AM
Subject: Re: [nvda-devel] NVDA crashes if non-ASCII characters are in the path


Hi Nikita,

Thanks for pointing this out. It is a known issue [1]. We are confident this is caused by an issue in espeak and there is little we can do about it in the short term. We hope that the espeak maintainers will fix this issue, but unfortunately it is too late for a fix to be included in 2019.3.

[1] https://github.com/nvaccess/nvda/issues/10607

NVDA 2019.3rc3 now available for testing

Reef Turner
 

Hi all,

 

NVDA 2019.3rc3 has just been released for testing.

 

Changes from RC2:

 

• Updated translations for many languages

 

 

Full blog post: https://www.nvaccess.org/post/nvda-2019-3rc3-now-available-for-testing/

 

Reef Turner
Software Developer 

 

www.nvaccess.org

Facebook: https://www.facebook.com/NVAccess
Twitter: @NVAccess 

 

Re: NVDA crashes if non-ASCII characters are in the path

Reef Turner
 

Hi Nikita,

Thanks for pointing this out. It is a known issue [1]. We are confident this is caused by an issue in espeak and there is little we can do about it in the short term. We hope that the espeak maintainers will fix this issue, but unfortunately it is too late for a fix to be included in 2019.3.


[1] https://github.com/nvaccess/nvda/issues/10607

NVDA crashes if non-ASCII characters are in the path

Nikita
 

Hello everybody!

Now if the path to the nvda.exe contains non-ASCII characters, the NVDA will crash.

At a minimum, the problematic component is eSpeak. With some other synthesizers, NVDA may start.

However, I'm not sure that eSpeak is the only component experiencing such problems.

Tell me, please, is this a known problem?

If so, is it considered a bug that is planned to be fixed?

Regards, Nikita.

NVDA 2019.3 and add-ons: more add-ons buying compatibility ticket

 

Hi NVDA developers and add-ons community,

 

Since we had two betas in a span of days, I figured it is time to give you an update as to what’s going on with add-ons and their compatibility with 2019.3:

 

There’s nothing to report expect…

 

NVDA Remote add-on is getting closer to making itself NVDA 2019.3 ready. Python 3 compatibility code from NV Access was merged into NVDA Remote add-on repo with some work to be done. Thus the compatibility status for this add-on is now “work in progress”.

 

Hopefully the next briefing will be sent when 2019.3 release candidate (RC) is sent. At that point, the add-ons community should enter release preparation phase where authors should start publishing NVDA 2019.3 compatible versions of add-ons or announce when compatible versions will be released to stable channel (I myself will publish schedule for my add-ons within 24 hours after 2019.3 RC goes out).

 

Cheers,

Joseph