Started by Menion, July 07, 2013, 14:44:19
0 Members and 1 Guest are viewing this topic.
Quote from: "gynta"Quote from: "ta-ka"..."You've arrived at your destination". Try attached the gpx file.Ah i see. It is also a calculation "problem". Distance from the last instruction and speed. Isn't it?
Quote from: "ta-ka"..."You've arrived at your destination". Try attached the gpx file.
Quote from: "menion"EDIT: ah ta-ka, sorry I forget to check your last post ... so hope tomorrow
Quote from: "ta-ka"@menionPlease fix typos in en.tts.Text-to-speed -> Text-to-speechnineth -> ninth
Quote from: "menion"If you'll miss any notifications, tell me, I'll improve it
Quote from: "menion""better text fro clock/distance instructions" - you mean for a guiding? I'll improve support for text configuration TTS file to cover also commands for this guiding. Next week ...
Quote from: "menion"Btw. what order should be more usable then this?
Quote from: "ta-ka"I have an another problem of the unofficial Google route calculation and TTS voice navigation of Japanese roads.Japan is a left-hand traffic country. But the Google route calculation in Locus wrongly shows right-hand traffic route. Therefore the TTS voice navigate to the opposite direction.Well, it's an unofficial function but could you please fix this?
Quote from: "tommi"Another question (I admit it's a bit off-topic but has to do with TTS).There are navigation instructions "after 50m turn right" and later "after 100m turn left" " and sometimes its "after 50m turn right then after 100m turn left". What is the exact condition that Locus concatenates the two instructions?Or is this info coming from the online routing service?
Quote from: "menion"ah yes , sorry. These instructions are generated by myself. If there is distance up to 300 metres, between orders, locus say both, otherwise just current. And both are also said only in case, you're closer then 200 to first command