(no subject)

[swaldman]

I squeeeed quite a lot when I heard that webfont support was now available in the wizard.
However, I can't figure out how to use it. I think that I'm doing something wrong with DW, but it may be that I'm doing something wrong more generally - I'm new to this.

So I've used FontSquirrel's excellent converter to produce versions of the font in all the various formats, and I've hosted them all at http://www.firecloud.org.uk/07509_centaur-webfont.extension.

I've created a file at http://www.firecloud.org.uk/centaur.css, which contains:

@font-face {
    font-family: 'Centaur';
    src: url('http://www.firecloud.org.uk/07509_centaur-webfont.eot');
    src: url('http://www.firecloud.org.uk/07509_centaur-webfont.eot?#iefix') format('embedded-opentype'),
         url('http://www.firecloud.org.uk/07509_centaur-webfont.woff') format('woff'),
         url('http://www.firecloud.org.uk/07509_centaur-webfont.ttf') format('truetype'),
         url('http://www.firecloud.org.uk/07509_centaur-webfont.svg#centaurregular') format('svg');
    font-weight: normal;
    font-style: normal;

}

In the Dreamwidth Customize wizard, I have put the font to use as "Centaur,Times New Roman,serif" in a number of fields, and I have put "http://www.firecloud.org.uk/centaur.css" as the "Embedded fonts stylesheet URL ".

And yet, I'm still seeing this text display in Times New Roman.

Help! What am I missing?

Thanks :-)
 

Comments

[exor674]

It looks like the cssproxy was failing to resolve "www.firecloud.org.uk" -- me poking at things seems to have gotten it to wake up.

I'm seeing your title in, well, a different font now.

I give up trying to make the HTML cleaner not hate me.

[momijizukamori]

I think the problem you may be running into is that Gecko is trying to save you from yourself *g* I'm seeing the new font fine in Chrome, but not in FF, which means you probably haven't reconfigured your .htaccess to allow cross-domain requests on the font (which Gecko refuses to do by default, unlike the other browsers). You'll want this block in there:

[Error: Irreparable invalid markup ('<filesmatch "\.(ttf|otf|woff|eot)$">') in entry. Owner must fix manually. Raw contents below.]

I think the problem you may be running into is that Gecko is trying to save you from yourself *g* I'm seeing the new font fine in Chrome, but not in FF, which means you probably haven't reconfigured your .htaccess to allow cross-domain requests on the font (which Gecko refuses to do by default, unlike the other browsers). You'll want this block in there:

<FilesMatch "\.(ttf|otf|woff|eot)$">
<IfModule mod_headers.c>
Header set Access-Control-Allow-Origin "*"
</IfModule>
</FilesMatch>

Re: I give up trying to make the HTML cleaner not hate me.

[swaldman]

Er, apparently I replied to my post rather than this comment. Sorry. There is a reply below....

Re: I give up trying to make the HTML cleaner not hate me.

[momijizukamori]

It happens XD and aha, Gecko strikes again.

[swaldman]

Ah HA! That fixed it, thank you.

Now I'm trying to add to it to make it use the Adobe Centaur font (which is nicer) if the user has that installed, and use the free webfont if not. I've set the hosted version to chmod 000 so that I can see what I'm doing, and I'm trying out src: local statements in the css file. And it only works in Chrome, not Firefox. Does firefox not pay attention to src:local or something?

I've got rid of the IE-fixing stuff for now for simplicity, and the css I'm trying is:

@font-face {
    font-family: 'Centaur';
    src: local('Centaur'), local('Centaur Regular'),
         url('http://www.firecloud.org.uk/07509_centaur-webfont.woff') format('woff'),
         url('http://www.firecloud.org.uk/07509_centaur-webfont.ttf') format('truetype'),
         url('http://www.firecloud.org.uk/07509_centaur-webfont.svg#centaurregular') format('svg');
    font-weight: normal;
    font-style: normal;

}

EDIT: But now it's working... I suspect there is some caching going on here and confusing things, either by the browsers or by DW's cssproxy. Ah well, it seems to work for now...

[exor674]

Yeah, DW's cssproxy caches the cleaned content for 5 minutes ( unless you have a no-caching specified in the http headers, so next time you want to mess with things, set that first and wait for it to expire! ).

[swaldman]

Fair enough, that would make sense :-)