-
Notifications
You must be signed in to change notification settings - Fork 3
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
Support for the <mark> element? #4
Comments
j'ai vraiment besoin d'utiliser mark. comment je peux faire. merci de me fournir un exemple concret . très important merçi |
According to the specification https://www.w3.org/TR/2010/REC-speech-synthesis11-20100907/#S3.3.2
The element can be placed anywhere in the input SSML. Do you propose that in this case hosting environment is the code in this repository and one or both of the requirements be met by notifying the code, that is the caller of the parser instance?
Can you provide a minimal, complete, verifiable example?
Are you referring to the Web Speech API specification does not provide any means to capture or adjust the raw audio output in "real-time". What is possible is either capturing the audio output using Another alternative is implementing the |
Basic support for <mark>, defined in section "3.3.2 mark Element" of the SSML specification, would call back to a user-supplied function when the is encountered. This might be done by replacing line 287, utterance.onend = resume; , with a callback that would execute the user-supplied function, then call resume. That only works for a mark at the end of an utterance. To support multiple marks at the end, a queue of callbacks would be needed. Likewise, a mark at the beginning of an utterance could be handled with the onstart event.
However, a mark in the middle of an utterance can't work. The utterance would need to be split into multiple utterances and my experience with WebSpeech browser implementations is that they mess up the prosody in this case.
More sophisticated support for <mark> would include the startmark and endmark attributes on the <speech> tag, per section "3.1.1.1 Trimming Attributes" of the SSML specification.
The text was updated successfully, but these errors were encountered: