TTS Nextgen discussion

**nanocosm** · 24th September 2015, 09:49 AM

Originally Posted by Mike Hunt

In addition to the ttspro.zip suggestion, check your installed Android system TTS engine..perhaps it is not compatible. I have found good old free Google TTS to be trouble free.

Certainly did not mean to imply that you did not know what you were doing (and glad that you do), I just can never guess what knowledge or skills someone has and always err on the side of caution.

Great. Please do (especially with it proven working). In fact, the whole voice file would be good to benefit others who may be looking for one.

Ok, translation done.

Below is the whole translated "dictionary.voice" in to German (GER)

Code:

Please Login or Register to see the links

The file below is the German (GER) TTS Voicefile to be placed into "./content/voice/" folder. It includes the "dictionary.voice" from above.
Temporary removed due to a bug

Place the current version of the file "tts-speedcam-eng.zip" into iGONext "ux" folder.
Note to all users even thinking about it: The "-eng-" in the filename is ok.
It's a translation-table from "eng" to every TTS file and should therefore NOT be translated itself or even renamed. Just place it in the "ux" folder.
[Only registered and activated users can see links. ]

By the way, I totally agree with BrownDog. All this TTS Stuff should be placed into a separate thread very soon!

**Mike Hunt** · 24th September 2015, 10:03 AM

Originally Posted by nanocosm

Ok, translation done.

Excellent work. Thank you.
The only 'mistake' I could find was a line in dictionary.voice (noticed while copy/pasting) that should be:
Limit% s="Limit% s"
My mistake for not making it clear that any word attached to a "%", regardless of it's position, should be left alone.
Not sure of the impact this may have...if any. That line could be leftover from an old WinCE installation and not affect NextGen at all.

And PS...I also agree with BD. It seems that people have more questions about TTS than almost any other single thing. If every TTS post in this thread could be plucked out and dumped into a new dedicated thread it would accomplish two things:
1) Clean up this thread and return it to a more general NextGen topic
2) Make it easier for people seeking TTS answers by not having to slog through 400 posts to try to find a TTS post (and maybe prevent having to ask something that has already been answered if they don't read them all).

**nanocosm** · 24th September 2015, 11:32 AM

Originally Posted by Mike Hunt

....

Warning Method="Warning Method"
Preliminary="Preliminary"
Only for active signs="Only for active signs"
You can increase speed.="You can go faster now. Up to,"
Limit% s="% s"
After %s = "After %s"
Possible alternative route = "possible alternative route"
more shortly on %s = "shorter on %s"
more long on %s = "longer on %s"
Tunnel length %s = "The length of the tunnel is %s"
After %s = "After %s"
Environmental Zone = "Eco-Zone"
Remaining %s = "left %s"
Remaining more than %s = "left more than %s"
;;------------------- Speedcams IGO_NextGen --------------
Warning! Speedcam.="Warning! Speed camera ahead."
Warning! Possible mobile speed camera.="Warning! Possible mobile speed camera ahead."

Originally Posted by Mike Hunt

Excellent work. Thank you.
The only 'mistake' I could find was a line in dictionary.voice (noticed while copy/pasting) that should be:
Limit% s="Limit% s"
My mistake for not making it clear that any word attached to a "%", regardless of it's position, should be left alone.
Not sure of the impact this may have...if any. That line could be leftover from an old WinCE installation and not affect NextGen at all.

Yes, I also noticed that "wired" line.
Code:

Please Login or Register to see the links

It's from your post above.
The question is: Which is the right one? Both are included.

Code:

Please Login or Register to see the links

I'd say

Code:

Please Login or Register to see the links

makes more sense at all. The other one is probably a left over copy'n' past typo.

**Mike Hunt** · 24th September 2015, 12:46 PM

Originally Posted by nanocosm

I'd say

Code:

Please Login or Register to see the links

makes more sense at all. The other one is probably a left over copy'n' past typo.

I think you are absolutely correct. I believe it's left over from an edit with a diMka skin for WinCE and possibly duplicated incorrectly.
I think originally it was two lines:

You can increase speed.="You can go faster now. Up to,"
Limit %s="Limit %s"

One triggered the other within the skin modifications. Somehow this combination also made the cut into an apparently common UX file because it still works.
But much of the diMka add-on settings were translated (badly?) by somebody into English and posted on various sites, so a bad spacing would not be impossible, and I have been copying/pasting ever since. I checked my own personal voice file (which is slightly different based on what I want vocalized which may not be family friendly), sorted it alphabetically and both were there. I removed the bad spacing one and left Limit %s="Limit %s" and everything still works as expected.

**nanocosm** · 24th September 2015, 01:31 PM

Originally Posted by nanocosm

Ok, translation done.

Below is the whole translated "dictionary.voice" in to German (GER)

Code:

Please Login or Register to see the links

Sh***! Seems that there is a type, forgotten double-quote, special char ect in my dictionary.voice. NextrGen crashes right after the spinner...

Could not find the typo right now.

Any idea how to find the typo? Logcat does not help here.
Logcat only shows one relevant line:

Code:

Please Login or Register to see the links

Ironically it even crashed pass a completely empty dictionary.voice
So it seems that there is something important missing.

Well I will re-check it line by line but will take some time...

**Mike Hunt** · 24th September 2015, 02:33 PM

Originally Posted by nanocosm

Sh***! Seems that there is a type,

It's not your syntax...your zip compression apparently got corrupted as far as iGo was concerned (wrong version of WinRar?)
I fixed it using your translations into another original copy of the voice file (yours is not recoverable..might as well delete it), so this combination works for me on Android 4.44 with Google TTS.

[Only registered and activated users can see links. ]

**AureliusMax** · 24th September 2015, 04:36 PM

Hi Mike Hunt,

Wow...that took me sometime. Never realized that translating business isn't as straightforward as it looks. But here goes: my Dutch language speedcam translation:

Spoiler: Dutch Language Speedcam

And attached the TTS Voice that works for me with Google TTS, Nextgen on a Samsung Galaxy S6:

[Only registered and activated users can see links. ]

Would be very much obliged if you would turn it into a tts-speedcam file! Thanks!

P.s. Does having a tts-speedcam file mean that I can leave out the

Spoiler: speedcam setting

etc in my sys.txt file?

**Mike Hunt** · 24th September 2015, 05:21 PM

Originally Posted by AureliusMax

Wow...that took me sometime. Never realized that translating business isn't as straightforward as it looks. But here goes: my Dutch language speedcam translation:

P.s. Does having a tts-speedcam file mean that I can leave out the
; S P E E D C A M - C A T : 1
etc in my sys.txt file?

Yeah, translating is not fun. I tried it ONCE with the whole file using Google Translate, and that was enough times for me.
Anyway, here you go..you know what to do with the files:
[Only registered and activated users can see links. ]

This voice file does not work for me (possibly Loquendo-based?), so I could not test it myself. Hope it works for you.
I checked by inserting your translations into a Dutch Voice (Zander) that does work for me, and all the available TTS and speedcam alerts worked.
Basically, yes. All or most of that is in the *speedcam*.zip UX file, so there is no point in cluttering up your sys.txt with it UNLESS you want to over-ride a default setting with your own..but if the systax does not match the UX file, it would not do anything anyway.

**boblejeune** · 4th October 2015, 08:27 AM

Do you have the complete sys.txt as the TTS button in options does not light up so guess something is missing in SYS.txt file.
will yout sys.txt it work for DUT TTS as well (flemisch)
Grtz

**Mike Hunt** · 4th October 2015, 09:41 AM

Originally Posted by boblejeune

Do you have the complete sys.txt as the TTS button in options does not light up so guess something is missing in SYS.txt file.
will yout sys.txt it work for DUT TTS as well (flemisch)

There is nothing in sys.txt that 'activates' TTS. It depends on the proper files (voice and UX modules) being in place and a proper TTS engine installed in Android for the options to be usable in Settings.
But, if you are curious, below is my sys.txt. It will not solve your problem.

Spoiler: Sys.txt