<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hi Steve,<br><br>I think in the old algo the bytes of the suffix<br>were compared at last, with the patch they are compared <br>before the prefix.<br><br>Gerd<br><br><div>&gt; Date: Thu, 26 Feb 2015 22:47:42 +0000<br>&gt; From: steve@parabola.me.uk<br>&gt; To: mkgmap-dev@lists.mkgmap.org.uk<br>&gt; Subject: Re: [mkgmap-dev] FW: AW: RE:  computing power mdx/mdr<br>&gt; <br>&gt; Hi Gerd<br>&gt; <br>&gt; &gt; yes, looks much better. I did not test it, but I think it will<br>&gt; &gt; give a different result for those cases where name contains<br>&gt; &gt; a suffix (0x1e) . I remember these as lead in/lead out sequences<br>&gt; &gt; for japanese characters (double byte) characters in ASCII strings?<br>&gt; <br>&gt; <br>&gt; Japanese almost certainly doesn't work with the global index anyway.<br>&gt; I don't see that there would be a difference however - the<br>&gt; MultiSortKey is effectively just sorting on the concatenation of the<br>&gt; partial and its prefix.<br>&gt; <br>&gt; ..Steve<br>&gt; _______________________________________________<br>&gt; mkgmap-dev mailing list<br>&gt; mkgmap-dev@lists.mkgmap.org.uk<br>&gt; http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev<br></div>                                               </div></body>
</html>