[text to speech] Special Character failure resolution

[blakesteve]

Related to #635

Reverts the encoding so TTS won't read "+" when returning a space.

[josepmao]

@blakesteve @germanattanasio
I do not think just remove String encodedText = RequestUtils.encode(text); can be a proper change here. It will cause problem in #602 come back again. I suppose you add the RequestUtils.encode(text) to avoid that, and even in the workaround from #602, it give extra with .replace("+", "%20") after called URLEncoder.encode() to avoid the problem reported in #635 , although looks it is not a proper fix.

should we consider change to use POST? If keep using GET, agree with #635 at least need to modifying RequestBuilder to escape semicolons properly

[blakesteve]

@josepmao with commit 19948d5 the semicolon gets properly encoded before sent to the server, and testing against the string you provided in #602 it resolves the issue, unless I'm mistaken?

[germanattanasio]

LGTM

[josepmao]

@blakesteve thanks for the response. Get it now :-)