string tokens with newlines print the escape sequences
This was first noticed when viewing an RExpression's "output" port. The output port emits a string token containing a section of the RExpression's stdout stream, with newlines encoded in the relevant OS's format. The report will then display literal "\n" or "\r\n" in the report, rather than the appropriate newlines.
While much of reporting ignores newlines (text boxes, for example), it might be useful to respect them here, since the RExpression output is less useful without them.