Converting strings with line feeds to a single line with identifying chars

Question

Hi, I dont want to re invent the wheel if there is something out there that does this already. I want to take some string with multiple
line feeds and convert it to a single line. For example:
"I want this string
to be changed to
a single line"
to this...
"I want this string\r\n to be changed tor\\n a single line"

Answer 1

vsekvsek wrote:
OK, Hope this will make better sense. So right now a I have a routine that loads files like below:
"TEST\r\n TEST1\R\n TEST2"It's not clear to me at this point what you mean by that string.
After the initial word TEST, does that string have a backslash character followed by an r followed by another backslash followed by an n? Or does it have a carriage return followed by a line feed. (\r followed by \n)
We format it when loading in a way that it will look like this when queriing from the DB
"TEST
TEST1
TEST2"It doesn't look like anything "when querying from the DB." That part doesn't make any sense.
Either the string has a backslash followed by an r, in which case when you render in in a text editor or on a console it will look like a single line with a visible backslash character followed by an r, or it has a carriage return (\r) in which case it will look like multiple lines when rendered in a text editor or on a console.
Later I re-extract it to a file from the DB and What confuses me is when I inspect the string it looks like this
"TEST\r\n TEST1\R\n TEST2"How are you inspecting it? If it's in a debugger or similar tool, it's not uncommon for it to be showing a carriage return character (\r) as a visible backslash followed by an r, rather than interpreting it and rendering a new line. This is so that you can see exactly what characters are in there, rather than wondering about the specific whitespace.
>
but it extracts to my file like
"TEST
TEST1
TEST2"
So I guess there are some hidden cr's or something messing it up that I need to manipulate but not sure how to apprach it?I still don't know what you're trying to do, or if you even have an actual problem with your data or are simply not understanding what you're seeing.