Debbie, On Dec 31, 2005, at 8:10 PM, Iorhael wrote:
>> David Laakso wrote: >> >>> Iorhael wrote: >> >>>> http://www.drk-writing.com/3columnlayout/ >> >>> Either way, setting: >>> body { font: 100.01%/1.2 'Lucida Grande', 'Nimbus Sans', 'Luxi Sans', >>> Arial, sans-serif; } >>> and deleting *each and everyone* of those font-families, pixel >>> font-sizes, pixel line-heights, replacing justify /with/ left, and >>> changing the headers to percent for font-size-- just *starts* to >>> approach something readable(and zoomable cross-browser). >> >> http://mrmazda.no-ip.com/SS/iorhael1.jpg >> >> Debbie, everything David said, particularly px line-heights. Except, >> better yet, don't set any font-family on the body. Limit your family >> styles to headings and menus so that the main content text can work >> best >> for me and your other visitors. We already picked the size and family >> that works best for us. If you insist on making your page difficult >> overriding our carefully chosen defaults, we'll just do as many others >> do. Instead of zooming or squinting, we'll just hit the back button >> without giving your site any chance to do whatever is is you want it >> to >> do. >> >> Browser makers provide users with a preference adjustment precisely so >> that they can optimize to the size that best suits them. Your visitors >> don't appreciate web artists arbitrarily reducing text size to >> anything >> smaller than their choice, particularly those using web browsers with >> no >> zoom function that works on sites like yours that set text sizes and >> line heights in itty bitty px. Instead, defer to what your users >> prefer, >> leaving your content's P text unsized, or reinforcing it with an >> explicit font-size: medium. Too small text is the #1 complaint from >> web >> users: http://www.useit.com/alertbox/designmistakes.html I'm a little confused about who said what in this regard, but I can tell you David is good at color and typography, so I trust his judgment on these issues. Also, the list admins work hard at avoiding the 'font wars', so I highly recommend checking out the wiki on this topic. Given those caveats, I'll try to answer your questions. > Okay, are you both saying that I shouldn't be using font families in my > style sheets at all? I've been setting fonts the way I learned in my > two > online CSS classes. So reading these messages is a total surprise. I would doubt that they are saying that. Here are my 'rules of thumb' for font issues. 1. For efficiency's sake declare it on the body and let it inherit through to the rest of the elements on the page. If an element needs a different font family, declare it in a selector for that element only. 2. Set the size to 100% so the user's default size choice is the baseline (using 100.01% gets around some order browser rounding errors). 3. Prefer flexible units like em or % for screen (keywords work ok too as long as you account for ie5). 4. The user is in total control and can override all your font settings at will. Keep in mind that there are multiple valid way to work with font issues. Every method has strengths and weaknesses. Thats why there are 'font wars'. The wiki is your friend. I go there first when I have a question because the answers are almost always there. Roger, Roger Roelofs "Remember, if you’re headed in the wrong direction, God allows U-turns!" ~Allison Gappa Bottke ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
