This object is in archive! 

Issue with Quick Map Switch text encoding in 3.38

Marcin shared this problem 4 years ago
Closed

Like in title. See attached screenshot.

Replies (4)

photo
1

Good day Marcin,

interesting problem. I've downloaded the same Krakow map and no problem.

May you please attach here file Jura_Krakowsko_Czestochowska.info from the directory Locus\maps\compass.pl\ ? Thank you.

Menion

photo
1

There you go.

The same letter "ę" is not correctly displayed in map choice menu (see another screenshot). Funny that two maps below its rendered ok (Świętokrzyskie...) , so it must be some kind of special encoding in file that's not working.

But that is minor issue.


I've attached here also another screenshot of issue that also appeared in 3.38 but most probably you're already aware of it (issue with some .tar maps - they don't load)


Thanks for taking care and good luck!

Your soft is the best ;)

Marcin

photo
1

Today at night I'll look at those encodings in map files on PC and let you know.


Thanks!

Marcin

photo
1

Thanks Marcin,

indeed in your *.info file is incorrectly defined name. I have no idea why this happens to be true.

Anyway, fixed file in the attachment. You may modify "name > def" parameter on your own if the same problem exists in another map. Only important you have to keep untouched is "storeItem" parameter.

Btw. I received an error about little problematic calibration of TAR maps, but not about its complete malfunction. May you share with me one problematic TAR map for the test? Thank you!

Menion

photo
1

Hi Menion,

Please find attached .tar map you asked for. 

Let me know once you will figure it out. 

Thanks! 

Marcin 

On Sat, 25 May 2019, 19:54 Locus Map, <locus.map@asamm.com> wrote:

photo
1

Hello Marcin,

this map worked for you before?? I'm trying it with previous 3.37.2 version and map does not work as well.

Seems that Locus Map has a problem how to handle configuration for this map. In its definition is wrote that projection is "Map Projection,Latitude/Longitude", but in next calibration points is missing lat/lon and instead is there some kind of UTM coordinates. Little confusing for me.

In the case of lat/lon projection, app expect spherical coordinates like this

Point01,xy, 1818, 8360,in, deg, 49,27.03084,N, 21,47.27694,E, grid, , , ,N
Any tip on how to handle it?

Menion

Replies have been locked on this page!