I post here about the discussion of comma and tts.
I'll try to think and find some general solution.
Hmm as I think about it, I'll try to next version add a dot instead of comma.
I'm afraid but "dot" won't be a general solution. I confirmed it is literally pronounced by N2TTS as shown in a video below.
https://www.dropbox.com/s/a99451wtokegpz0/20150408_tts_comma_period.mp4?dl=0Main reason why TTS file was created, is to be able to define some special texts that will TTS engine read correctly.
Because some TTS engines reads this correctly, some not,
To read, or not to read, that is the question.

Since "," and "." are not punctuations but special symbols in Japanese, it makes a sense that N2TTS pronounce it literally. On the other hand, it is known that "," and "." are punctuations in a lot of languages in the world. So, it also makes a sense that Japanese Google TTS doesn't pronounce it but put a pause for convenience. Which is correct? It is difficult to say.
Japanese punctuations are "、" and "。" which correspond "," and "." respectively. When we read Japanese text, we put a short pause at "、" and a longer pause at "。". (We learn it at primary school

) Please note that both Google TTS and KDDI N2TTS put a pause on "、" and "。" and don't pronounce them. It is correct behaviour.
adding "separator" to tts is not something I want.
Then how about to introduce punctuations entry in tts file and put it between variables? (period is for further compatibility.)
"comma": ","
"period": "."
In fact, I usually translate "," to "、" in ja.tts and crowdin.
Think "KDDI N2TTS" only known in asia? Isn't it?
So can't check this TTS-engine.
@gynta Thanks for trying to test even Japanese TTS

. I think it is Japanese language specific TTS. Is it possible to open google play with this url?
https://play.google.com/store/apps/details?id=jp.kddilabs.n2ttsIf it's not successful, you may try apk downloader.