[mkgmap-dev] Please try and report results of Huffman compression

Mon Jan 17 15:41:36 GMT 2022

Hi Arndt,

I think there are still problems with address search, probably not related to compression, but to problems with --lower-case.
I'm still analysing it...

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Arndt Röhrig <arndt at speichenkarte.de>
Gesendet: Montag, 17. Januar 2022 15:56
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Please try and report results of Huffman compression

Hi all,

now the search works with r4870 and Speiche_NRWplus. Thankx for the fix!

Greetz

Arndt

Gerd Petermann <gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com>> hat am 17.01.2022 11:35 geschrieben:

Hi all,

Ticker found the error, see https://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4870
I also fixed display tool.

Please try again with r4870: https://www.mkgmap.org.uk/download/mkgmap-mdr2-r4870.zip

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces at lists.mkgmap.org.uk>> im Auftrag von Gerd Petermann <gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com>>
Gesendet: Montag, 17. Januar 2022 11:16
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Please try and report results of Huffman compression

Hi Ticker,

yes, thanks, that was the problem. The table width also depends on this and I didn't understand that so far.

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces at lists.mkgmap.org.uk>> im Auftrag von Ticker Berkin <rwb-mkgmap at jagit.co.uk<mailto:rwb-mkgmap at jagit.co.uk>>
Gesendet: Montag, 17. Januar 2022 10:44
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Please try and report results of Huffman compression

Hi Gerd

I'm looking at GPXSee at the moment.

Significant to the problem lots of symbols:

The size of the tab1 offset into the symbol list is the same as the
size of the size (the 1+ bytes after the 8/symbol width), so, if more
than 127, it needs an extra byte.

Ticker

On Mon, 2022-01-17 at 04:26 +0000, Gerd Petermann wrote:
Hi Ticker,
yes, one byte at a time. Else we would need symbol width > 8, and
Garmin doesn't use that for the unicode maps that I know.to
I plan to contact the author of GPXsee, Martin Tůma. He seems to know
much more than we do and maybe he is willing to help.
Gerd

_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk<mailto:mkgmap-dev at lists.mkgmap.org.uk>
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk<mailto:mkgmap-dev at lists.mkgmap.org.uk>
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk<mailto:mkgmap-dev at lists.mkgmap.org.uk>
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev