<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hello!<div class=""><br class=""><div class="">As of r197145, the SVG -> OTF Font Converter is enabled on the OS X, iOS, and Apple Windows ports. This converter replaces our old, invasive, error-prone, and security-hole-ridden SVG font support in WebKit. The converter is much faster (read: at least 3 orders of magnitude) and produces much better results (subpixel-antialiased text) than the old code path, as well as having significantly fewer security vulnerabilities.</div></div><div class=""><br class=""></div><div class="">As soon as we get all the ports on the converter, I’d love to be able to delete all the old code. However, GTK and EFL are still using the old code path. Turning the converter on should be simple: I’ve posted patches for GTK [1] and EFL [2] to flip the switch. Note that some tests may need to be rebaselined; the underlying graphics system will likely provide differently quantized glyph metrics than the existing code path. There are also some known bugs; if you want to learn more about them, please feel free to reach out to me.</div><div class=""><br class=""></div><div class="">Please reply by Tuesday, March 15 so I can go ahead with this project!</div><div class=""><br class=""></div><div class="">Thanks!</div><div class=""><br class=""></div><div class="">1. <a href="https://bugs.webkit.org/show_bug.cgi?id=155191" class="">https://bugs.webkit.org/show_bug.cgi?id=155191</a></div><div class="">2. <a href="https://bugs.webkit.org/show_bug.cgi?id=155192" class="">https://bugs.webkit.org/show_bug.cgi?id=155192</a></div><div class=""><br class=""></div></body></html>