- 01.28.12
Ambicase Fatface
Stephen Coles: Celebrating its inclusion on this list, Ambicase Fatface is now 30% off at MyFonts.… - 01.28.12
Chartwell
AndrĂ© Mora: I really like Chartwell and have used it for editorial design. I'm impressed by its ingenuity and excited by what it may insp… - 01.27.12
Sutturah
Marian Bantjes: I love this! My highest compliment: envy.… - 01.27.12
Neue Haas Grotesk
Erik Spiekermann: That, Matthew, is why Helvetica was so successful: nobody except a few Swiss & German designers would have ever dared order t… - 01.27.12
Apple Color Emoji
Christoph: You can find a complete overview of all the Apple Color Emoji characters here. (Works only with Safari. Hover to see Unicode … - 01.26.12
Changing
AndrĂ© Mora: I would love to read a 5,000 word review by Paul Shaw on this typeface. Though something tells me he'd only need 5.… - 01.26.12
Our Favorite Typefaces of 2011
Stephen Coles: Jason Santa Maria just posted a nice summary of highlights from the list.… - 01.26.12
Reina
Marian Bantjes: Whoa. Fantastic!… - 01.26.12
My Favorite Font Sources: A Shortlist of Trusted Foundries and Retailers
Josh Farmer: What about Underware and TypeTogether?…
UsableType
UsableType is a new online resource dedicated to issues surrounding ‘typography for the world wide web.’ There’s a good bit there (especially the Style Guide section), and they’re currently featuring the provocative rant, The Battle is Won, about default font sizing on the web. Personally, I’m not sure it’s time to hang the banner on the aircraft carrier, but it’s interesting stuff. Good comment link to the Noodle Incident’s 76% solution.
Tom, could you please tell me what this all means? I do understand that/how text sizes come out different in different platform-browser combinations, but do these articles describe some kind of new trick/breakthrough? Also, is there some kind of consensus about ideal PPEM size, specifically for reading? One thing that at least one person seems to be missing is that we read onscreen at a greater distance than onhand.
hhp
While ‘breakthrough’ is a strong word, these articles describe an approach which I think is worth following. As to your second question first: There has been significant debate in the web designer community around which measure to actually use to specify text size. Through the use of style sheets there are several approaches, none wholely satisfactory to may page layouts. The first factor here is allowing the user to change text sizing, which is now easily done in most browsers, except when text is specified in pixels (PX). Pixels however have been the web designer’s measure of choice, as the more flexible ‘default’ sizings provide too few options, and default very differently in different browser versions. The “76% Solution” is a very well researched approach that creates a new default that is incredibly consistent across major browsers, gives designers options in sizings that they will find attractive, and gives the user the option of adjusting sizing if they see fit. It’s a better approach than what’s commonly used today.
OK, I get it. Man, I sure love the smell of a good hack in the morning.
Question: What about the effect of this on the full-anti-aliased text rendering in OSX – any significance? Does Panther still increment size in steps or continuously?
hhp