CRLF # value in text edit UI control

[Former Member]

Hi,

We have an existing web dynpro application that saves long strings and the formatting via a text edit UI control.

Since a recent support pack upgrade we are now seeing that CRLF i.e ENTER on the keyboard is being saaved as a # value.

So.....

This

is

my change

becomes

This#is#my#change

The textedit UI element is bound to a string data type.

Anyone got any ideas??

Thanks D

[alex_campbell]

This might have something to do with Unix-systems using just LF as a newline (ENTER) vs Windows-systems using CRLF as a newline. I often notice the same thing (hashes instead of newlines) when a file is read from our App server (Unix - LF) but the program is expecting a file from the Presentation Server (Windows - CRLF).

Have you debugged through your program to determine whether the data bieng put to/pulled from the TextEdit UI Element is using LF vs CRLF?