<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Train Tickets, Rethought</title>
	<atom:link href="http://www.vestaldesign.com/blog/2007/03/train-tickets-rethought/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.vestaldesign.com/blog/2007/03/train-tickets-rethought/</link>
	<description>A design blog with a particular emphasis on green design, design for society, and environmental technologies, Vestal Design Blog also discusses web design, product design, graphic design, and architecture.</description>
	<lastBuildDate>Tue, 16 Mar 2010 18:51:37 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: akaisha</title>
		<link>http://www.vestaldesign.com/blog/2007/03/train-tickets-rethought/comment-page-1/#comment-34822</link>
		<dc:creator>akaisha</dc:creator>
		<pubDate>Sun, 01 Apr 2007 14:23:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.vestaldesign.com/blog/2007/03/train-tickets-rethought.html#comment-34822</guid>
		<description>yes</description>
		<content:encoded><![CDATA[<p>yes</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Pitman</title>
		<link>http://www.vestaldesign.com/blog/2007/03/train-tickets-rethought/comment-page-1/#comment-30302</link>
		<dc:creator>Dave Pitman</dc:creator>
		<pubDate>Wed, 21 Mar 2007 19:21:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.vestaldesign.com/blog/2007/03/train-tickets-rethought.html#comment-30302</guid>
		<description>Thanks. We actually had that debate about what to do with the dates and came to consensus that since we&#039;re showing the time in the 24hr format (see the project page), it would appropriate to have the date simply follow the same &lt;a href=&quot;http://en.wikipedia.org/wiki/Internationalization_and_localization&quot;  rel=&quot;nofollow&quot;&gt;localization&lt;/a&gt; conventions without explanation. We couldn&#039;t think of a good graphical representation for month/day, and having the first letter M, D (or M, G in Italian) is useless.</description>
		<content:encoded><![CDATA[<p>Thanks. We actually had that debate about what to do with the dates and came to consensus that since we&#8217;re showing the time in the 24hr format (see the project page), it would appropriate to have the date simply follow the same <a href="http://en.wikipedia.org/wiki/Internationalization_and_localization"  rel="nofollow">localization</a> conventions without explanation. We couldn&#8217;t think of a good graphical representation for month/day, and having the first letter M, D (or M, G in Italian) is useless.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Prashant</title>
		<link>http://www.vestaldesign.com/blog/2007/03/train-tickets-rethought/comment-page-1/#comment-30088</link>
		<dc:creator>Prashant</dc:creator>
		<pubDate>Wed, 21 Mar 2007 04:55:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.vestaldesign.com/blog/2007/03/train-tickets-rethought.html#comment-30088</guid>
		<description>This is a very cool design. One issue I can see, though, is the date. It&#039;s not totally language-free since we use MM/DD/YYYY in the U.S., instead of DD/MM/YYYY. Maybe different calendar-based icons could denote which number is the month and which the day.</description>
		<content:encoded><![CDATA[<p>This is a very cool design. One issue I can see, though, is the date. It&#8217;s not totally language-free since we use MM/DD/YYYY in the U.S., instead of DD/MM/YYYY. Maybe different calendar-based icons could denote which number is the month and which the day.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#8230;then the smartest thing to say is nothing &#171; Doobybrain.com</title>
		<link>http://www.vestaldesign.com/blog/2007/03/train-tickets-rethought/comment-page-1/#comment-29059</link>
		<dc:creator>&#8230;then the smartest thing to say is nothing &#171; Doobybrain.com</dc:creator>
		<pubDate>Sat, 17 Mar 2007 03:12:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.vestaldesign.com/blog/2007/03/train-tickets-rethought.html#comment-29059</guid>
		<description>[...] Vestal Design has an interesting look at how train tickets (and probably tickets in general) can be .... I don&#8217;t take the train very often, but I know that tickets for just about anything are as confusing as ever. Take airplane tickets and concert tickets for example. Both kinds of tickets are basically all text, with either zero or very little graphical interpretations. This means that someone would have to take the time out to read, or at least skim over, every line of the ticket before finding out the specific information he/she may want to know (ie: seat number, location, destination, arrival/departure time, etc.). Also, there&#8217;s a good point about the life expectancy of most standard issue tickets: they suck. Paper quality is almost always utter crap and most of the time you can&#8217;t put a ticket in your purse or wallet without having it rip or get folded into a paper airplane. To remedy the situation, Vestal Design has suggested using large graphic icons (universally recognizable or at least interpretable) as well as a color scheme of some sort. Check out the rest of the project to redesign tickets here. [...]</description>
		<content:encoded><![CDATA[<p>[...] Vestal Design has an interesting look at how train tickets (and probably tickets in general) can be &#8230;. I don&#8217;t take the train very often, but I know that tickets for just about anything are as confusing as ever. Take airplane tickets and concert tickets for example. Both kinds of tickets are basically all text, with either zero or very little graphical interpretations. This means that someone would have to take the time out to read, or at least skim over, every line of the ticket before finding out the specific information he/she may want to know (ie: seat number, location, destination, arrival/departure time, etc.). Also, there&#8217;s a good point about the life expectancy of most standard issue tickets: they suck. Paper quality is almost always utter crap and most of the time you can&#8217;t put a ticket in your purse or wallet without having it rip or get folded into a paper airplane. To remedy the situation, Vestal Design has suggested using large graphic icons (universally recognizable or at least interpretable) as well as a color scheme of some sort. Check out the rest of the project to redesign tickets here. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
