Leonard de Ruijter

I think we can consider closing this given: * The bug in libFFI has been fixed * It is planned to incorporate this update of libFFI into new versions of...

I wonder whether this could have been fixed in the new Baum driver, which also applies to this display.

Woops, sorry for going mad there. [**@jcsteh**](https://github.com/jcsteh) commented on [14 aug. 2017 09:05 CEST](https://github.com/nvaccess/nvda/issues/2315#issuecomment-322114576 "2017-08-14T07:05:19Z - Replied by Github Reply Comments"): > Regardless, this isn't fixed. As I noted in...

[**@jcsteh**](https://github.com/jcsteh) commented on [14 aug. 2017 13:20 CEST](https://github.com/nvaccess/nvda/issues/2315#issuecomment-322165249 "2017-08-14T11:20:26Z - Replied by Github Reply Comments"): > ... Windows released all resources associated with the display... Talking about freeing resources and...

Based on NVDA Remote, we could also go for a completely different implementation. When NVDA is running under the current user profile and the secure desktop is activated, create a...

It is still present. My advise would be to wait for Python 3 and a possible integration of NVDA Remote into core.

I guess to fix this properly, we need an additional behavior in the speech symbol processor that simply discards the symbol as it wasn't there.

I think handling soft hyphens primarily should be a task of the braille table. In the Dutch 8 dot table for example, we ignore it completely.

Would it be worht it to test this during daily use using a try build? Or is this still not mature enough?

@feerrenrut: thinking about this again, have you considered implementing the C++ code in this as a [Python extension](https://docs.python.org/3/extending/extending.html). I really understand that for historical reasons, the local NVDAHelper library was...