
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 ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Sonntag, 16. Januar 2022 23:40 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Please try and report results of Huffman compression Hi Gerd So, for unicode, it just runs on the stream of utf-8 representation a byte at a time, rather than on unicode chars? It works but is not a good compression. Ticker On Sun, 2022-01-16 at 19:16 +0000, Gerd Petermann wrote:
Hi Ticker,
you seem to think that the encoder must understand what a codepoint is? I don't think so. The only important thing is that utf-8 still can use a single 0 to terminate strings.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Sonntag, 16. Januar 2022 19:43 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Please try and report results of Huffman compression
Hi Gerd
More unicode problems: The data structures for the frequency analysis and then the list of chars to encode will all need attention.
Ticker
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev