Integrating Opentts into a android tts engine.

[LuekWasHere]

Hello!
I thought i'd attempt to raise this issue here, as it seems fit. Be aware im quite new to working with or understanding source code.
I have been trying to integrate the opentts api into a open source android system-wide tts (tts-server-android). It was going well except there seems to be a conflict with the opentts api when trying to do a http request to it.

The application allows for custom http requests, in this format:

"The format is the same as the Legado APP network TTS engine：
http://url, {"method":"POST", "body": "POST body. support using {{js code or variable}} "}

Built-in variables：

• Text：{{speakText}}
• Speed：{{speakSpeed}}
• Volume：{{speakVolume}}

Baidu Example：
http://tsn.baidu.com/text2audio,{"method": "POST", "body": "tex={{encodeURI(speakText)}}&spd={{speakSpeed}}&per=4114&cuid=baidu_speech_demo&idx=1&cod=2&lan=zh&ctp=1&pdt=220&vol={{speakVolume}}&aue=6&pit=5&res_tag=audio"} "

I tried to make a custom http request to the opentts server running in docker.
Using this url:
http://192.168.0.226:5500/api/tts?voice=larynx%3Acmu_aew-glow_tts&text={{java.encodeURI(speakText)}}&vocoder=low&denoiserStrength=0&cache=true

Some raw inputs work and others seem to conflict with the syntax.

This does not work:

from an intelligence explosion (Good 1965): a process in which software based intelligent minds enter a runaway reaction of self improvement cycles, with each new and more intelligent generation appearing faster than its predecessor

log output:

Failed: (1) cc.l: Expected start of the object '{', but had 'EOF' instead at path: $ JSON input: %20with%20each%20new%20and%20more%20intelligent%20generation%20appearing%20faster%20than%20its%20predecessor.&vocoder=low&denoiserStrength=0&cache=true

This does work:

Part I of this volume is dedicated to essays which argue that progress in artificial intelligence and machine learning may indeed increase machine intelligence beyond that of any human being.

I'm curious to see what you think (or if you notice a issue I cant seem to detect.), as I strongly believe if I can get this reliably integrated into this application, I will have a functioning and incredibly good quality tts, that might encourage further development. So far the text that does get parsed is incredble.

Additionally here is a link to a issue raised by myself to the developer of the android application aswell. It has more detail on the information specific to the application itself.