After all it's almost only a "want-to type-less" feature.
Personally, I think it's not even "almost", that's exactly what it is.
I have mixed feelings about that feature. There are things I like about it and things I don't like.
I like the clean, uncluttered look of the multiline string.
I am not fond of the need to have a new token in the language (presumably "(#") and, I like even less the need to have directives to control the trimming of the strings. Most, if not all the savings in typing, go out the window with those directives.
Here is a thought, it's a small variation on the concept Akira has presented, using current Pascal syntax:
const
s = 'hello ' +
'world' ; // would print "hello world" (just as it does now.)
{$LINEBREAKS ON}
b = 'hello' +
'world' ;
// would print (imagine "// " is the beginning of the line)
// hello
// world
{$LINEBREAKS would be active ONLY for 1 string, the very next one, to prevent having unintended line breaks in other strings. I think this is a feature that is used rarely enough that having to type {$LINEBREAKS ON} for each one of them is within reason.
Basically, teach a new "trick" to the "+" pony.
That method would make "xxxTRIM" directives unnecessary since the programmer would still be responsible to put whatever number of spaces he/she desires within the quotes. It also gives the programmer very precise control, which may be needed/wanted when the purpose is to have fixed-length strings on separate lines.
Those are my two (2) counterfeit cents on the subject.