Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

NVDA next 10237: reading version numbers in commas instead of dots #3814

Closed
nvaccessAuto opened this issue Jan 24, 2014 · 7 comments
Closed

NVDA next 10237: reading version numbers in commas instead of dots #3814

nvaccessAuto opened this issue Jan 24, 2014 · 7 comments
Labels
blocked/needs-external-fix bug/regression bug component/speech

Comments

@nvaccessAuto
Copy link

Reported by domasofan on 2014-01-24 14:39
Hi all,

Just discovered this while i was updating from nvda next 10190 to 10237.
anyone noticed this with nvda that it says for example one comma two comma three when i write 1.2.3.
this seems to be in english and german at least.
in next 10190 it said as it should 1 point 2 point 3.
my local espeak install which i used from the command prompt seems not to say this at all.

would be nice if this could be fixed.

greetings,
simon
Blocked by #3842
@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2014-01-24 17:18
This is a bug in the eSpeak development version we're currently using for next to fix some crashes. Jonathan noted that he has fixed this and there will be a new release soon.

@nvaccessAuto
Copy link
Author

Comment 2 by domasofan (in reply to comment 1) on 2014-01-24 19:31
ah thanks for the info.

greetings,
simon
Replying to jteh:

This is a bug in the eSpeak development version we're currently using for next to fix some crashes. Jonathan noted that he has fixed this and there will be a new release soon.

@nvaccessAuto
Copy link
Author

Comment 4 by jteh on 2014-02-03 11:03
Is this fixed in the latest next snapshot? (Even if it is, please just comment; don't close the ticket yet.)

@nvaccessAuto
Copy link
Author

Comment 5 by k_kolev1985 on 2014-02-03 13:46
Yes, Jamie, for me at least it is fixed. Now eSpeak speaks version numbers with dots as it should, instead with commas as it did with the last few "next" snapshots. Thanks!

@nvaccessAuto
Copy link
Author

Comment 6 by domasofan (in reply to comment 4) on 2014-02-03 19:15
hi,

i also confirm that it is fixed and works now as expected.
using next 10291.
thanks very much.

greetings,
simon

Replying to jteh:

Is this fixed in the latest next snapshot? (Even if it is, please just comment; don't close the ticket yet.)

@nvaccessAuto nvaccessAuto mentioned this issue Nov 10, 2015
Closed
@dkager
Copy link
Collaborator

dkager commented Nov 18, 2015

From the comments I gather this can be closed?

@jcsteh
Copy link
Contributor

jcsteh commented Nov 18, 2015

Yup; fixed by #3842.

@jcsteh jcsteh closed this as completed Nov 18, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
blocked/needs-external-fix bug/regression bug component/speech
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dkager @jcsteh @nvaccessAuto