On Fri, Oct 17, 2008 at 10:32 PM, Jan Poulsen <[EMAIL PROTECTED]> wrote:
> Helvetica is one of the main reasons that Blueprint is a beautiful
> framework. When you use Helvetica it kind of lends its aesthetics to
> your work.

Helvetica, in 12px  size on computer screen doesn't have much to do
with aesthetics.
Usually it wont even be aliased and it will just look bad. Remember
this is not print design we are talking about.

As for Verdana, it would require (imho) more then 18px line-height. It
is very tall type and i don't like the way it looks with Blueprints
vertical rhythm implementation.

I don't really care if Arial is rip off Helvetica or not (and I'm sure
it is), but it's widely available and it is designed with computer
screen in mind (and Helvetica isn't).
And it doesn't seem to interfere with Blueprint's grid.

Bottom line, I see Helvetica as something you will remove from
screen.css as soon as you see how bad it looks like. If framework is
used to cut down on repetitive work, why should you always go out of
your way to remove (or just move) Helvetica from body element?

Maybe there is a just cause for putting it in base typography, but i
just don't see the use of it on the web and Arial will mostly be the
first thing you'll reach for in web design (other then Verdana or
Helvetica Neue if you insist).

Of course this is just my opinion. I am not trying to troll about how
Helvetica is bad, i just want find out is there a valid reason to use
it.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Blueprint CSS" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/blueprintcss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to