<?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: Planning Ahead</title>
	<atom:link href="http://www.hiwiller.com/2008/11/11/planning-ahead/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hiwiller.com/2008/11/11/planning-ahead/</link>
	<description>Zack Hiwiller&#039;s Blog on Game Design and The Industry</description>
	<lastBuildDate>Tue, 31 Aug 2010 12:48:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Bryan</title>
		<link>http://www.hiwiller.com/2008/11/11/planning-ahead/comment-page-1/#comment-430</link>
		<dc:creator>Bryan</dc:creator>
		<pubDate>Tue, 11 Nov 2008 23:17:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.hiwiller.com/?p=280#comment-430</guid>
		<description>Your screen has plenty of space there too, so that&#039;s not an issue.  What we tend to do in space-limited situations is provide enough space for what the &quot;normal&quot; use case, and then squish it horizontally if someone decides to put in a name of &quot;WWWWWWWWWWWWWWWMW&quot; or something stupid like that.  It can become somewhat unreadable in extreme cases on standard-def displays, but if you can&#039;t read your own player&#039;s name because the characters are too wide, then it&#039;s your own fault.

But because the band and the song title are both 16 characters then I&#039;m guessing they simply limit it to 32 bytes of PAD (http://en.wikipedia.org/wiki/Program-associated_data) per song.  The only thing I can think of to make this sort of acceptable is that they have to broadcast enough information for all of the channels and songs playing all of the time, so that a receiver turned on at any point can get it.  But I, for one, wouldn&#039;t mind waiting a few more seconds in order to see the entirety of a song&#039;s name.</description>
		<content:encoded><![CDATA[<p>Your screen has plenty of space there too, so that&#8217;s not an issue.  What we tend to do in space-limited situations is provide enough space for what the &#8220;normal&#8221; use case, and then squish it horizontally if someone decides to put in a name of &#8220;WWWWWWWWWWWWWWWMW&#8221; or something stupid like that.  It can become somewhat unreadable in extreme cases on standard-def displays, but if you can&#8217;t read your own player&#8217;s name because the characters are too wide, then it&#8217;s your own fault.</p>
<p>But because the band and the song title are both 16 characters then I&#8217;m guessing they simply limit it to 32 bytes of PAD (<a href="http://en.wikipedia.org/wiki/Program-associated_data" rel="nofollow">http://en.wikipedia.org/wiki/Program-associated_data</a>) per song.  The only thing I can think of to make this sort of acceptable is that they have to broadcast enough information for all of the channels and songs playing all of the time, so that a receiver turned on at any point can get it.  But I, for one, wouldn&#8217;t mind waiting a few more seconds in order to see the entirety of a song&#8217;s name.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
