What this is actually saying is don't use Garamond for copy text as its not designed for current DPI's that are currently used on monitors. It doesn't mean you can't use it for titles or headings or devices with a high DPI.
What does Garamond look like on an iphone 4?
Design For Hackers: Why You Don't Use Garamond on The Web
51–60 of 70 posts
Re: Design For Hackers: Why You Don't Use Garamond on The Web
#52Earlier quoted context omitted.
I would very much like a simple cheat-sheet of "standard" fonts and what range of sizes each looks best at with regards to webpages. Something that I can blindly follow when making the first draft of a site. Anyone want to share a link to such a thing?
http://www.typetester.org is a great resource for making comparisons. But I will try to put together a simple list of standard fonts and how to optimize them for the best results. Will shoot you an email when it's done.
Re: Design For Hackers: Why You Don't Use Garamond on The Web
#53Earlier quoted context omitted.
If you know your target's DPI, that doesn't sound to me like "the web."
[deleted]
For an example of viewport CSS, take a look at http://news.ycombinator.com/item?id=1377241
Re: Design For Hackers: Why You Don't Use Garamond on The Web
#54Earlier quoted context omitted.
Although it might be a creative way to promote your panel, it earned a downvote. Just don't think it's the appropriate place to promote it.
Can you explain that further? Here's my logic: if you're in the comments on this thread, you're presumably interested in this topic, and would like to learn more about it -> Many HNers go to SXSW, and would get a chance to learn more, should my panel be accepted -> I'm not famous, so getting help from interested people is my only chance at getting a panel accepted.
Edit: that sounds snarky. It's not intended to be, but just an explanation of why I downvoted. I can appreciate your later comment, but when I made my reply to your original comment, yours was the only other comment in the submission. It seemed tacky.
Re: Design For Hackers: Why You Don't Use Garamond on The Web
#55Earlier quoted context omitted.
I would very much like a simple cheat-sheet of "standard" fonts and what range of sizes each looks best at with regards to webpages. Something that I can blindly follow when making the first draft of a site. Anyone want to share a link to such a thing?
http://www.typetester.org is a great resource for making comparisons. But I will try to put together a simple list of standard fonts and how to optimize them for the best results. Will shoot you an email when it's done.
Re: Design For Hackers: Why You Don't Use Garamond on The Web
#56Earlier quoted context omitted.
Actually its 10 points (at least so it's defined in the CSS). But I wouldn't like to read any longer passages in this font size, and sometimes I zoom in even here to read more comfortably. But 12pt seems actually quite comfortable now that I tried it, so the part about it being too small can be redacted. But the main point was that I strongly disagree defining font sizes in pixels. What happens when somebody with 250…
Note that a px is not the same thing as a pixel. On a 250 PPI display 1 px probably equals 2 pixels. http://webkit.org/blog/55/high-dpi-web-sites/
Re: Design For Hackers: Why You Don't Use Garamond on The Web
#57Re: Design For Hackers: Why You Don't Use Garamond on The Web
#58Earlier quoted context omitted.
Can you explain that further? Here's my logic: if you're in the comments on this thread, you're presumably interested in this topic, and would like to learn more about it -> Many HNers go to SXSW, and would get a chance to learn more, should my panel be accepted -> I'm not famous, so getting help from interested people is my only chance at getting a panel accepted.
Here's my logic: if you read the post, you already saw the plug (on the post). Edit: that sounds snarky. It's not intended to be, but just an explanation of why I downvoted. I can appreciate your later comment, but when I made my reply to your original comment, yours was the only other comment in the submission. It seemed tacky.
Re: Design For Hackers: Why You Don't Use Garamond on The Web
#59Earlier quoted context omitted.
Actually its 10 points (at least so it's defined in the CSS). But I wouldn't like to read any longer passages in this font size, and sometimes I zoom in even here to read more comfortably. But 12pt seems actually quite comfortable now that I tried it, so the part about it being too small can be redacted. But the main point was that I strongly disagree defining font sizes in pixels. What happens when somebody with 250…
Note that a px is not the same thing as a pixel. On a 250 PPI display 1 px probably equals 2 pixels. http://webkit.org/blog/55/high-dpi-web-sites/
Re: Design For Hackers: Why You Don't Use Garamond on The Web
#60Earlier quoted context omitted.
Note that a px is not the same thing as a pixel. On a 250 PPI display 1 px probably equals 2 pixels. http://webkit.org/blog/55/high-dpi-web-sites/
This just makes me angry. The whole point of being able to specify in px was to have something that is actually specific to the device's pixels---otherwise you'd use points or inches or cm---for those rare instances where the pixel count is actually relevant. Of course, it got overused, but the answer should not be to just redefine "pixel" as "something a bit smaller than a point" (except in a bit more detail)! Argh.