Thiago Seus

+1, I also would like to see it merged.

I tested it and also seen this bug, I think it could be a bug on on IntelliJ's end. On my tests, I also tried to add a new Java...

@mwhapples Some time ago I created an issue to address the freeze with example code, but it was converted to a discussion. See https://github.com/nvaccess/nvda/discussions/14461 .

In some cases there might be other factors causing a freeze, for example speech dictionary substitution processing or character processing with a large string and a regexp with a lot...

An expandable code textInfo API might be useful for other editors as well, for example we could expose on this API more information about parenthesis levels for example, so the...

Another idea, maybe this new API could be implemented as an addon, and when opening supported IDEs, NVDA could suggest to install the addon. This could ease implementation of new...

A question, does the normalization could solve the problem of italic or bold unicode characters that synthesizers can't read?

Performed some tests using the latest build on the Windows 10 machine and it continues working as well.

I've also reproduced this bug, but I've noticed when selecting text using the control shift arrow keys, NVDA identifies the word boundaries correctly, there might be a difference between the...

Here's what I discovered so far: it seems the bug is inside the text info, NVDA is constructing its own representation of the text on the [JABTextInfo class](https://github.com/nvaccess/nvda/blob/bf96860d561aa6c1e03f0cbd286be9b04587cb92/source/NVDAObjects/JAB/__init__.py#LL123) based on...