New Topic

Locus Map - help desk Topic Problem Locus Map (Android)

This object is in archive!

Category Locus Map (Android)

Tags Navigation, Language

Comments 16

Subscribers 4

Votes 1

Navigation point and language

Jürgen Holm shared this problem ago

Solved

Hi.

With the route function all my automatically generated navigation points are in english (e.g. "sharp left") no matter what language is configured (I tried: System default, Deutsch, Dansk) . Is there trick I did'nt know?

The same problem 0

Replies (10)

Michal Stupka ●

Hi Jürgen,

language settings in settings > language&units > language affect language of the app texts, not of navigation commands. Go to settings > language&units > Text to speech settings instead.

URL

Jürgen Holm ●

Hi Michal,

my problem is, that the text of the navigation points (right of the icon) are in englisch and not in German.

My TTS settings are all German.

URL

Michal Stupka ●

Hi Jürgen,

so your phone system is German, TTS German, Locus is in German and the navigation commands are English... interesting. J´Have your tried to restart the phone?

URL

Jürgen Holm ●

Hi Michal,

shure. This effect is on my S5 (6.01), my new Tab S2 (7.0) an my old 2014 Tab now on LOS 14.1.

URL

Menion ●

Good day Jürgen,

may you please write me some additional information?

- what routing service are you using?

- what is selected language for your navigation in Locus > settings > navigation > select voice? Do you have here selected "Text-to-speech" option?

- may you post us here a screenshot of menu > settings > language & units > text-to-speech settings?

Thank you!

URL

Jürgen Holm ●

Hi,

I'm using brouter

7a2f2238e3bf328305c60a697873ffde

4f33e47c21314acdcb58160a72466205

cd504814dd3a55073180e8e00f77daa3

URL

Menion ●

Hello, thanks for a screenshot.

Oki, in this case, I see only possible reason for this behavior.

It is possible to setup custom text notification commands over text file placed into Locus/data/tts . In this case, you will need an Locus/data/tts/de.tts file. Content of this file will be used for german translation of notification commands. Is it possible that you just renamed some English sample file from en.tts to de.tts? Check this directory please. If this file exists, simply delete it, it should help.

Let me know,

Menion

URL

0709 ●

Menion,

I think message is not about wrong spoken language TTS audio commands !

As the English <sym>translated by (de.tts) to the German TTS language probably is well and ok. It is about the text that is displayed in the map, when auto-generated by the Locus planner. Jürgen expects the German translation to be shown visualy in <name> too.

Example [NL] <name> (created by a manual edit)

d339a2ef8f908c984f915524e7255a2e

URL

Jürgen Holm ●

Exactly!

URL

Menion ●

Hmm, thanks Willy (0709) for a comment. In case of automatically generated navigation points, same system as for voice TTS is used. So names are really generated by same background engine. I just tried it on own device ... by default, I use Locus Map completely in English. I then simply in Text-to-speech settings in Locus, changed to what you may see on screen01. After that, starting navigation on track without commands and letting Locus generate these commands, I get this itinerary result (screen02).

So you may see ... all texts in app are still in English, but because TTS was changed to German, names of points as well as spoke instructions, are now in German.

644ee32e807caaba91dcff5720630fdf

564815f723c48733dfeb2783893a9650

Quite interesting. It looks I'll have to create for you a special version that will print us some information into log file.

URL

0709 ●

Just another comment:

After that, starting navigation on track without commands and letting Locus generate these commands, I get this itinerary result (screen02).

I think it is not about "let Locus generate commands on a navigation track without commands" . It's about the generation of commands by the Locus_Brouter planner resulting in a track inclusive the commands.

URL

Jürgen Holm ●

Hi Menion,

spoken language was always german, so this is ok. But interesting: I took a look into data/tts and found:

ce538e4263b25171ee0e917736767777

After deleting all files an configure TTS to german, en_sample_v4.tts was downloaded by Locus an Locus speaks in german. Strange.

URL

0709 ●

Hi Jürgen.

The used TTS language in Locus is by the standard internal language set.

The [DE] language instructions are suggested by the German community forum group.

The en_sample_v4.tts is an example template file to be customized into "en.tts" or "de.tts" etc.

So you are able to create your personalised "de.tts" file by changed or compact commands.

Example: By the DE community for the "right" command you notice: "biege rechts ab"

If you prefer compact TTS messages change this into: "rechts"

A critical operation because any syntax error makes your customised file unusable.

Anyway there is always a fall back to the original internal file if such happens.

Info here: http://docs.locusmap.eu/doku.php?id=manual:advanced:customization:tts

Tip: Ask in [DE] language forum if someone wants to share you a recent (compact) "de.tts" (v6) version.

URL

Jürgen Holm ●

Hi Willy (0709),

I never had a problem with TTS. In the past I added nagigation point manually with the good old track editor and all was fine. This is impossible with the new track editor and a pain with the new router interface. So, I created navigation automaticlly. But: language is wrong (only with brouter!).

Changing the TTS file has no effect on text of the naviagtion points

URL

Jürgen Holm ●

Another observation:

if using: "Grashopper" or "Yours" for routing the text of the navigation points are in german in contrast to brouter.

brouter version is 1.4.9

URL

Menion ●

I think I probably have source of problems. Seems that BRouter already generate names for waypoints, so what you see are not texts generated by Locus Map, but directly by BRouter. In you case, I expect, your device is in English? If so, then BRouter itself also use English and visible names are not affected by any Locus Map settings.

Since next version, Locus will generate names for these navigation points manually also for a BRouter results, so they will be in correct language. Thanks for bug-report and discussion.

URL