Fix line breaks ruining call tag regexp

[kirsle]

Per issue #108, if you used a line break sequence "\n" inside a <call> tag, it would break the regular expression trying to match the <call>...</call> sequence because this regexp couldn't handle line breaks.

JavaScript regexp doesn't support the /.../s flag which would make the . metacharacter match line break characters. The workaround is to replace the . metacharacter with the sequence [\s\S] to match spaces and non-space characters (essentially forcing it to match everything, including line breaks).

- callRe = /<call>(.+?)<\/call>/ig
+ callRe = /<call>([\s\S]+?)<\/call>/ig

Additionally, I changed the code to call the new utils.trim() function (which is a more compatible version of String.prototype.trim() to support Internet Explorer < 9) instead of the utils.strip() function -- because that function would remove line breaks anywhere in a string, negating the whole point of allowing "\n" to appear inside a <call> tag.

This code fixes #108.

[davidchriqui]

Thanks for the reactivity.

However, your fix causes "string1\nstring1" to be troncated to "string1"

[kirsle]

Can you give me an example? When I tested it with your example from #108 it worked for me.

[davidchriqui]

My bad. It does work. Thank you ;)