Hi Steve, yes, looks much better. I did not test it, but I think it will give a different result for those cases where name contains a suffix (0x1e) . I remember these as lead in/lead out sequences for japanese characters (double byte) characters in ASCII strings? Gerd Steve Ratcliffe wrote
Hi Gerd
My idea was to optimize the cases where partial name and name are different. If I got it right, we use this to handle the highway shields. I wonder if it would be enough to move the byte(s) for the highway shield to the end of the name that is used for sorting?
Yes, we can completely remove the MultiSortKey and treat all cases the same. Just need to append any initial part of the name at the end.
As in attached (untested) patch.
..Steve
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
sort-save-mem.patch (1K) <http://gis.19327.n5.nabble.com/attachment/5835073/0/sort-save-mem.patch>;
-- View this message in context: http://gis.19327.n5.nabble.com/FW-AW-RE-computing-power-mdx-mdr-tp5834885p58... Sent from the Mkgmap Development mailing list archive at Nabble.com.