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
It is the case that when < or > exist a s variables or values, this same exception is thrown. It is probably the case that a general XML check is performed on all variables and this exception thrown when < or > is found, even in this less common case for if statements.
The text was updated successfully, but these errors were encountered:
Yes, you should indeed use "<" (lower than) and ">" (greater than) instead of < and > in order to get valid XML. I'll change the documentation to reflect this, thanks for noticing the error.
It is the case that when < or > exist a s variables or values, this same exception is thrown. It is probably the case that a general XML check is performed on all variables and this exception thrown when < or > is found, even in this less common case for if statements.
—
Reply to this email directly or view it on GitHub.
Pierre Lison (Postdoctoral Research Fellow)
Department of Informatics, University of Oslo
Mobile: +47.967.998.12
Web: http://folk.uio.no/plison
The above error is thrown when I load a custom domain.xml file with the following if statements within a rule:
But according to http://www.opendial-toolkit.net/user-manual/dialogue-domains, the "<" and ">" characters should be usable as relations.
It is the case that when < or > exist a s variables or values, this same exception is thrown. It is probably the case that a general XML check is performed on all variables and this exception thrown when < or > is found, even in this less common case for if statements.
The text was updated successfully, but these errors were encountered: