Messages

Thanks for the fix.
I've updated ja.tts for improvement. This should be the final for next Locus release. Please fetch it. (sorry for many time.)

I've confirmed that the warning message "incorrectly initialized action %N1" still appears in 3.7.1.6 and in this case the voice system of Locus falls back to crowdin text base. I'm sure that empty "numbers_N1" in tts file cause the issue and it's possible to reproduce it by using attached en.tts.

Now, I would like to ask again whether empty "numbers_N1" is a valid format or not. If valid, please fix the issue to properly load tts file. (for both tts file integrated in Locus and placed at data/tts folder.) If invalid, I'll re-modify ja.tts at google drive with non-empty "numbers_N1".

Thank you for quick answer and decision as always!

And, please fix empty "numbers_N1" issue (post #89) as well.

EDIT:
updated ja.tts

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=0

Main 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.n2tts
If it's not successful, you may try apk downloader.

@ta-ka, problem with comma should be a problem. It's weird that TTS reads it, weird. Google TTS or Czech Ivona TTS reads it correctly - just as a small break. Hmm ...

Is the adding 'comma' hard coded in the program source? If so, how about to take it out to ??.tts/crowdin text as a parameter.

Code Select Expand

"short_pause": ","
"short_pause" can be 'comma' or 'white space' or any other appropriate character depending on Language and TTS engine.

Btw, reading balloni and your post, I confirmed Japanese Google TTS doesn't speak comma, too.  However KDDI N2TTS speaks comma...

About Training, I've noticed that Locus pronounces annoying 'comma' between variables if Japanese voice is selected. Could you please improve this?

The warning popup message reported in post #89 still appears in version 3.7.1.4.
Haven't it fixed yet?  Or, is there anything wrong in ja.tts at google drive?
Could you please have a check?

@menion thanks for the fix of 0 minutes issue.

updated ja.tts : "numbers_N1" is empty now.
fixed en.tts : 's' after mile was missing at "%N1 mile per hour, 2, Inf"

EDIT:
crowdin done. (except Locus GIS, sorry for that)

@ta-ka: are you really interested in seconds when you are in time, more then hour since start? Because here it is not an issue, but intent.

I somehow foresee that this is an intent. My case is middle-range running more than one hour and I want to know time with seconds at every 1.0 km even after 10 km or so. The explanation in my previous post was so bad. sorry.

In any case, please note that no voice at every '0 minutes' is the issue as same as already fixed '0 seconds' issue.

I tested ja.tts with empty "numbers_N1" as shown the first code in post #86, and got an error message below just after locus start to speak something. There was no force close. Locus kept working but voices of Navigation/Guidance/Training were complicated mixture of Japanese and English.

[@balloni55]

@balloni55: heh, Locus had problems with times where was '0 seconds' . Fixed, thanks.

'0 minutes' not fixed. 

After one hours passed, locus talks only hours and minutes. I think there should be seconds, too.
Currently, if time interval is set to 30 sec, Locus talks the same "X hours Y minutes" twice at 0 sec and 30 sec.

In case of popular freely available Japanese TTS system in android like Google TTS or KDDI N2TTS, passing numbers as digits to the TTS system gives satisfiable results for cardinal numbers, as the TTS system takes care of different pronunciations. Only ordinal numbers have to be replaced in Locus. So, I'm going to test and update ja.tts.

It is useful for languages like Czech, where exists many various of word "one" - jeden, jedna, jedno, etc.

Knowing about other language is always interesting.

If there is no need to replace the digits in "numbers_N1", is it allowed to make it empty?

Code Select Expand

},
"numbers_N1": { },
"numbers_N2": {
Or, is it allowed to completely remove it?

Code Select Expand

},
"numbers_N2": {

In ja.tts, "numbers_N1" doesn't contain the words to replace but only digits like follows.

Code Select Expand

"numbers_N1": {
      "1": "1",
      "2": "2",
      "3": "3",

[@ta-ka]

@ta-ka: hmm thanks, very helpful. I found an older code from times, when TTS file wasn't so useful as now. I've improved whole system and now it should work as expected.

I confirmed that "Next waypoint" notification come from tts file now in 3.7.2.3.
However there are issues remained. (confirmed with guidance.gpx attached again below)
- Locus says "after 300m turn around" before the end point "DEST".
- Locus doesn't say about approching to the destination.

And, One request please.  I would like to translate "DEST".

don't see "built the project" on crowdin

hehe
version without translation

[@ta-ka]

@ta-ka: hmm thanks, very helpful. I found an older code from times, when TTS file wasn't so useful as now. I've improved whole system and now it should work as expected.

Good

4 votes in case of such simple task, was enough for me. I had no idea, that there may be anyone who was aware of sorting in old system. Is it a bigger usability problem or you may live with it?

I can live with that. Don't worry.