Hi, That's an interesting point. I think part of the reason for labeling it that way is due to Python 2 versus Python 3 - the former is ancient now, and the latter is modern. Cheers, Joseph

I don't know how special characters were handled previously, I don't use them. But the suggestion sounds like a very good one. Aside from that, I think that how certain default behaviors are

I'm not thrilled that this add-on is said to work with "modern" NVDA, as some folks think 2019.2.1 is pretty modern already. Why can't that page just say 2019.3 and above, and be done with it?

I would imagine there is a setting to change this behavior but it is another example of a very poor choice for the default being chosen. Are such choices reviewed by a panel of users or perhaps sent

Michael, Java Access Bridge is included with NVDA as of the latest version.

Hello Rui, thank you for your help. But today before I receive your reply, I have reset my laptop because I'm not sure what the problem is. Then I just install NVDA 2019.2.1 and Vocalizer Expressive

Martin, I just checked it again with 2019.2.1. I have the same symptoms there as you describe in 2019.3.1 Please do me a favour and go to your 2019.2.1 installation and press NVDA-Q and restart NVDA

Hello, as anounced I looked up the version of NVDA where it last worked correctly: nvda v2019.2.1 gives the feedback as expected. a "." is spoken emedeately. Other

Ok, then it is a different problem... Rui Fontes Às 12:52 de 12/02/2020, Martin Thomas Swaton escreveu:

Hi Rui, it does not matter where - right now I write in thunderbird, I also tryed firefox and Notebad. It is a global behaviour best, Martin

Hi again, the reboot did not change anything - as expected. @Ralf I had 2019.2 (do not know which one exactly) installed on this computer (and still have it on my

Hi, as I tryed to state, I want typed characters set to off! :-) But still one has to get feedback on typed characters in word mode - they cannot be ignored, they have to be

Hi Quentin, I understood Martin that he discovers that with typed chars off and typed words on. And that can beconfirmed at my end, but it was the same under 2019.2.1 Cheers, Ralf

Hello! Go to the following folder: %appdata%\vocalizer-for-nvda and delete the activation.dat file. Restart NVDA and you will be able to activate again...

Hi Martin, Have you restarted the computer since you updated NVDA? I just tried type a. with speak typed characters on, and NVDA read "A dot" just as you expected. I don't have Eloquence, but it

Yes just buy eloquence because the paid version works much better and gets updated right away. You can buy it from www.atguys.com for around $65.

It must do it with the old driver... If the new driver couldn't remove the activation, the only way is deleting the files in %appdata%\vocalizer-for-nvda. We will increase the remaining activations

My primary TTS engine with NVDA has, for quite a while, been eSpeak-NG. Anyway, partly due to being a programmer, I specifically prefer to stick to having all numbers spoken out as digits, and, thus

Hello! Are you talking when writing in a browser, in Skype and so on? Rui Fontes Às 11:00 de 12/02/2020, Martin Thomas Swaton escreveu:

Hi, I searched for this problem, but could not find a topic on it ... so if this already was asked, I am sorry... Since the update the feedback of special characters and punctuation while typing