today I updated my chrome for OSX to version 38.0.2125.101. Now all my unicode characters from a custom svg font are not shown properly. truetype and woff are still working, svg not any more.Any idea why?
--
You received this message because you are subscribed to the Google Groups "Chromium Apps" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-app...@chromium.org.
To post to this group, send email to chromi...@chromium.org.
Visit this group at http://groups.google.com/a/chromium.org/group/chromium-apps/.
For more options, visit https://groups.google.com/a/chromium.org/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
On Mon, Oct 13, 2014 at 6:15 AM, PhistucK <phis...@gmail.com> wrote:Is this related specifically to your Chrome application, or are you talking about regular web pages?Anyway, this is an intended change, starting with Chrome 38. SVG fonts are only supported on Windows systems, older than Windows 7, due to their poor font rendering.You should be able to convert the SVG font to WOFF and your fonts should look good.Note that only Chrome and Safari supported SVG fonts (and I think I read somewhere that they are contemplating dropping support as well, but I might be mistaken).
WebKit is implementing a built-in SVG->WOFF converter, I believe, so they can remove the SVG font code path. Also, the next iteration of the SVG spec removes SVG fonts.
I was slightly wrong. WebKit is converting SVG to OTF. Look for WebKit bugs with the [SVG -> OTF Converter] title tag.Stephen.