@kas1e
No, but this problem is just related to the network/stack, anyway. Nothing you could reproduce.
About that site without visible fonts, it's just using complex font rendering path, which is no-op in the webkit freetype implementation (only pango and mac/win implementations supports the complex path properly).
But it's quite trivial to tweak OWB and fallback to simple font rendering path (of course, it won't handle arabic ligatures properly doing so, but it's better than blank output). I did that in later OWB versions.
|