Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - ta-ka

#241
Other features / Re: Offline POI database
July 23, 2013, 14:34:40
I've tested Japan DB and it works fine. Thank you.
I noticed two things.
- accomodation -> accommodation
- icon of grave_yard is 'info mark'?
#242
Other features / Re: Offline POI database
July 23, 2013, 09:04:25
I'm interested in it.
Could you provide POI data for Japan?
Thanks in advance.
#243
Other features / Re: TTS voices
July 23, 2013, 08:47:17
I compared the voice navigation of the google route between version 2.13.1.4 and version 2.13.1.5.

version
2.13.1.4 : (1)take exit right -> (2)stay left -> (3)take exit right
2.13.1.5 : (1)take ramp left -> (2)merge left -> (3)take ramp right

- At the entrance of the JCT (1), the direction is correct now (take ramp left).
- At the middle of the JCT (2), it was correct (stay left), but it becomes wrong (merge left).
- About the end of the JCT(3), there is a difference (exit, ramp) but I don't know which is correct.

Hum...  I think I should prepare another sample for test.
#244
Hi menion.
About the list, there is no easy way to prepare but there is only looong way.

For the translation work, I tried almost every single menus/functions in locus, one by one, as much as I could, then assigned translations taking into account where/when/how the words appears in locus.
It requires real hassle but it makes the quality of translations much higher. As a by-product of the careful work, I've found some words are missing.

Translation into Japanese have some chance to obtain such by-product because of the language dissimilarity to English. It sometimes makes strange meaning on the screen and it is relatively easy to recognize. Of course I had to be careful.
#245
It seems that several texts are still missing at the crowdin.net for translation while they are shown in the last locus release version. Could you please check the consistency of the texts between locus and crowdin.net ?

Here is a list of missing texts which I found so far. Some of those texts were discussed before the release of version 2.13.0 but it wasn't listed in the crowdin.net at that time. So I've been expected to be add at the next release.

  - weather_visibility
  - sensor_orientation
  - tab_basic
  - text_size
  - guiding
  - add_new_point
  - geocache_disabled
  - map_screen
  - map_type_city
  - map_type_nautical
  - locus_world
  - search_wikipedia
  - geocaching_live
#246
Other features / Re: TTS voices
July 22, 2013, 05:42:30
Please find attached a gpx file which contains start point and end point for route calculation test.
The route should go though the junction which I've shown in the screenshot.
Thanks in advance.
#247
I report what I found using test version 2.13.1.14.

- the text at the title bar of the "Map color mode" dialogue is wrong.
- on GPS screen, meaning of the texts (on/off) at the bottom button seems opposite.
- GPS on/off by tapping 2D sky view is very nice.  I think it will be also nice if the same function is available at the 3D sky view and the compass view.
#248
Other features / Re: TTS voices
July 21, 2013, 14:58:17
I've just updated ja.tts file.

@menion
Please fix typos in en.tts.
Text-to-speed -> Text-to-speech
nineth -> ninth

Quote from: "menion"EDIT: ah ta-ka, sorry I forget to check your last post ... so hope tomorrow
I see. Thanks!
#249
Other features / Re: TTS voices
July 19, 2013, 14:50:57
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?
Yes, I agree. It depends but I haven't figured out what exactly condition is...

@menion
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?
#250
Other features / Re: TTS voices
July 18, 2013, 16:38:02
I've heard the voice "You've arrived at your destination".
Try attached the gpx file for navigation test.
With this gpx file, you will also hear that the '%N1' is pronounced literally.

By the way, who fixed my mistake in the en.txt? Thanks.
#251
Other features / Re: TTS voices
July 14, 2013, 21:22:01
Quote from: "ta-ka"1. For "approximately after %N1 kilometers",
'%N1' is not replaced with numbers but is pronounced literally.
Quote from: "menion"1. may confirm, funny issue, I'll fix it
I've got some clue. The key may be decimal number in distance and internal/external .tts file.

When .tts file exists in Locus folder and distance value is decimal number (not integer number)
for example 1.5 km, the problem seems occur.

But when there is no .tts files in Locus folder, ie internal tts file is used, '%N1' is properly replaced and
no problem happen even if distance value is decimal number.
#252
Other features / Re: TTS voices
July 14, 2013, 18:27:16
Quote from: "menion"2. I used this text for "information" voice that confirm, your voice works. Anyway I'll add there some text specially for this case
I think it may be nice if the information voice text also appears as a 'TEST PHRASE' in Text-to-speech settings dialogue. It is currently "Do you like Locus?" which is shared with the Main menu as a section title.

Quote from: "menion"3. imagine Locus things you still ride 72km/h. Distance for voice commands is computed by your speed and because you ride still too fast, last distance should be 200m. Set value to 10.0 and you'll hear difference
Oh. I see. I didn't notice that the voice depends on the speed. Sorry. I just selected 'Cycle' or 'Foot' for route calculation.

edit
I've just updated ja.txt and en.txt at my first post in this topic.
Please note that I changed identifier name of "dist_mil" to ''dist_mile"

Well I know it's just an id-name and any text can be used if the id-name between config file and source code is consistent. But, mil is a different unit in length and not an abbreviation of mile. So I think it is better to change...
#253
Other features / Re: TTS voices
July 13, 2013, 19:26:53
By setting speed parameter to 20.0 and renaming en.txt to en.tts, the voice simulation works now.

I'm testing TTS navigation for now under the condition:
Locus Language : English
TTS Engine : Google TTS
Compute source : MapQuest

1. For "approximately after %N1 kilometers",
'%N1' is not replaced with numbers but is pronounced literally.

2. Tapping [Settings] -> [Navigation] -> [Choose voice] -> [Text-to-speech] or
   [Nav button] -> [Choose voice] -> [Text-to-speech] during navigation,
   the device speaks "You've arrived at your destination".  Isn't it strange?

3. It seems that the last voice before a turning point is usually given at 200 meter before the point.
Is this reasonable distance? It may be good for Cars but too far for cycle and for Foot.
Well I'm not sure if this issue should be discussed here now but I wrote it just to remember...
#254
I'm sending some reports.

1.  TTS voices
Is "voice simulation" enabled in the test version 2.13.1.2?
It  worked in the last test version 2.12.2.10 but it seems not now. So it's difficult to test.

2. compass & sat screen
I think it's strange that "Compass On/Off" button appears only in sat screen.

3. gesture
I confirmed that screen turn on/off by gesture properly works on my device (SGNoteII).

4. own web loader for login
login to Geocaching Live and OSM gives "Unexpected Problem!".
(I haven't created account on them yet.)

5. highlight of simplified dots on map
It looks better than before. I like this.
#255
Other features / Re: TTS voices
July 07, 2013, 20:30:17
Hi, gynta and menion. Thanks for information.
When testing version comes, I'll see(listen to), which text(%N1) or number(%V) gives better results.