Re: [mkgmap-dev] Fix and augment sort definitions

2022-01-10 Thread Gerd Petermann
Hi Ticker, didn't try it: Will mkgmap complain when building an indexed gmapi/gmapsupp where some tiles where freshly compiled with the new version and others with an older (like Felix and Carlos do)? Gerd Von: mkgmap-dev im Auftrag von Ticker Berkin G

Re: [mkgmap-dev] [mkgmap-svn] Commit r4854: - fix possible error when negativ index was written to lookup table

2022-01-10 Thread Ticker Berkin
Hi Gerd I think I got table1 / table2 names the wrong way round. The bit about "should it need" is probably necessary when all the levels fit into the prefix table but it isn't full. I won't look at it again until you want me to. Ticker On Mon, 2022-01-10 at 19:16 +, Gerd Petermann wrote: >

Re: [mkgmap-dev] [mkgmap-svn] Commit r4854: - fix possible error when negativ index was written to lookup table

2022-01-10 Thread Gerd Petermann
Hi Ticker, table1 size depends on the number of levels with values and the existence of the lookup table, empty levels are not stored. When there is a lookup table (table2) we must not store the corresponding top 5 /6 levels in table1. I don't understand the part after "Should it need ..." . It

Re: [mkgmap-dev] [mkgmap-svn] Commit r4854: - fix possible error when negativ index was written to lookup table

2022-01-10 Thread Ticker Berkin
Hi Gerd More minor stuff - Still haven't understood the mincode parts mdr/Mdr16.java: loopupBits/lookupBits is very confusing. Can you have lookupBits for table2 size and something else for table1 size If maxDepth < initial size (5 or 6), can't you just set table1 size to maxDepth and set table

Re: [mkgmap-dev] LBL file encoding - Huffman

2022-01-10 Thread Gerd Petermann
Hi Ticker, interesting. I thought this only happens with NT format (if that is what the existience of an GMP file means) Of course we should try to use it whereever we can manage to write correct data. Have no time to look into this today, but it should be easy to extract the calc() method from

[mkgmap-dev] LBL file encoding - Huffman

2022-01-10 Thread Ticker Berkin
It looks like the LBL file could be Huffman compressed with an ENCODING value of 11. Is there scope for having the new Huffman logic with app/labelenc/CharacterEncoder /CharacterDecoder interface? Ticker ___ mkgmap-dev mailing list mkgmap-dev@lists.mkg

Re: [mkgmap-dev] Fix and augment sort definitions

2022-01-10 Thread Ticker Berkin
Hi Gerd What I meant was that keyboards/devices don't normally have ways of entering the single chars "…", "¼", "½", "¾", "™". Names with these might be presented by Garmin software after some initial chars have been entered and you can then select the complete name that contains these chars. I

Re: [mkgmap-dev] Fix and augment sort definitions

2022-01-10 Thread Gerd Petermann
Hi Ticker, I've committed displaySrt_v2.patch . I don't fully understand the comment "Leave the above because no method of inputting them anyway and unlikely at start of names." It is possible to enter these characters in MapSource and I think MapSource uses MDR12 when you type only a few char

Re: [mkgmap-dev] Fix and augment sort definitions

2022-01-10 Thread Ticker Berkin
Hi Gerd I tried various approaches to fixing "Find" when the fixed length Mdr17 (maybe also Mdr12) prefix contains sort.expand chars and couldn't make it work. I could documents these attempts in Sort.java if you feel this is worthwhile. New patch attached that, for cp1252, leaves "ß" as its own

Re: [mkgmap-dev] [mkgmap-svn] Commit r4854: - fix possible error when negativ index was written to lookup table

2022-01-10 Thread Gerd Petermann
Hi Ticker, thanks for reviewing, fixed the bug in MDR17. I've not even started to optimize anything reg. performance. I'm still trying to understand the idea of the shifted minCode values and I think I understand it now after looking at the code in GPXSee (huffmantable.cpp method HuffmanTable::s

Re: [mkgmap-dev] [mkgmap-svn] Commit r4854: - fix possible error when negativ index was written to lookup table

2022-01-10 Thread Ticker Berkin
Hi Gerd Just starting to read the new code more carefully and a few comments: In Mdr17 the following line should be deleted: len = (len << 1) + 1; Mdr15 is not written forDevice so can skip all the compression stuff. Have you seen an example with unicode. There seem to be too many assum