On Sat, Jun 20, 2009 at 3:29 AM, Levantovsky, Vladimir < Vladimir.Levantovsky@monotypeimaging.com> wrote: > On Thursday, June 18, 2009 11:06 PM John Daggett wrote: > > Things like machine-readable lists of domains are equivalent to a root > > string solution, like EOT, and suffer the same problems: moving the > > font file around between different servers (e.g. stage to production) > > requires constant updating of the font data, is difficult to work with > > locally (e.g. drive/path inclusions in EOT spec(!)), and breaks down > > completely when used with caching servers (e.g. Akamai). > > Root strings allow multiple different domains and paths be encoded in the > same font resource - specifying all stages (including local drives) in your > content development path should work just fine, without updating web font > data. And I would be curious to know how Akamai breaks it, since it's > supposed to be completely invisible to UA. > So any change in your workflow, or even the file layout on your local drive, requires rebuilding all your font assets or things mysteriously break. Rob -- "He was pierced for our transgressions, he was crushed for our iniquities; the punishment that brought us peace was upon him, and by his wounds we are healed. We all, like sheep, have gone astray, each of us has turned to his own way; and the LORD has laid on him the iniquity of us all." [Isaiah 53:5-6]
Received on Friday, 19 June 2009 22:16:53 UTC