Closed henryjc closed 2 years ago
@henryjc You are correct on both counts!
<break>
element is unary, so the examples should be constructed as shown in the SSML specification.I will close this issue when both of the changes have been updated in the documentation. Thank you for taking the time to report the excellent comments, and I apologize for the errors!
@henryrc The documentation will be fully updated next week. I am unable to publish the fixes before then. Thank you again!
@jeffpk62 Good to hear, no rush I was just curious. Cheers
This is published and live. Thank you!
I am following an example from the documentation page, linked and screenshot below regarding the \<break> element. It seems like the text enclosed in the \<break> tags are not outputted properly (at all). I suspect this may have something to do with differences between SSML version 1.0 and 1.1? Or is this a peculiarity with IBM's treatment of SSML?
I noticed here (https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-ssml) and elsewhere, that the page states that the TTS is based off of version 1.0, but then it links to a page for 1.1 (https://www.w3.org/TR/speech-synthesis/) - "The Text to Speech service bases its support on SSML Version 1.0, which was recommended by W3C on September 7, 2004. For more information about the W3C SSML recommendation, see W3C Speech Synthesis Markup Language (SSML) Version 1.0."
Code I used to test; the output doesn't synthesize the text in between the break tags, yet there are breaks of the right length:
Removing the second \</break> results in a mismatched tag error, however other SSML documentation (amazon, W3C, google) shows that the \<break> element does not enclose anything, but rather can be used independently. Ex.
Am I missing something here?
Link to problemed documentation page: https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-elements#break_element