Comment 1 by mdcurran on 2011-06-27 23:32
Can you give a better example of where this really affects you? I'm sure there is one, but its unclear from your previous example. As in, where did you see this in the real world that made you notice the problem.

Comment 2 by jteh on 2011-06-28 03:22
I don't think this is an NVDA issue, as we don't insert spaces or the like after numbers. If I understand correctly, this is related to the specific synth you are using.

Comment 3 by elliott94 (in reply to comment 2) on 2011-06-28 06:56
Replying to jteh:

I don't think this is an NVDA issue, as we don't insert spaces or the like after numbers. If I understand correctly, this is related to the specific synth you are using.

When using ESpeak, this behaviour can be seen. An example of this is on ebuyer.com, where prices are listed without any spaces inbetween.

Comment 4 by MHameed on 2012-10-09 06:28
Does this problem still persist for you with newer versions of espeak?

You might want to download latest sapi5 compatible development version of espeak and see if the problem still happens there.
http://espeak.sourceforge.net/test/latest.html

If so then the fix belongs in espeak.

Comment 5 by elliott94 (in reply to comment 4) on 2012-10-09 06:58
Replying to MHameed:

Does this problem still persist for you with newer versions of espeak?

No, I can still see this particular issue. It doesn't just occur with eSpeak, however. The example that I gave above still gives the same speech output.

Comment 6 by jteh on 2012-10-09 07:05
What speech output? I don't hear any difference between the two cases given in the description of this ticket with eSpeak.

Comment 7 by elliott94 (in reply to comment 6) on 2012-10-09 13:57
Replying to jteh:

What speech output? I don't hear any difference between the two cases given in the description of this ticket with eSpeak.

Basically, £15.21 would read as "fifteen Pounds and twenty one pence". However, something like £15.21 with a letter positioned straight after it would read as "Pounds fifteen point two one", if that makes sense.

Comment 8 by jteh on 2012-10-09 21:49
As I said, this is an issue with the synth. I still can't get this to happen with eSpeak, though. It always just says pound fifteen point two one.

I am experiencing the same results as @jcsteh in #1615 (comment) with no dictionary entries using the latest ESpeak NG. Closing