Attachment log wikipedia.txt added by Sukil on 2014-10-15 13:27
Description:
Log file, just with the string I suspect that originated the crash. Logging level set to debug.

Comment 1 by jteh on 2014-10-15 22:06
Confirmed.

Technical: Both Chinese characters U+4e2d and U+6587 cause this crash, but only when speaking as characters. You can reproduce it by passing the following SSML to eSpeak:

<voice xml:lang="zh"><say-as interpret-as="characters">\u4e2d</say-as></voice>

Comment 3 by Sukil on 2014-10-27 20:38
Is Jonathan already aware of this?

Comment 4 by jteh on 2014-10-28 00:11
Probably not. Based on past experience, it's also possible it doesn't occur in his build, since he builds with an older compiler and different settings.

Hi, I have tried that SSML string on my espeak-ng linux build and espeak 1.48.15 and get:

(en)b'a55ksla55S_!(zh)_| j'iou55_!_| s'i[51_!_| j'i51_!_| '@r51_!_| t'i51_!_|

Looking at the code, I can't see anywhere it is handling \uNNNN style character markup. Additionally, the SSML documents for the say-as attribute values don't mention that syntax.

NOTE: Using 中 results in espeak saying (with the default, incomplete dictionary):

ts.'ong55_!_|

What compiler and settings are you using on Windows?

Thanks for looking at this @rhdunn.

Looking at the code, I can't see anywhere it is handling \uNNNN style character markup. Additionally, the SSML documents for the say-as attribute values don't mention that syntax.

Oops. I must have copied the raw string from Python. That should be:

<voice xml:lang="zh"><say-as interpret-as="characters">中</say-as></voice>

NOTE: Using 中 results in espeak saying (with the default, incomplete dictionary):

ts.'ong55_!_|

What compiler and settings are you using on Windows?

@michaelDCurran?

The crash no longer exists in eSpeak NG master, probably through some msc /analyze fixes. Therefore this will be fixed once #5651 is merged.

#5651 is now merged. Closing.