Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Likes Likes:  0
Results 1 to 8 of 8
  1. #1
    Junior Member
    Join Date
    Oct 2017
    Location
    Slovenia
    Posts
    5
    Rep Power
    0

    help Wrong city names (language) in iGO 8.3.5 / Primo 2.4 and the latest TomTom maps

    I have a "test" SD card with 3 versions of iGO 8.3.5 and 2 versions of IGO Primo 2.4, running on an old MioMoov 360 with VisualGPS. All 5 versions are running just fine with the latest HERE 2018/Q2 maps, while running exactly the same copies with TomTom maps 2018.06 (10xx fix) or 2017.12 displays Austrian city Graz as "Stajersky Hradec", and capital Wien (Vienna) as "Viden" (or something like that - I guess Czech or Slovak names for them). My language set is always Slovenian (not Slovak). I'm pretty sure I didn't have this issue with older TomTom maps (2017.06 and older). Slovenian names would be "Gradec" and "Dunaj", by the way.

    Does anyone have a clue what might be a reason for that (somehow Slovenian and Slovak to be erranously mixed or so?)? I don't have anywhere some Czech or Slovak language set (all settings for HERE and TomTom are exactly the same, and no issue with HERE!).

    And, even more important - how to fix it.I don't mind if the names are displayed in original language (Graz / Wien) or in Slovenian (Gradec / Dunaj), but the language as now (Czech / Slovak / Polish...?) s quite confusing for me (not for those two cities that much, as I know what they are by their location on the map, but there might be some more such names for places located in the areas I'm not that familiar with...).

    My device details (to staisfy the rules ;-)):
    - What is Device that you have problem with? Mio Moov 360
    - What is device screen resolution? 480x272
    - Whether the device is rooted or not (for Android based devices)? does VisualGPS count here? ;-)
    - WinCE (I guess 5)
    - Which version of the navigation software, exactly? 5 different, as above - iGO 8.3.5 and Primo 2.4
    - Where the navigation software is (internal / external memory)? SD Card
    - Which edition of maps and extras? TomTom 2018.06 fix and 2017.12
    - Whether the use of the skin (which)? no
    - something about a specific addition that you may use; no

  2.    Advertissements


  3. #2
    Global Moderator Wrong city names (language) in iGO 8.3.5 / Primo 2.4 and the latest TomTom maps
    Wrong city names (language) in iGO 8.3.5 / Primo 2.4 and the latest TomTom maps
    Midnight Blues's Avatar
    Join Date
    Aug 2009
    Location
    EU
    Posts
    1,009
    Rep Power
    994

    Default

    It's obvious that it is problem within map files.
    But how are those names displayed if you change program language to English or German?
    NO THANKS POSTS ALLOWED, NO LIKES NEEDED, ALL MIRRORS APPRECIATED
    ztsyz4
    Password for all my uploads: gpspower.net

  4. #3
    iGO Moderator Wrong city names (language) in iGO 8.3.5 / Primo 2.4 and the latest TomTom maps
    Wrong city names (language) in iGO 8.3.5 / Primo 2.4 and the latest TomTom mapsWrong city names (language) in iGO 8.3.5 / Primo 2.4 and the latest TomTom maps
    Boki_Srb's Avatar
    Join Date
    Jun 2014
    Location
    Niš
    Age
    46
    Posts
    1,984
    Rep Power
    1098

    Default

    Hmm, on my navi, with P 2.0 (KIA) and TT maps, I don't have problems. But, I am using (Serbian) language file that is improved (by BD).
    Also, phoeneme files could have influence, I am using them.
    Edit:
    Just tested with Primo 2.4 (Civic) - everything is OK, also.
    Last edited by Boki_Srb; 6th November 2018 at 07:16 PM.
    Before asking a question, know it's already discussed here and at 99.9% is not unique. Use search.
    NO ONE IS A SEER, READ (click on): [Only registered and activated users can see links. ] <- Click!
    [Only registered and activated users can see links. ] <- Click!

    Spoiler: obs
    Many questions become very arduous, a lot of time chewed deja vu...Since we have lost all the year of work and effort, many people have no will to answer the same questions again. Me neither. Use a search, please.

  5. #4
    Junior Member
    Join Date
    Oct 2017
    Location
    Slovenia
    Posts
    5
    Rep Power
    0

    Default

    Thank you both for help / interest.

    I've checked just to be sure (iGO 8.3.5.231128) - replacing just maps with 2017.06 makes things to go as expected (displayed: Graz).

    Removing phoneme (iGO 8.3.5.193799) - no difference with 2017.12 and 2018.06 (crashing with 2018.03 and 2018.06 first release / before fix).

    Switching to Serbian language (iGO 8.3.5.193799), w/o phoneme files - Maribor displayed with latin letters (same as in Slovenain letters), Graz dispalyed as Grac and Klagenfurt as Klagenfurtska or so (in Cyrillic - hope to read it correctly, don't practice much recently...).

    Switching to English (UK), iGO 8.3.5.193799, w/o phoneme files - Graz is Graz, Wien is Vienna - as expected.

    Seems to me that TomTom has done something wrong (maybe somehow related to issues with recent versions causing iGO / Primo to crash?). Is there any guide about how to mess with map files - probably possible only with hex editor (to correct the language codes)?

    Tested also with Primo 9.6.5.306142 and primo 9.6.13.405512.

    It is interesting that switching to Serbian Latin (author: BD) displays names in original language (Graz, Wien etc.), while switching to English (UK) displays Vienna. All for TomTom 2018.06 maps (latest, with fix).
    Last edited by Boki_Srb; 7th November 2018 at 07:15 AM.

  6. #5
    iGO Moderator Wrong city names (language) in iGO 8.3.5 / Primo 2.4 and the latest TomTom maps
    Wrong city names (language) in iGO 8.3.5 / Primo 2.4 and the latest TomTom mapsWrong city names (language) in iGO 8.3.5 / Primo 2.4 and the latest TomTom maps
    Boki_Srb's Avatar
    Join Date
    Jun 2014
    Location
    Niš
    Age
    46
    Posts
    1,984
    Rep Power
    1098

    Default

    Recent language files also contain a code layout and the corresponding keyboard\
    It's probably because of that. You need very latest UK lang file, if there is any.
    Before asking a question, know it's already discussed here and at 99.9% is not unique. Use search.
    NO ONE IS A SEER, READ (click on): [Only registered and activated users can see links. ] <- Click!
    [Only registered and activated users can see links. ] <- Click!

    Spoiler: obs
    Many questions become very arduous, a lot of time chewed deja vu...Since we have lost all the year of work and effort, many people have no will to answer the same questions again. Me neither. Use a search, please.

  7. #6
    Junior Member
    Join Date
    Oct 2017
    Location
    Slovenia
    Posts
    5
    Rep Power
    0

    Default

    There is no problem with English (UK) language files, as well as with Serbian (latin) on Primo. I have a problem with Slovenian language (by Janch).

    There is also no problem with most recent HERE maps! Only with TomTom 2017.12 and 2018.06. (2018.03 crashes iGO / Primo).

    Do you know how to edit / instert proper language code in Slovenian language file (to display city names in Slovenian or at least not localized at all / displayed as in the Country, like Graz, Wien etc. - more or less as Serbian Latin does)? Or, where to find more details about that (how it works, code / language tables etc.)?

    Or, is there any setting in some iGO / Primo configuration files to set names in map view to be displayed in local language (Graz, Wien etc. in Austria), not localized (should be Gradec, Dunaj etc. in Slovenian)? That would be OK for me as well.

  8. #7
    Junior Member
    Join Date
    Jan 2016
    Location
    Prague
    Posts
    2
    Rep Power
    0

    Default

    It needs to be edited in the info.ini file, which is located in lang_slovenian.zip. Significant is the semicolon before languagekey = "slovenian". This should look like this after editing:
    [INFO]
    ;languagekey="slovenian"
    flag="flag_svn.bmp"
    Last edited by geoferoone; 7th November 2018 at 09:33 AM.

  9. #8
    Junior Member
    Join Date
    Oct 2017
    Location
    Slovenia
    Posts
    5
    Rep Power
    0

    Default

    Thank you for an info / tip very much.

    Unfortunately, it doesn't seem to work for me (Slovenian language is not displayed on the list anymore at all, I had to choose something else - English...).

    What shall be an encoding for info.ini (if I open with gedit on linux, it shows me UTF-16 - is it possible?!). Maybe I screwed that? I've edited in an archive directly, as advised somewhere else...

    I've also noticed an interseting thing in Serbian Latin langauge file - in info.ini (dated March 21, 2014 - by Brown Dog) iso_lang="en-gb"... Does anybody know how that setting matters?

    What if I would change LCID (to something not recognized by iGO / Primo - like 0x0000 or 0xffff) - would it make places to be displayed in "original" (local) language(s) on map?

    ================================================================================


    Sorry, geoferoone - it works. Thank you very much!

    It didn't work on linux (tried with the latest 7-zip through wine, and 2 different gnome archivers / edited with gedit end even with hex editor, no go with any combination...), I'll try to figure out which part is causing a problem (and, how it can be done also in linux, if at all...).

    On windows, editing "in ZIP file" (with notepad) finally worked (even if info.ini here also seems to be extracted to some temp location, edited and saved back into ZIP - but it is obviously done in a bit different way as in linux...).

    By the way - changing to iso_lang="en-gb" didn't work for me (it obviously has no influence to my issue). Changing LCID is causing Slovenian language to disappear from the list of langages, and another language has to be set at boot.

    Thank you all for help again.
    Last edited by Boki_Srb; 9th November 2018 at 08:02 AM.

 

 

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.