<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Linden LAN &#187; Typography</title>
	<atom:link href="http://www.lindenlan.net/tag/typography/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lindenlan.net</link>
	<description></description>
	<lastBuildDate>Sat, 29 Nov 2014 04:54:20 +0000</lastBuildDate>
	<language>en-US</language>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>On “Modern CSS Typography and Font Styling Examples”</title>
		<link>http://www.lindenlan.net/2010/01/21/on-modern-css-typography-and-font-styling-examples/</link>
		<comments>http://www.lindenlan.net/2010/01/21/on-modern-css-typography-and-font-styling-examples/#comments</comments>
		<pubDate>Thu, 21 Jan 2010 14:28:36 +0000</pubDate>
		<dc:creator><![CDATA[Brian]]></dc:creator>
				<category><![CDATA[Software]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Typography]]></category>

		<guid isPermaLink="false">http://www.lindenlan.net/?p=367</guid>
		<description><![CDATA[I read an article titled, “Modern CSS Typography and Font Styling Examples”, and though mistakes and omissions weren’t major, I felt compelled to comment on them. My comment got so long, I figured a quick blog post would be better than a long-winded comment. Smallcaps is not the same as uppercase. Even if you can [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>I read an article titled, “<a href="http://www.dlocc.com/articles/modern-css-typography-and-font-styling-examples/">Modern CSS Typography and Font Styling Examples</a>”, and though mistakes and omissions weren’t major, I felt compelled to comment on them.  My comment got so long, I figured a quick blog post would be better than a long-winded comment.</p>
<p><span id="more-367"></span></p>
<p>Smallcaps is not the same as uppercase.  Even if you can simulate smallcaps using uppercase letters (similar to simulating italics or bold), fonts that employ smallcaps are specifically created to maintain proper balance and weight.</p>
<p>Furthermore, it’s important to use glyphs as intended with proper formatting.  This is a small detail, but in the CNN example, a double-hyphen is incorrect.  An emdash should be used instead and without the spaces.  Many CMSes and blogging software, WordPress included, are able to convert typographic shorthand like double– and triple-hyphens and convert them to their proper glyphs.  An old but timeless article: <a href="http://www.alistapart.com/articles/typography/">Typography Matters</a> covers this topic.  Also it wouldn’t hurt to look at print style guides such as the Chicago Manual of Style.  </p>
<p>Also not mentioned but useful to know is to make sure that when using justified text (most everything is on the web is flush-left), that it should be used in combination with hyphenation.  See <a href="http://kingdesk.com/projects/wp-typography/">wp-Typography</a> for example.</p>
<p>As for the top-10 list (I disagree that Dreamweaver should be on the list), it’s important that the imagery is consistent.  The Photoshop icon sticks out like a sore thumb.  Also if the list is ordered, it would make sense to provide some way to indicate that it is ordered like numbers.  That sets it apart from an itemized list.</p>
<p>I like Georgia since it is one of the better looking serif fonts among the web core fonts.  However, since this is supposed to be a post about <em>modern</em> typography, the author should have mentioned upcoming font-embedding  technology that would allow the use of much better looking fonts than Georgia.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.lindenlan.net/2010/01/21/on-modern-css-typography-and-font-styling-examples/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic page generated in 0.282 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2026-04-18 21:25:02 -->

<!-- Compression = gzip -->