Hi,
Thanks for unlocked file, run fine on 3490LMT after boot GPS with French automatic language.:)
Printable View
Hi,
Thanks for unlocked file, run fine on 3490LMT after boot GPS with French automatic language.:)
I might be late to the game, but the converted .gpi is corrupted due to the incorrect text substitution at address #8889a2
It incorrectly find "SL" belonging to lang "CS" and changed it to "CSK" which changed the size of the MLText causing the length to be wrong. I'm surprise that no one complained; maybe Garmin software just ignore the error for that record and recovered/continued. Fortunately my parser coughed :)Code:#88a97f 3e 43 53 4c
> C S L
Here is one incorrectly changed from SK to SL, the SK is part of ">ESK", not ">SK"
Note that the above are just examples of incorrectness; there are many more that have similar errors.Code:#1cd0b7d 3e 45 53 4b
> E S K
So just changing the text "SL" to "SK" and vice-versa is wrong. You must do what sbog said:
Change "<hr>SL" to "<hr>XX", change "<hr>SK" to "<hr>SL", and then change "<hr>XX" to "<hr>SK"
Here is the correct conversion
Spoiler: .
When i use this gpi i see no problem, all work ok.
Maybe as you wrote, garmin somehow continue.
Trust me the error is there :) You can check it using hex editor or file comparer; just use the example addresses that I posted. Then you can find out the POI's that have the problem and see if your Garmin show it correctly (remember it corrupted the unfortunate record that happen to match substring "SL" or "SK", not the SL/SK record) Make sure you test the lang CS or ES because those two are the corrupted records, not SL nor SK lang (lucky you lolypop000) So I guess if you are using SL or SK, you're ok; everybody else better use original or corrected conversion.Quote:
Originally Posted by lolypop000 [Only registered and activated users can see links. Click Here To Register...]
I use SL, so this is reason why all work OK :)
I think that repaired version download only people from SL or SK and this is reason why nobody see error ;)
Yea, isn't it ironic? Unless you are using a lang that has the corrupted data, you'll never see it. Still kind of bad to carry all that excess data. I mean if you're interested in only EN, then the file containing just english should be a lot smaller.Quote:
Originally Posted by lolypop000 [Only registered and activated users can see links. Click Here To Register...]
If you make GPI parser it will be very interesting for all. I see your thread but it is no interesting for me because I use anothers region and data base. It is pity. I want to be involved to discussion too...
My parser is WIP (Work in Progess); that is why I'm searching for any .gpi that would causes problem so I can fix it. There is nothing to prevent anyone from taking in discussion. What is needed are testers (like x-trail) that can help in trying to figure out best way to implement some of my ideas (like directional alerts) I do not have resource to make parser available just yet.Quote:
Originally Posted by Giomen [Only registered and activated users can see links. Click Here To Register...]