chrome

Arabic web-font Mark feature bug in Safari

Hello,

I've stumbled upon a bug in Safari (and webkit browsers) when using the Mark feature in web fonts,
As demonstrated by the screenshot, when a word has diacritics either on the beginning or the ending, the word space gets omitted.

I've tried my own fonts, and multiples fonts by other vendors but i get the same result, Only fonts that implement the Mark feature display the error.
Is anyone else facing the same problem?

Tested on Safari 6.0.5/osx 10.8.5

liga GSUB in webfont (otf-cff) works in Firefox, doesn't work in Chrome or IE

Forums: 

Hey all,

I'm working on an on-page glyphet font generator in JavaScript, and am making decent headway, except I've run into a problem with GSUB ligature substitution...

If you load http://pomax.github.io/CFF-glyphlet-fonts in Firefox, you'll note that the "small" font, without GSUB table, renders the character "~" as a rectangle with a cutout. The second font has a GSUB table for the 'liga' feature with a lookup type 4 to turn the sequence "c,u,s,t,o,m" into "~", http://github.com/Pomax/CFF-glyphlet-fonts/blob/gh-pages/binaries/with%20GSUB/customfont.gsub.ttx#L271, which works in Firefox, but not in Chrome or IE (of course IE doesn't like plain .otf, so the fonts are repackaged as uncompressed WOFF as well, as fallback option).

I can't see more than a half of the Unicode (utf-8) chars

I've tested it here, http://www.fileformat.info/info/unicode/utf8test.htm
No talking about the miscellaneous ones.

Is it Windows 7 fonts? Is it Chrome rendering? Is it some configuration I should tweak? Any help is welcome!
I've just checked that UTF-8 was selected in Chrome codification, and it was. Strangly I can see more symbols in IE 11 (!)

Chromebook PIxel: an expensive 239ppi web browsing "netbook"

chrome.blogspot.com/2013/02/the-chromebook-pixel-for-whats-next.html

By comparison, Surface Pro is 207.82 ppi and a MacBook Pro 13" is 227 ppi. My iPhone 4s, by comparison stands tall at 326 ppi, although the next generation of phones (like HTC One) should pass it by.

Should I switch to the metric system when discussing this?