<div dir="ltr"><div>1) because there is a special scanning method for Japanese<br></div>2) because unicode diacritics and other combining chars should be rendered specially<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">
2013/9/25 tim Rowledge <span dir="ltr"><<a href="mailto:tim@rowledge.org" target="_blank">tim@rowledge.org</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
On 24-09-2013, at 3:14 PM, Yoshiki Ohshima <<a href="mailto:Yoshiki.Ohshima@acm.org">Yoshiki.Ohshima@acm.org</a>> wrote:<br>
><br>
><br>
><br>
> I'd support a rewrite of the whole thing, and perhaps would do more<br>
</div>> "total rewrite" approach…<br>
<br>
<br>
That's easy for you to say; you actually know about i18n stuff. I can't even reliably spell it…<br>
<br>
What do you remember about the various scanMultiCharactersCombiningFrom:to:in:rightX:stopConditions:kern: methods? The only 'live' reference to them is commented out in Unicode class>scanSelector, so we could argue that they all ought to be deleted. But I doubt all that work was done just for the hell of it and if it isn't in use now there was presumably a reason for the change.<br>
<div class="im"><br>
tim<br>
--<br>
tim Rowledge; <a href="mailto:tim@rowledge.org">tim@rowledge.org</a>; <a href="http://www.rowledge.org/tim" target="_blank">http://www.rowledge.org/tim</a><br>
</div>Useful random insult:- Has a pulse, but that's about all.<br>
<br>
<br>
<br>
</blockquote></div><br></div>