No it's more in keeping it "correct" in terms of tokens, as your replace combines them all into one garbled string, sure you could do it that way but you'd have to include $chr(32) in your regex substitution to space them out, and possibly $mid(,1,-1) to remove the trailing space at the end (if more regexes done on it which could throw off matches not accounting for the extra space at the end, token identifiers wouldn't care...)