[FIXED] Speak tags for card and screen displayJune 7, 2019 at 12:20am (Edited 3 months ago by @felix-voicehub)
Another place where having <speak> tags will be problematic is for non-speech text that is returned from a skill. On Alexa, I'm specifically thinking of the help card title/text and any text which is shown via the Display directive. I think a field type of plaintext would help in these cases.
June 7, 2019 at 7:42am
July 3, 2019 at 1:46pm
Thanks - this looks like a good start for basic card responses. There are more complex multi-model interactions that I'd want to be able to do, such as interfacing with the Dialog.Display directive. Those may require either creating a large variety of options (e.g. an APL-style tool), or providing ways to get to the raw content and building it within the code.