A presentation for Carsonified by Sean Gaffney and Matthew Smith.
A presentation for Carsonified by Sean Gaffney and Matthew Smith.
Uploaded via SlideShare as Adobe PDF
© All Rights Reserved
lasanthabuddhika
4 months ago
Cristina_Blanaru
5 months ago
angeldp
6 months ago
Subhash Azhikodan at iBizSoft Inc
9 months ago
Winston 1982, Graphic Designer/ Web Designer / Student
11 months ago
Vinicius Nenartavis, Criação at Agencia de Comunicação Marca d’ Água
1 year ago
parthium
1 year ago
Mohammed Arif, Manager, Interactive Development at SapientNitro
1 year ago
Liudas Ka
1 year ago
Masakazu Shin-ya at 株式会社アイフリーク
1 year ago
Web Typography with CSS3
--
Q: Are there any notable effects on performance when implementing @fontface for larger portions of text? (regardless of design issues of course)
A: Once the file is loaded into the browser’s cache, it performs just as well as if the font were local to the visitor’s machine. Neither sIFR, FIR, Cufon, nor any other javascript technique can claim anything near that performance-wise.
Q: How does one achieve the best typography without hyphenation and justification?
A: Justification of text is available via the CSS ’text-align’ property, which is from the CSS1 spec and supported by all major browsers. Just set it to ’justify’ and you’re good to go. Granted, it’s not the sophisicated justification we get from something like InDesign (where letterspacing is also affected), but it works. Hyphenation is a different story. It’s in the CSS3 Text module spec, but it’s not been implemented by any browser manufacturers that I’m aware. Check out this link: http://www.w3.org/TR/css3-text/#hyphenate. There is, however, what’s called the ’soft hyphen’. You can include this HTML entity in your word ’shy;’ (preceded with an ampersand) and the word will break with a hyphen where you’ve included that entity IF the containing element’s width gets in the way. No, it’s not separated from markup, which makes it a pain to use, but it is the tool we currently have. :)
Q: Do the rendering issues on Windows also affect EOT files?
A: Yep. EOT is just the format of the font file, which is specific to IE. You can deliver a WOFF to Firefox on Windows and still have the same rendering problems, which are a result of a) the font’s hinting and b) the rendering engine used to display the type by Windows. Check out this article for more information: http://www.thomasphinney.com/2009/12/browser-choice-vs-font-rendering/
Q: If you have three font file formats declared like the last screen (where they actually had three font file types for the same font to make sure all browsers are covered), will your browser and load time be effected as it tries to load all the supported formats?
A: Nope, as long as you’ve provided the correct syntax, the browser will go down the list until it finds a format that it recognizes, then download it and ignore the rest. 3 years ago