Leonard de Ruijter

> Can you resolve this by typing a Capital followed by a lowercase letter? Yes. > If so, that is a problem I know well from Linux versions of eSpeak,...

I wonder whether this change justifies a restructure of the dialog that changes debug logging and add-ons disabled to check boxes.

I guess this is currently blocked by the fact that we can't yet distinguish between a terminal with and without notifications at the time of initializing the overlay classes.

According to https://github.com/microsoft/terminal/issues/13601#issuecomment-1217144689, all WT versions that are currently supported have UIA notifications implemented. Therefore it is safe to drop the older approach for Windows Terminal, at least for NVDA...

Did this work on Python 2 versions of NVDA? I guess this applies to almost every synthesizer.

Marking this p3, as it is unlikely that one would feel very comfortable with having synthesizer pitch at 0. Having said that, it should be pretty easy to fix.

How does movement by the page unit behave in consoles? Wouldn't it be better and more consistent to add review commands to move the review cursor by page?

> Strangely enough (at least to me), the `TextInfo` retrieved that way does not contain the selection, but rather "\ufffc\ufffc\ufffc\ufffc\ufffc\ufffc\ufffc" and has offsets (2, 3) if there is a selection,...

Something like this: ``` from NVDAObjects.IAccessible.ia2TextMozilla import MozillaCompoundTextInfo info = MozillaCompoundTextInfo(self.rootNVDAObject, textInfos.POSITION_SELECTION) ``` Note that CompoundTextInfo is very performance heavy

I think either Mozilla or Chromium based. The Mozilla name is a bit misleading here, probably because Firefox came first with their IA2 implementation. For IE, I Wouldn't bother that...