Hi @Laurent_Knimer , thanks for providing a potential solution to your problem. I believe though that the issue you face is possibly caused by the confusing nature of the use of regex escaping ie \\ within String Manipulation. Whilst double-escaping works in the search portion of the regexReplace, in the replace portion you need to use triple-escaping. Weird I know but go with it 
Take a look at the following workflow as an example, and see if this assists you:
In the Table Creator, I create a string that I shall convert using String Manipulation so that it becomes a multi-line string. The original string is:
The Quick¬Brown Fox¬Jumps Over¬The Lazy Dog
In the first String Manipulation, I replace the “¬” character with a linefeed, using regexReplace:
regexReplace($column1$,"¬","\\\n")
so the "¬" is replaced with "\\\n", which I use the three-backslash syntax instead of two-backslash. If I had only used two backslashes, it would have replaced the original string as follows:
The QuicknBrown FoxnJumps OvernThe Lazy Dog
But with a triple escape, it correctly includes the linefeed.
This situation is further evidenced by my second String Manipulation where I then wish to add some additional linefeeds and underscores after the “Brown Fox” line:
regexReplace($first replacement$,"(\\nBrown Fox)","$1\\\n_____\\\n_____\\\n")
As you can see, it will happily accept \\n within the search portion, as you had noted, but in the replace portion, we have to use \\\n to indicate that linefeeds are to be inserted.
This does feel an odd inconsistency and is presumably to do with the levels of interpretation of the different parts of the regexReplace statement within the internals of the String Manipulation node when both interpreting the statement, and also when converting it to java. I guess it is just one of those niggling things that you need to discover and hopefully remember!
Interestingly, you can (at least in this case) opt to use three backslashes within both parts of the statement and it still works,
i.e.
regexReplace($first replacement$,"(\\\nBrown Fox)","$1\\\n_____\\\n_____\\\n")
Here is the above sample workflow that may be of interest:
Escaped linefeeds in String Manipulation regexReplace.knwf (2.2 KB)
I hope that provides some “simpler” (albeit “weird”) solutions to your problem 