1. Messages
  2. NVDA reading number

Re: NVDA reading number

Brian's Mail list account <bglists@...>
 

Basically as the previous person said, if its fine on Espeak and the windows 10 one core voices, the issue is most likely to be synthesiser related and you may need to change your synth, or contact the vendors.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "aikeo koomanivong" <moykoomanivong@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Thursday, April 11, 2019 3:23 PM
Subject: Re: [nvda] NVDA reading number


Hi all
I’m using NVDA with vocalizer and some sapi5
In the pass it was read well but I’m not sure when it’s happened
All of computer here also facing the same problems
I’m using latest NVDA
Or maybe that would be happened on my own TTS
Because Lao TTS not good on developing and maybe it has been modified some point on NVDA
Just guess
ฟืาห

Sent from Mail for Windows 10

From: Andre Fisher
Sent: Thursday, April 11, 2019 6:15 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA reading number

Hi.

Which synthesizer do you face this problem with, and which language is it set to? Using eSpeak and Windows OneCore Voices with English variants, I don't face this problem. Also, which version of NVDA are you using?
Join nvda@nvda.groups.io to automatically receive all group messages.