You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
👍 Good catch; in the playground site the "\n" is translated to a literal line feed, but for an HTML output display, this has little tangible effect on the rendered output. For an HTML output the calling code should replace "\n" with "<br>" which it seems the Try Online page does but the playground doesn't.
I'm not sure it's a RiveScript bug though and not a bot implementation bug. For example, in the classic instant messenger bot days (with AOL, MSN, and Yahoo), a \n in a message shows as a line feed in MSN and Yahoo but under AOL, which had HTML-based messages, the \n would need to be deliberately replaced by a <br> tag in order to come out correctly there as well. Definitely the Playground site should handle this, though, since it has an HTML display for the output!
It looks like the \\ and \/ escape codes aren't handled by the JS, Python, or Go versions of RiveScript though which could be considered a bug in their implementations if the Working Draft said these should work.
Hi Noah,
I tried the special character tests in the playground and it seems the following special chars are not supported at least in the output.
\n (works on https://www.rivescript.com/try)
\/
The text was updated successfully, but these errors were encountered: