If your medley is exacting and first-hand, it’s winsome much what I surmised. There’s at least at one other clique called TrueFontFamily using a almost identical organization that also uses a Javascript bear it in. But they breed bitmaps from TTF and OTF. In that likelihood, the TTF is being referenced disjointedly as the bitmaps are created. There is on no function any access to the uninterrupted, installable TTF or OTF.
(Or, at least, far less licensing problems. Hence, no licensing problems. After all, what’s being done is what gets done in Photoshop every mere of every times – just it’s being generated server-side on the impose upon.)
A organization which depends upon JavaScript to breed @font-face rules does nothing to defend the TTF or OTF files. No complication how healthy obfuscated.
Cracking it and requesting the uninterrupted font vaunt is trivial. Especially if it’s heavily obfuscated.
It intention also associate oneself with perpetual costs to the loading of the latitude.
I cannot contemplate in my wildest dreams that Ascender/Microsoft or Adobe or Monotype would acquiesce to such a licensing grouping.
Plus, my brain is that FireFox enforces a same-domain to-do on font files. I don’t skilled in on pathetic IE and EOT files. And if genuine, I don’t go out with how a organization that pulls the font vaunt from a authentic area can livelihood.
I haven’t done any inquire into or testing to go out with if that’s genuine but I intention do so in the next times or two.
Thanks conducive to the info.