Metadata
- Source
- SJRK-271
- Type
- Improvement
- Priority
- Major
- Status
- Open
- Resolution
- N/A
- Assignee
- N/A
- Reporter
- Gregor Moss
- Created
2019-09-03T14:25:49.071-0400 - Updated
2019-09-03T14:25:49.071-0400 - Versions
- N/A
- Fixed Versions
- N/A
- Component
-
- Storytelling Tool UI
Description
Consider handling grammatically conflicting punctuation in the arrayToString transform function, or extending the transform with another that would detect such cases.
From the discussion for the SJRK-263 pull request:
Example:
- Add a text block with text like "Some Text!"
- Add another text block with text like "more text"
- The output is "Some Text!. more text"; Notice the double punctuation "!.".
I imagine that what happens with that will depend on the synthesizer used. Some might ignore it, others might read it as "dot". If you end up using the contentString for output the text visually, it will look strange and be incorrect. Also what about other languages that have different punctuation? It may be better not to try to add punctuation and just separate based on " "
If we set the delimiter to " " then we won't get the pause between blocks, and the synthesizer may continue reading the next one as if it's all one sentence
- Add a text block with text like "Some text"
- Add another text block with text like "more text"
- the output is "Some text more text", which will be read without pauses and could cause confusion
Also explore the possibility of not storing the contentString in the model at all. Perhaps even just using the Orator component to read through the content in the story instead.