I remember a few years ago building a ebsite and specifying a unique font using the M/S WEFT tool. I want to force browsers to use a specific font again, and came across "@font-face". I used the online utility font-squirrel, and even after doing that, I can't get the unique font to load in my web page. The sample they provide works fine, so it has to be something I'm doing... or not doing.
I know this sounds really nasty, but I've not worked with CSS before this past weekend, although I can immediately see it's advantages, and I've created so very nice pages with it. I seem to be missing the boat on this font thing, something that should be relatively simple.
I guess I'm confiused as to where the specific pieces of code go... in the index.html or the sytle.css file. Non of the tutorials are clear on that, and assume more knowledge on the subject than I have. I've even gone back to the basics - since the site I was trying to apply this to was kind of busy with code - and started working fresh on new files. Still can't get the font to work....unless I load it as a system font,.
Thks for the read, and putting up with another noob.
S~
Well...hmmm...
Not getting any love out of this exercise.
This is as far as I get.
IN the index.htm file I put
<head>
<title>Untitled Document</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<link rel="test" href="test.css" type="text/css" charset="utf-8" />
</head>
On the test.css file, it looks like this...
@font-face {
font-family: 'DistortiaRegular';
src: url('distorti-webfont.eot');
src: url('distorti-webfont.eot?#iefix') format('embedded-opentype'),
url('distorti-webfont.woff') format('woff'),
url('distorti-webfont.ttf') format('truetype'),
url('distorti-webfont.svg#DistortiaRegular') format('svg');
font-weight: normal;
font-style: normal;
}
.style2 {
font-family: distorti-webfont;
font-size: 18px;
font-style: normal;
font-weight: 400;
font-variant: normal;
color: #FF0000;
line-height: normal;
text-transform: none;
}
Text does not adopt the new font. Like I said, I must be missing something....and even though I don't like to have it that way, all the files for this test page are in the root of the site....until I get it working. Then I can tidy that up later.
Oh yeah, I also get a message when I validate the page that says:
The tag "link" has an XML style closing syntax for an empty element even though version "HTML20" is not an XML tag language. [HTML 4.0]
Hmm, I haven't done this since IE was the only browser that supported it, but it looks right to me. Doesn't it work in any browser? I suppose you have double checked that the font files are uploaded and the URLs to them are correct?
There seems to be a 3rd step to the instructions that font-squirrel kicked out...
To take advantage of your new fonts, you must tell your stylesheet to use them. Look at the original @font-face declaration above and find the property called "font-family." The name linked there will be what you use to reference the font. Prepend that webfont name to the font stack in the "font-family" property, inside the selector you want to change. For example:
p { font-family: 'WebFont', Arial, sans-serif; }
I don't know where this is supposed to go....
The help finle from font-squirrel says this about my issue:
Fonts not showing in any browser
This sounds like you need to work on the plumbing. You either did not upload the fonts to the correct directory, or you did not link the fonts properly in the CSS. If you've confirmed that all this is correct and you still have a problem, take a look at your .htaccess file and see if requests are getting intercepted.
We can forget the .htaccess part right now, I think my problem is this linking in the .css file. Idon't know that I've done it right, or if I'm supposed to define a style or something. Time for a brain break and some supper....
S~
Did you read Christian's post above? He spotted the mistake I missed. That's likely your problem.
Wait, I think there is one more mistake. You call the font-family DistortiaRegular
Well, I don't give up, but if I was ever driven to drink... this might do it.
Here is the code generated by FontSquirrel:
@font-face {
font-family: 'DistortiaRegular';
src: url('distorti-webfont.eot');
src: url('distorti-webfont.eot?#iefix') format('embedded-opentype'),
url('distorti-webfont.woff') format('woff'),
url('distorti-webfont.ttf') format('truetype'),
url('distorti-webfont.svg#DistortiaRegular') format('svg');
font-weight: normal;
font-style: normal;
}
Notice it mentions DistortiaRegular twice. It also uses src: twice, example code I found elsewhere only uses src: once. Don't know if that makes a difference. Also, I had to create a style as a subset of the stylesheet. Text would adopt the attributes of size and colour, but the actual typeface is not changing.
So again, In the index.htm (or index.html - I've tried both) file I have this hunk of code:
Well. Isn't that just ducky.
It works.
Sort of.
Sort of not.
I've been sitting here baising "working" on the fact that I can't see the typeface change in Dreamweaver. I've been using Dreamweaver for years and it shows you just what you're doing.
Apparently not this time.
I was growing tired of failin, I even resorted to looking at the source code for the html sample taht came from Font-Squirrel. Copied it to my own files. Nothing.
Well.... nothing in Dreamweaver, but for some reason I was inspired to his F12 and preview in browser and blamo,there it is... the gawd awful test text I was looking for. So, I got it working, but not within the coding app. I guess I can fix that by turning it on as a local system font, after I see it working in a browser.
I don't have that much hair left to pull out...
S~
You get the @font-face syntax from Font Squirrel inside stylesheet.css. Then have a look in the demo.html page and see how the font-family is called for BODY in an embedded style at the top of the page.
Since your font is DistortiaRegular, that's what you should use (font-family: DistortiaRegular) in your .style1 declaration, instead of "font-family: distorti-webfont".
As for DW, I have an old version too and it didn't even want to show a regular font (Verdana), when I had to make some pages with it. What I did was declare the font for all selectors embedded in the page itself. Only then it worked.
Mind you, I'm used to handcode HTML and CSS. I had never used DW before.
All's well that ends well. Never even occurred to me that you only viewed it in DW. My advice to you - use real browsers (plural) for previewing. No one surfs with DW and what its viewer is capable of and not is of no interest. It's sad to get stuck for a reason like that. Learn from it and you will get something useful out of this exercise.
@Frederiek
Well in the end I had to use the source code for the sample page provided by font-squirrel. Something in the code that was on the face of the document didn't add up, even after I figured out D/W was failing to show the font. All's well that ends well, I suppose.
@pandy Good point lesson learned. In my defense, I had previewed pages earlier in the session... I guess there were syntax errors still. After using D/W for as long as I have, it never occurred to me that it would fail to display a typeface inline. Actually, going back to the original page I had created using WEFT, D/W did display that font inline. Perhaps the difference is that I installed it as a system font to achieve the effect, and used WEFT to push the font out later. In this case, I already was aware of the font issue so I didn't install it as a system font. That' probably why D/W didn't display it. Complicates the validating procedure a bit in that I have to look at the files from another system that doesn't have the font in question on it.
And my son thought HTML was easy.
S~
It is. But CSS is a *beep*.
Sigh. I wasn't THAT bad a word. Female dog.
I didn't have DW code the font, I directly had it in an external CSS file. Am I glad that I don't have to redo an entire web site (that I already had made by hand) in DW. In my case, it was a test case, so others would be able to work in those files too.
Personally, I couldn't care less how DW showed my page while everthing was ok in the browser. And yes, in the end, that's what counts.
Actually, leaving DW and typing by hand might be the answer to that problem too. I remember things I write much better and I don't think that's unusual.
Powered by Invision Power Board (http://www.invisionboard.com)
© Invision Power Services (http://www.invisionpower.com)