Hi Gerd
I looked more carefully after your last post and I agree; except "p"
increases when the partialString is at the end and "s" when at the
start.
There were some cases that confused, but I think these were mostly
where there was a 0x1f (zoomSuffix) in the string; p & s > 1.
I notice that
Betreff: Re: [mkgmap-dev] [mkgmap-svn] Commit r597: fix stupic typo: use given
recsize instead of constant 5
Hi Ticker,
the p/s numbers are not offsets, they are some kind of id for equal prefix
strings or suffix strings.
Not sure but I think those prefix/suffix strings are marked by the stuff
-dev] [mkgmap-svn] Commit r597: fix stupic typo: use given
recsize instead of constant 5
Hi Gerd
Going through the Mdr7 p and s values and mdr32/3 table (looks good
now) I can't see any logic to it.
Mdr32/33 has 210 records, which, as you say, look like common parts of
street names.
Mdr7 p= has
onntag, 23. Januar 2022 11:51
> An: mkgmap-dev@lists.mkgmap.org.uk; mkgmap-...@lists.mkgmap.org.uk
> Betreff: Re: [mkgmap-dev] [mkgmap-svn] Commit r597: fix stupic typo:
> use given recsize instead of constant 5
>
> Hi Gerd
>
> Looking at the mask logic in MdrDisplay printSect
for mkgmap
Betreff: Re: [mkgmap-dev] [mkgmap-svn] Commit r597: fix stupic typo: use given
recsize instead of constant 5
Hi Ticker,
the recsize 5 in mdr32 was in the large mdr.mdr file from Nick. I think the
extra bytes where almost always 0.
I don't dare to share a complete Garmin map, and I
the effect that
you expect?
Gerd
Von: mkgmap-dev im Auftrag von Ticker
Berkin
Gesendet: Sonntag, 23. Januar 2022 11:51
An: mkgmap-dev@lists.mkgmap.org.uk; mkgmap-...@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] [mkgmap-svn] Commit r597: fix stupic typo: use
Hi Gerd
Looking at the mask logic in MdrDisplay printSect30/32 I'd guess that
the pointer size is always governed by the size of Mdr31/33 and any
extra bytes are something else, probably the length of the string.
I've haven't managed to find any maps with these sections so I can't be
sure. How
