We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Steps to reproduce:
Read the following line in an editor which displays it in one entire line, such as Notepad++:
https://www.quora.com/qemail/track_click?uid=84yIVIuDx4x&al_imp=eyJoYXNoIjogIjE4NjY1OTE2NTEyODM4NjE0MDZ8MXwxfDIxNDA5MzcyIiwgInR5cGUiOiAzM30%3D&aoid=Yu5OqPucJld&request_id=1866591651283861406&aoty=2&et=2&al_pri=QuestionLinkClickthrough&id=yW-rqVp48N_cxPtRUMb3wA%3D%3D&ct=1464855319030676&src=1&ty_data=9gmvYcWTEn6&ty=1&click_pos=1&st=1464855319030676&source=1&stories=1_9gmvYcWTEn6|1_SWXfVGSfFP|1_dJLCSyqwgEK|1_zPhdCJfCtKS|1_FCZfSjj8QT|1_VcZUYZR1p8P|1_YyIMgwcLFc4|1_XHZJlXRySrF|1_bUbeecdjbM7|1_MHJr1MtCGM4&v=0&aty=4
Expected result: the line should be read.
Actual result: the error sound is played. Here is the log output when this happens:
WindowsError: exception: access violation writing 0x72581A07 ERROR - synthDrivers._espeak.BgThread.run (17:34:52): Error running function from queue Traceback (most recent call last): File "synthDrivers\_espeak.pyc", line 156, in run File "synthDrivers\_espeak.pyc", line 177, in _speak WindowsError: exception: access violation writing 0x72581A07
The text was updated successfully, but these errors were encountered:
I think this is fixed in eSpeakNG and therefore NVDA 2016.2?
Sorry, something went wrong.
Yes, fixed before the NVDA2016.2 releasing. If this error occours with a specific language, please report on espeak-ng issues. Thanks.
Fixed as part of #5651.
No branches or pull requests
Steps to reproduce:
Read the following line in an editor which displays it in one entire line, such as Notepad++:
Expected result: the line should be read.
Actual result: the error sound is played. Here is the log output when this happens:
The text was updated successfully, but these errors were encountered: