Thread: Fuel Types and Vehicle Charge Points for Europe

If you look for XX you will find it in gpi so you can't use this in your 3 step, but if you use ŽŽ for your 3 step then work like charm, thank you for this tip i forget about this

Then you must also change from Vodík to Vodik but you must do this manual becouse also CS language have Vodík.

p.s.
Vodík is in hex = 56 6F 64 C3 AD 6B
Vodik is in hex = 56 6F 64 69 6B

You must change Vodík to Vodik like this: 56 6F 64 69 6B 20

Here is repaired Fuel Types and EV Charging for Slovenian and Slovakian user
Now you will have all in your language.

[Only registered and activated users can see links. ]

Repaired gpi from above link look like this if you have text in Slovenian language:








Original gpi from Garmin site look like this if you have text in Slovenian language:

Look here in decrypted file you find XX

[Only registered and activated users can see links. ]

Originally Posted by lolypop000

Look here in decrypted file you find XX

So what?
i advised to look for <hr>XX - six bytes (in hex: 3C 68 72 3E 58 58), can't realize why you limit search string to two bytes only.

Originally Posted by sbog

So what?
i advised to look for <hr>XX - six bytes (in hex: 3C 68 72 3E 58 58), can't realize why you limit search string to two bytes only.

Becouse i search in text not hex
Slovenian and Slovakian user now have working Fuel Types and Vehicle Charge Points.gpi thank to syzygy for decrypted file i hope user will give Rep to syzygy.

[Only registered and activated users can see links. ]

And i like to thank you again @sbog for tip for autochange becouse i forget this function.

p.s.
I am not programmer so i don't know all tips and tricks but i try to learn from you who know how to do it.
My only goal is to help other users who don't know how to do it.
So, respect and thank you both for all your help and tips.

p.s.
the same link for repaired gpi is also in post n18 on previous page.
You have also in post #18 picture how is look before and after.
Also in Caty post #2 you have link for download

I might be late to the game, but the converted .gpi is corrupted due to the incorrect text substitution at address #8889a2

Code:

Please Login or Register to see the links

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
Here is one incorrectly changed from SK to SL, the SK is part of ">ESK", not ">SK"

Code:

Please Login or Register to see the links

Note that the above are just examples of incorrectness; there are many more that have similar errors.
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: .

[Only registered and activated users can see links. ]

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.