| Commas are missing from semantic interpretations that are printed to the log |
| Categories: Audium Call Services 3.4.x and 3.5 |
| Article ID: | 33 |
| Last updated: | November 02, 2006 |
| User Opinions |
|
No users have voted.
|
|
Thank you for rating this answer.
|
SUMMARY
When a custom Audium log entry is made that prints out the value of a variable holding the interpretation of a grammar (usually for debug purposes), commas that are expected to appear are not present.
SYMPTOMS
In Audium Builder for Studio, an element was configured to produce a custom log entry that included the interpretation of a user utterance (e.g. a Form's nbestinterpretation1 variable from element data). However, when the Audium log is examined, the commas that are expected to appear in this interpretation are missing.
RESOLUTION
The Audium log strips commas from text that it outputs, since the comma character is reserved as a delimiter. However, this does not change the value stored in the variable, and so the commas will be present as expected when the variable is accessed by your application and custom code.
Note that commas are stripped from all values that are outputted to the log, not just semantic interpretations.
|
| Visitor Comments |
|
No visitor comments posted. Post a comment
|
| Attachments |
|
No attachments were found.
|
Search the Knowledgebase
Jump to ID
Browse by Category
Print this page
Post a comment