Never thought about this until you brought it up – thanks! I’ve been digging more heavily into typography recently and this article came in at a great time.
Copy & paste the code below to embed this comment.
backlinkbuilder
ESPON® Printer Support just a free call away at 888-817-3484 Toll Free Number. PCASTA, have many noted expert to solve your Epson® printers issues, Epson® Printer Problem, Epson issue, Troubleshooting, error Support. We are able to solve almost all types of Epson® Printers’ errors, Epson® Printer Problems Support.
Copy & paste the code below to embed this comment.
SinisterKid
Interesting article. I’m still a little new to using web fonts. When you make the @font-face rule, how are you getting the font URLs listed in the rule?
Copy & paste the code below to embed this comment.
Alan Stearns
SinisterKid,
For Google fonts, the rule I used came from following the link href in the “Add this code to your website” part of their UI. If you follow the link in IE, you get the most cross-browser @font-face rule that service provides.
Great suggestion, but the overall result of these new best practices is the increased workload for the type foundries and designers, who must now create additional styles (bold, italic, etc) for their digital fonts. Most of the trendy new design fonts only have a single variant to begin with.
I wasn’t aware of this as a problem with web design fonts. Now i know that i need to be more selective in the family fonts i chose, and whether or not i choose to bold them.
Makes perfect sense though; and your article outlines very clearly all the relevant key points.
It is so true that HTML editors, unlike more publish oriented software, often ignores the type and font designations. It was common, and still is, to have multiple font choices for the browser to pick from. Since until recently, browsers and/or the OS stored fonts, and the web page authors could only guess on what fonts would be served by the various browsers, pretending to have any control was nearly useless.
Finally, with HTML5/CSS3 compliant browsers, we finally can truly start to deal with typefaces, fonts, if not kerning, etc. And since the HTML editors within a CMS often cannot handle the uses of bold and italic and standard HTML style elements like H1…H5, or keep them from overlapping, this leaves it difficult to compensate.
Better web site publishing that integrates tightly controlled styles and CSS with the system to edit content is needed. And, since some browsers cannot handle this, old browsers will still cause problems, it is important to still use “serif” etc.
Also, since semantic understanding is the reason for styles, use of bold, cite, H1, italics, strong, and the rest, must continue to be present, so do not let style settings undo understanding.
By the way, this problem of worrying about fonts on web pages is a beautiful problem to have (pun intended). How to present content in as clear a way possible is the whole point. Now if we can better address printing web pages …
Well! thanks for informative article. I am working for Minneapolis Web Design firm now. I could easily have provided a bold version of the font for the headings but all that would have done is add bloat to the byte count and it wouldn’t have added one whit to the substance of what was being communicated. So question number one is: are you against letting the browser handle the bolding and italicizing in all instances?
21 Reader Comments
Back to the Articleofflajn
I’m allways happy reading about custom fonts, the web is full of the old Times new and Arial.
“Offlajn”:http://offlajn.com
ajtreat
Never thought about this until you brought it up – thanks! I’ve been digging more heavily into typography recently and this article came in at a great time.
backlinkbuilder
ESPON® Printer Support just a free call away at 888-817-3484 Toll Free Number. PCASTA, have many noted expert to solve your Epson® printers issues, Epson® Printer Problem, Epson issue, Troubleshooting, error Support. We are able to solve almost all types of Epson® Printers’ errors, Epson® Printer Problems Support.
“EPSON Printer Supporto”:http://www.pcasta.com/support-for-epson-printer/
SinisterKid
Interesting article. I’m still a little new to using web fonts. When you make the @font-face rule, how are you getting the font URLs listed in the rule?
src: url(‘http://themes.googleusercontent.com/static/fonts/ »
diplomata/v1/8UgOK_RUxkBbV-q561I6kPY6323mHUZFJMgTvxaG2iE.eot’);
src: local(‘Diplomata’), local(‘Diplomata-Regular’),
url(‘http://themes.googleusercontent.com/static/fonts/diplomata/v1/ »
8UgOK_RUxkBbV-q561I6kPY6323mHUZFJMgTvxaG2iE.eot’) format(‘embedded »
-opentype’), url(‘http://themes.googleusercontent.com/static/ »
fonts/diplomata/v1/8UgOK_RUxkBbV-q561I6kD8E0i7KZn-EPnyo3HZu7kw.woff’)
format(‘woff’);
If I’m using another Google font, how would I get that information? I don’t see it anywhere in the Google Web Fonts site.
crocodile
Thank you for this greate article!And I want to know the result of Richard Fink’s test.
Alan Stearns
SinisterKid,
For Google fonts, the rule I used came from following the link href in the “Add this code to your website” part of their UI. If you follow the link in IE, you get the most cross-browser @font-face rule that service provides.
SinisterKid
Thank you! Got it. Thanks for the help and the article, very educational.
Paul Geronca
Great suggestion, but the overall result of these new best practices is the increased workload for the type foundries and designers, who must now create additional styles (bold, italic, etc) for their digital fonts. Most of the trendy new design fonts only have a single variant to begin with.
justincaron
I wasn’t aware of this as a problem with web design fonts. Now i know that i need to be more selective in the family fonts i chose, and whether or not i choose to bold them.
Makes perfect sense though; and your article outlines very clearly all the relevant key points.
Great article!
citizencontact
It is so true that HTML editors, unlike more publish oriented software, often ignores the type and font designations. It was common, and still is, to have multiple font choices for the browser to pick from. Since until recently, browsers and/or the OS stored fonts, and the web page authors could only guess on what fonts would be served by the various browsers, pretending to have any control was nearly useless.
Finally, with HTML5/CSS3 compliant browsers, we finally can truly start to deal with typefaces, fonts, if not kerning, etc. And since the HTML editors within a CMS often cannot handle the uses of bold and italic and standard HTML style elements like H1…H5, or keep them from overlapping, this leaves it difficult to compensate.
Better web site publishing that integrates tightly controlled styles and CSS with the system to edit content is needed. And, since some browsers cannot handle this, old browsers will still cause problems, it is important to still use “serif” etc.
Also, since semantic understanding is the reason for styles, use of bold, cite, H1, italics, strong, and the rest, must continue to be present, so do not let style settings undo understanding.
By the way, this problem of worrying about fonts on web pages is a beautiful problem to have (pun intended). How to present content in as clear a way possible is the whole point. Now if we can better address printing web pages …
Daniel Bennett
Katie Gray
Well! thanks for informative article. I am working for Minneapolis Web Design firm now. I could easily have provided a bold version of the font for the headings but all that would have done is add bloat to the byte count and it wouldn’t have added one whit to the substance of what was being communicated. So question number one is: are you against letting the browser handle the bolding and italicizing in all instances?