Thanks again for testing with my string, Dan.
That sounds plausible, your split criterion is a space ” “.
But what if you do the split with “/r” for “carriage return”?
There should not be any carriage return in my test string yet.
Imagine a user inserting my test string into a paragraph text and then reformatting it by hitting the carriage return key any number of times.
In this case the expected number of lines (strings) generated is not what you would expect because my test string contains special characters messing up something about the line count, I guess.
I am looking for a workaround regarding special characters messing up the number of custom “carriage returns” when splitting is done with “/r”.
Since a user hits carriage return any number of times, the resulting number of lines should match his hits and thus be correct in the end.