{"id":2296,"date":"2011-12-03T14:32:09","date_gmt":"2011-12-03T14:32:09","guid":{"rendered":"http:\/\/sunpig.com\/mt-entry-2296.html"},"modified":"2012-03-27T14:00:47","modified_gmt":"2012-03-27T14:00:47","slug":"styling-the-at-sign-in-din","status":"publish","type":"post","link":"https:\/\/sunpig.com\/martin\/2011\/12\/03\/styling-the-at-sign-in-din\/","title":{"rendered":"Styling the at sign in DIN"},"content":{"rendered":"

FF DIN<\/a> is a fantastic font. It’s clear and authoritative, but with loads of personality. Once you get to know it (thanks Mark<\/a>!), you start seeing it everywhere. It’s particularly delicious for all-caps titling, but it works equally well as a body text font.<\/p>\n

\"The<\/p>\n

The only problem with DIN is the default at sign (@), which looks like ass.<\/p>\n

\"email<\/p>\n

Fortunately, DIN comes with a set of alternate glyphs built in, which you can access through OpenType<\/a>‘s stylistic alternates<\/i> feature. One of those alternate glyphs is a version of the at sign that actually looks like an at sign rather than a half-melted “id” ligature.<\/p>\n

\"email<\/p>\n

You can usually select OpenType stylistic alternates from the advanced font options dialog of your graphics or word processing program. In Pixelmator for OS X, for example, you open up the fonts dialog, click on the tools button, select the “Typography” option, and then choose an alternative stylistic set in the Typography dialog. In Word 2011, you open up the fonts dialog by selecting “Font…” from Format menu; stylistic sets are shown in the “Advanced typography” section of the Advanced tab.<\/p>\n

Unfortunately, although CSS3 includes a font-variant-alternates<\/a><\/code> property with which you can select alternate glyphs, there aren’t any browsers that support this yet. Bummer. So if you want to use DIN on the web, you’re either stuck with the ass-at, or you have to use a workaround.<\/p>\n

One way is to wrap at signs in a <span><\/code>, so you can set their style explicitly, as suggested by Dan Cedarholm in his article Use the Best Available Ampersand<\/a>.<\/p>\n

monkey<span class=\"awesomat\">@<\/span>example.com<\/code><\/pre>\n
But Drew McLellan’s<\/a> article Creating Custom Font Stacks with Unicode-Range<\/a> in this year’s 24 Ways<\/a> advent calendar suggests an intriguing potential alternative. The concept is that the @font-face<\/code> rule allows you to select which unicode characters the webfont will be used for by setting the unicode-range<\/code> property. Single out the ampersand (U+0026) or the at sign (U+0040) for special treatment, and Bob’s your uncle.<\/p>\n
The difference is that for awesompersands you are trying to add<\/em> a font for a single character, whereas for DIN awesomats, I want to remove<\/em> font styling for a single character. The unicode-range<\/code> property obliges nicely here, because it accepts multiple ranges:<\/p>\n
@font-face {\n  font-family: 'dinregular';\n  url('font\/DINWeb.woff') format('woff');\n  unicode-range:U+0-3F,U+41-10FFFF; \/* Everything but the @ *\/\n}<\/code><\/pre>\n
Browsers that don’t handle unicode-range<\/code> will ignore it, and fall back to showing DIN for all characters, even the @. Which is fine.<\/p>\n
In terms of typography, however, the drawback of this technique is that the plain font to be used for the U+40 unicode character may have a different x-height<\/a> than the DIN of the surrounding text, so the at sign may look out of place — too large or too small. And the @font-face<\/code> rule doesn’t allow a font-size<\/code> property inside it, so you can’t tweak the font sizes to match each other. Hmm.<\/p>\n
On balance, I think I’ll stick to wrapping my DIN at signs in a <span><\/code> until font-variant-alternates<\/code> appears, but it’s a nifty technique to be aware of.<\/p>\n","protected":false},"excerpt":{"rendered":"
FF DIN is a fantastic font. It’s clear and authoritative, but with loads of personality. Once you get to know it (thanks Mark!), you start seeing it everywhere. It’s particularly delicious for all-caps titling, but it works equally well as a body text font. The only problem with DIN is the default at sign (@), … <\/p>\n
Continue reading “Styling the at sign in DIN”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[],"class_list":["post-2296","post","type-post","status-publish","format-standard","hentry"],"_links":{"self":[{"href":"https:\/\/sunpig.com\/martin\/wp-json\/wp\/v2\/posts\/2296","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sunpig.com\/martin\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sunpig.com\/martin\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sunpig.com\/martin\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/sunpig.com\/martin\/wp-json\/wp\/v2\/comments?post=2296"}],"version-history":[{"count":0,"href":"https:\/\/sunpig.com\/martin\/wp-json\/wp\/v2\/posts\/2296\/revisions"}],"wp:attachment":[{"href":"https:\/\/sunpig.com\/martin\/wp-json\/wp\/v2\/media?parent=2296"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sunpig.com\/martin\/wp-json\/wp\/v2\/categories?post=2296"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sunpig.com\/martin\/wp-json\/wp\/v2\/tags?post=2296"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}