<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Icons, pictograms, or glorified rebuses?</title>
	<atom:link href="http://blog.cocoia.com/2008/02/09/icons-pictograms-or-glorified-rebuses/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.cocoia.com/2008/02/09/icons-pictograms-or-glorified-rebuses/</link>
	<description>The Cocoia Blog is the website of Sebastiaan de With, a Dutch Icon and Interface designer.</description>
	<pubDate>Fri, 29 Aug 2008 03:52:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Matt Penrose</title>
		<link>http://blog.cocoia.com/2008/02/09/icons-pictograms-or-glorified-rebuses/#comment-167993</link>
		<dc:creator>Matt Penrose</dc:creator>
		<pubDate>Wed, 27 Feb 2008 23:30:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cocoia.com/2008/02/09/icons-pictograms-or-glorified-rebuses/#comment-167993</guid>
		<description>I've been thinking about this whilst reading, i am yet to read Khoi's piece, but to me an icon or logo should serve a different purpose to a pictogram.

Pictograms convey information quickly, visually, and multi-linguistically. Take the airport signs above, they show a plane landing and taking off.

However and icon or logo is a piece of branding which should invoke the feel of something, along with it's function or heritage. Just looking at my dock i still get confused whether i need a feather (photoshop), butterfly (in-design) or flower (illustrator)...as a student i cannot afford the hardware needed for CS3 but i know them well and they do look quite nice all lined up but still something a little more imaginative would have been nice.

thanks for such and interesting article, i'll bookmark this blog for future referenece</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been thinking about this whilst reading, i am yet to read Khoi&#8217;s piece, but to me an icon or logo should serve a different purpose to a pictogram.</p>
<p>Pictograms convey information quickly, visually, and multi-linguistically. Take the airport signs above, they show a plane landing and taking off.</p>
<p>However and icon or logo is a piece of branding which should invoke the feel of something, along with it&#8217;s function or heritage. Just looking at my dock i still get confused whether i need a feather (photoshop), butterfly (in-design) or flower (illustrator)&#8230;as a student i cannot afford the hardware needed for CS3 but i know them well and they do look quite nice all lined up but still something a little more imaginative would have been nice.</p>
<p>thanks for such and interesting article, i&#8217;ll bookmark this blog for future referenece</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reinier</title>
		<link>http://blog.cocoia.com/2008/02/09/icons-pictograms-or-glorified-rebuses/#comment-156242</link>
		<dc:creator>Reinier</dc:creator>
		<pubDate>Tue, 12 Feb 2008 21:02:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cocoia.com/2008/02/09/icons-pictograms-or-glorified-rebuses/#comment-156242</guid>
		<description>Great post and comment guys! In my opinion today's application icons serve both identification and branding purposes, whereas the classic pictogram (like Mijksenaar's for Schiphol Airport shown above) excludes the branding function.</description>
		<content:encoded><![CDATA[<p>Great post and comment guys! In my opinion today&#8217;s application icons serve both identification and branding purposes, whereas the classic pictogram (like Mijksenaar&#8217;s for Schiphol Airport shown above) excludes the branding function.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gedeon Maheux</title>
		<link>http://blog.cocoia.com/2008/02/09/icons-pictograms-or-glorified-rebuses/#comment-152625</link>
		<dc:creator>Gedeon Maheux</dc:creator>
		<pubDate>Sat, 09 Feb 2008 14:19:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cocoia.com/2008/02/09/icons-pictograms-or-glorified-rebuses/#comment-152625</guid>
		<description>&lt;p&gt;Nice piece Sebastiaan. I agree with you that Khoi's dream of a 100% pictogram world is both impractical and actually unwanted. The answer for this is more simple that you or he realize... the client.&lt;/p&gt;
&lt;br /&gt;&lt;br /&gt;
&lt;p&gt;Clients don't generally want their product's icons to be represented by abstract lines, shapes and symbols 90% of the time. For better or worse, thanks to the likes of Microsoft and Apple, they want shiny, realistic, highly literal images of every day objects. As icon designers, we can sometimes steer them in other directions, but as they say in the food industry "the customer is always right".&lt;/p&gt;
&lt;br /&gt;&lt;br /&gt;
&lt;p&gt;But this isn't necessarily a bad thing either. Sometimes a happy medium can be reached I think. Take on of my favorite icons we've done to date: Coda. &lt;a href="http://iconfactory.com/design/detail/coda" rel="nofollow"&gt;The Coda icon&lt;/a&gt; is in fact a real-world object, that of a leaf. But that object bears no actual relation to the software functions of the program it represents. It is meant as a symbol of growth and creation of the underlying functions of Coda and I think it works well for exactly that reason. Also, it is visually simple and almost serves as one of Khoi's pictograms he speaks of. In my mind it is the essence of what an icon should be. A simple picture that represents something much more complex that the user can quickly and easily associate by sight.&lt;/p&gt;
&lt;br /&gt;&lt;br /&gt;
&lt;p&gt;Sitting in the OS X dock, once you know what it is, Coda is one of the most easily recognizable and quickly spotted icons anywhere. It's color, shape and rendering all contribute to this, and I give Panic heaps of credit for letting us go in this direction when we designed it. If all clients were as open to ideas as they were, computer desktops would be a much better place.&lt;/p&gt;&lt;br /&gt;</description>
		<content:encoded><![CDATA[<p>Nice piece Sebastiaan. I agree with you that Khoi&#8217;s dream of a 100% pictogram world is both impractical and actually unwanted. The answer for this is more simple that you or he realize&#8230; the client.</p>
<p>Clients don&#8217;t generally want their product&#8217;s icons to be represented by abstract lines, shapes and symbols 90% of the time. For better or worse, thanks to the likes of Microsoft and Apple, they want shiny, realistic, highly literal images of every day objects. As icon designers, we can sometimes steer them in other directions, but as they say in the food industry &#8220;the customer is always right&#8221;.</p>
<p>But this isn&#8217;t necessarily a bad thing either. Sometimes a happy medium can be reached I think. Take on of my favorite icons we&#8217;ve done to date: Coda. <a href="http://iconfactory.com/design/detail/coda" rel="nofollow">The Coda icon</a> is in fact a real-world object, that of a leaf. But that object bears no actual relation to the software functions of the program it represents. It is meant as a symbol of growth and creation of the underlying functions of Coda and I think it works well for exactly that reason. Also, it is visually simple and almost serves as one of Khoi&#8217;s pictograms he speaks of. In my mind it is the essence of what an icon should be. A simple picture that represents something much more complex that the user can quickly and easily associate by sight.</p>
<p>Sitting in the OS X dock, once you know what it is, Coda is one of the most easily recognizable and quickly spotted icons anywhere. It&#8217;s color, shape and rendering all contribute to this, and I give Panic heaps of credit for letting us go in this direction when we designed it. If all clients were as open to ideas as they were, computer desktops would be a much better place.</p>
<p></p>
]]></content:encoded>
	</item>
</channel>
</rss>
