On Thu, Jan 29, 2009 at 8:32 PM, Lance Hepler <span dir="ltr"><<a href="mailto:nlhepler@gmail.com">nlhepler@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> That's a very interesting plan. I can understand its usefulness for cross-platform consistency. And I don't mean to attack your hard effort, but is that really practical? Each platform (Windows/Mac/*nix) has its own font-handling stack, and in the case of the two former, a certain look-and-feel of the font rasterization (Cleartype/Whatever-Apple-does) that is native to each platform. Users of these platforms sort of expect consistency in the font rendering, and moving all the rasterization into cairo would make it harder for developers to build applications on these platforms that "blend in" with the native environments. Is that sort of behavior desirable? I mean, I realize having consistent behavior between platforms is desirable, but I am uncertain as to the usefulness in this case.</blockquote> <div><br>I agree. We're very interested in having cross-platform shaping code in Gecko, but users really seem to want text rasterization that's consistent with other apps on the platform. I guess we don't mind if Linux/X/GTK font rasterization is in cairo, as long as we don't have to use it on the other platforms.<br> <br>Rob <br></div></div>-- <br>"He was pierced for our transgressions, he was crushed for our iniquities; the punishment that brought us peace was upon him, and by his wounds we are healed. We all, like sheep, have gone astray, each of us has turned to his own way; and the LORD has laid on him the iniquity of us all." [Isaiah 53:5-6]<br>