
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

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 Mdr16. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Montag, 10. Januar 2022 13:14 An: mkgmap development Betreff: [mkgmap-dev] LBL file encoding - Huffman 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.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (2)
-
Gerd Petermann
-
Ticker Berkin