Conversion between legacy error and encoded error strange behavior?

[bienieck]

I try to convert an error cluster using the new Convert to Encoded Error Cluster.vi and Convert to Legacy Error Cluster.vi. However, this simple workflow mess up the error message (see image). I wanted to include attributes to the error, access them in an error handler, and display a simple error message in the end.

Am I doing something wrong? Or the workflow I have was ignored by this tool designer?

EDIT: Actually, I see that \n and \r are not properly converted back to whitespace ☹️ Should I request a correction?

[altenbach]

I am not familiar with these tools. Can you attach an actual sample VI so we don't need to guess from a picture.

---

@bienieck wrote:

EDIT: Actually, I see that \n and \r are not properly converted back to whitespace ☹️ Should I request a correction?

---

They should again be interpreted as linefeeds (not whitespace) to match the first picture. Instead they seem to be displayed as \-codes.

[bienieck]

Example in the attachment.