Project

General

Profile

Actions

Bug #4548

closed

string tokens with newlines print the escape sequences

Added by Oliver Soong about 15 years ago. Updated almost 14 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
reporting
Target version:
Start date:
11/13/2009
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
4548

Description

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.

Actions

Also available in: Atom PDF