<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: A Handy Tip for Publicists</title>
	<atom:link href="http://whatever.scalzi.com/2009/07/10/a-handy-tip-for-publicists/feed/" rel="self" type="application/rss+xml" />
	<link>http://whatever.scalzi.com/2009/07/10/a-handy-tip-for-publicists/</link>
	<description>I FORGET WHAT EIGHT WAS FOR</description>
	<lastBuildDate>Fri, 10 Feb 2012 00:36:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: gottacook</title>
		<link>http://whatever.scalzi.com/2009/07/10/a-handy-tip-for-publicists/#comment-154444</link>
		<dc:creator><![CDATA[gottacook]]></dc:creator>
		<pubDate>Mon, 13 Jul 2009 20:27:11 +0000</pubDate>
		<guid isPermaLink="false">http://whatever.scalzi.com/?p=7919#comment-154444</guid>
		<description><![CDATA[Anyone finding this topic of interest will enjoy (if they haven&#039;t read it already) the story &quot;Babel II&quot; by Damon Knight.]]></description>
		<content:encoded><![CDATA[<p>Anyone finding this topic of interest will enjoy (if they haven&#8217;t read it already) the story &#8220;Babel II&#8221; by Damon Knight.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Spocko</title>
		<link>http://whatever.scalzi.com/2009/07/10/a-handy-tip-for-publicists/#comment-154327</link>
		<dc:creator><![CDATA[Spocko]]></dc:creator>
		<pubDate>Sun, 12 Jul 2009 19:31:20 +0000</pubDate>
		<guid isPermaLink="false">http://whatever.scalzi.com/?p=7919#comment-154327</guid>
		<description><![CDATA[What is the purpose of the release? To get people to notice and write about the product or service and then to buy it. 

It worked. I&#039;d expect more of this stuff. 

It&#039;s unusual, you noticed. In the dot.com days you would see stuff like this for new product launches.  I remember PR people sending fake hand grenades, &quot;the product is explosive!&quot;
chocolate shaped stuff and reversed product press releases. &quot;don&#039;t go backwards with your security!&quot;

The brilliant move here is it looks like an accident. This allows people to &quot;fix&quot; the problem.  Of course this is what I would tell the client if he called to complain. &quot;Did Scalzi blog about it? Did Charlie Stross trouble shoot it? Did the core IT/SF audience spend time in &quot;Mr Fix-it&quot; mode? Yes,Yes,and yes.  And they will be reminded of how great Silverburg is as a writer.  If I has sent out a standard release the audience could engage their superior feelings about grammer, printer drivers, PDF&#039;s and the correct spelling of famous SF writers.&quot;

The problem withthis strategy is that instead of people understanding your brilliance they think you just messed up. You should really tell the client first. &quot;This will look like an error, but it will engage the audiences&#039; puzzle solving skills and pull them into the story. But don&#039;t tell them I did it on purpose. Just pretend I&#039;m the dumbest person in the room and could the stories and watch the sales re in because of the &quot;stupid&quot; PR person.&quot;

Acting stupid is hard to do for people with big egos but if it works for you, use it.]]></description>
		<content:encoded><![CDATA[<p>What is the purpose of the release? To get people to notice and write about the product or service and then to buy it. </p>
<p>It worked. I&#8217;d expect more of this stuff. </p>
<p>It&#8217;s unusual, you noticed. In the dot.com days you would see stuff like this for new product launches.  I remember PR people sending fake hand grenades, &#8220;the product is explosive!&#8221;<br />
chocolate shaped stuff and reversed product press releases. &#8220;don&#8217;t go backwards with your security!&#8221;</p>
<p>The brilliant move here is it looks like an accident. This allows people to &#8220;fix&#8221; the problem.  Of course this is what I would tell the client if he called to complain. &#8220;Did Scalzi blog about it? Did Charlie Stross trouble shoot it? Did the core IT/SF audience spend time in &#8220;Mr Fix-it&#8221; mode? Yes,Yes,and yes.  And they will be reminded of how great Silverburg is as a writer.  If I has sent out a standard release the audience could engage their superior feelings about grammer, printer drivers, PDF&#8217;s and the correct spelling of famous SF writers.&#8221;</p>
<p>The problem withthis strategy is that instead of people understanding your brilliance they think you just messed up. You should really tell the client first. &#8220;This will look like an error, but it will engage the audiences&#8217; puzzle solving skills and pull them into the story. But don&#8217;t tell them I did it on purpose. Just pretend I&#8217;m the dumbest person in the room and could the stories and watch the sales re in because of the &#8220;stupid&#8221; PR person.&#8221;</p>
<p>Acting stupid is hard to do for people with big egos but if it works for you, use it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tangurena</title>
		<link>http://whatever.scalzi.com/2009/07/10/a-handy-tip-for-publicists/#comment-154269</link>
		<dc:creator><![CDATA[Tangurena]]></dc:creator>
		<pubDate>Sun, 12 Jul 2009 17:01:50 +0000</pubDate>
		<guid isPermaLink="false">http://whatever.scalzi.com/?p=7919#comment-154269</guid>
		<description><![CDATA[@ GWH, 19, sadly, it appears that the tentacled ones are coming whether we think the time is right or not:  
http://www.pinktentacle.com/2009/07/japan-fears-massive-jellyfish-invasion-this-year/]]></description>
		<content:encoded><![CDATA[<p>@ GWH, 19, sadly, it appears that the tentacled ones are coming whether we think the time is right or not:<br />
<a href="http://www.pinktentacle.com/2009/07/japan-fears-massive-jellyfish-invasion-this-year/" rel="nofollow">http://www.pinktentacle.com/2009/07/japan-fears-massive-jellyfish-invasion-this-year/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: allium</title>
		<link>http://whatever.scalzi.com/2009/07/10/a-handy-tip-for-publicists/#comment-154248</link>
		<dc:creator><![CDATA[allium]]></dc:creator>
		<pubDate>Sun, 12 Jul 2009 16:13:04 +0000</pubDate>
		<guid isPermaLink="false">http://whatever.scalzi.com/?p=7919#comment-154248</guid>
		<description><![CDATA[(looks closer)

&quot;I...prepared...Explosive Runes...this...mor...&quot;

(white flash)]]></description>
		<content:encoded><![CDATA[<p>(looks closer)</p>
<p>&#8220;I&#8230;prepared&#8230;Explosive Runes&#8230;this&#8230;mor&#8230;&#8221;</p>
<p>(white flash)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig Ranapia</title>
		<link>http://whatever.scalzi.com/2009/07/10/a-handy-tip-for-publicists/#comment-154233</link>
		<dc:creator><![CDATA[Craig Ranapia]]></dc:creator>
		<pubDate>Sun, 12 Jul 2009 07:41:04 +0000</pubDate>
		<guid isPermaLink="false">http://whatever.scalzi.com/?p=7919#comment-154233</guid>
		<description><![CDATA[Meanwhile, if I was a book page editor or buyer for an indie bookstore (yes, Virginia, they&#039;re not totally extinct) having that pile of shit land in my inbox would just guarantee it being dispatched straight back into the ether and my interest in the title being pimped remaining at zero.

Epic fail is how the kids put it, I believe.]]></description>
		<content:encoded><![CDATA[<p>Meanwhile, if I was a book page editor or buyer for an indie bookstore (yes, Virginia, they&#8217;re not totally extinct) having that pile of shit land in my inbox would just guarantee it being dispatched straight back into the ether and my interest in the title being pimped remaining at zero.</p>
<p>Epic fail is how the kids put it, I believe.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joel Polowin</title>
		<link>http://whatever.scalzi.com/2009/07/10/a-handy-tip-for-publicists/#comment-154228</link>
		<dc:creator><![CDATA[Joel Polowin]]></dc:creator>
		<pubDate>Sun, 12 Jul 2009 05:38:19 +0000</pubDate>
		<guid isPermaLink="false">http://whatever.scalzi.com/?p=7919#comment-154228</guid>
		<description><![CDATA[Paragraph 3 starts out with something like &quot;Some of Silverberg&#039;s taken for granted.&quot;  Near the bottom, the &quot;JTCO&quot; line is an ISBN; the next line is &quot;Publication date: June 2009&quot; and &quot;Distributed by IPG&quot;, I think.  Then &quot;Contact nonstop&quot;, &quot;nonstop press&quot;.

I don&#039;t think I&#039;ll try to parse any more of it.  But I&#039;m sure that Dave has identified the cause.]]></description>
		<content:encoded><![CDATA[<p>Paragraph 3 starts out with something like &#8220;Some of Silverberg&#8217;s taken for granted.&#8221;  Near the bottom, the &#8220;JTCO&#8221; line is an ISBN; the next line is &#8220;Publication date: June 2009&#8243; and &#8220;Distributed by IPG&#8221;, I think.  Then &#8220;Contact nonstop&#8221;, &#8220;nonstop press&#8221;.</p>
<p>I don&#8217;t think I&#8217;ll try to parse any more of it.  But I&#8217;m sure that Dave has identified the cause.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clay</title>
		<link>http://whatever.scalzi.com/2009/07/10/a-handy-tip-for-publicists/#comment-154201</link>
		<dc:creator><![CDATA[Clay]]></dc:creator>
		<pubDate>Sun, 12 Jul 2009 00:19:12 +0000</pubDate>
		<guid isPermaLink="false">http://whatever.scalzi.com/?p=7919#comment-154201</guid>
		<description><![CDATA[This is funny/sad to me. Tanguarena&#039;s assessment is pretty much right on. I&#039;ve encountered the same problem many times when my users attempt to print-to-fax a PDF containing a font that&#039;s not available on the system. The process converting the PDF to a TIF file for faxing dutifully does so, without regard to what the text actually looks like. 

Potential vendors call back confused, asking why their signup form was gibberish. 

It&#039;s somewhat of a relief to see it plagues others as well. 

ok, enough IT bloviation.]]></description>
		<content:encoded><![CDATA[<p>This is funny/sad to me. Tanguarena&#8217;s assessment is pretty much right on. I&#8217;ve encountered the same problem many times when my users attempt to print-to-fax a PDF containing a font that&#8217;s not available on the system. The process converting the PDF to a TIF file for faxing dutifully does so, without regard to what the text actually looks like. </p>
<p>Potential vendors call back confused, asking why their signup form was gibberish. </p>
<p>It&#8217;s somewhat of a relief to see it plagues others as well. </p>
<p>ok, enough IT bloviation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joel Polowin</title>
		<link>http://whatever.scalzi.com/2009/07/10/a-handy-tip-for-publicists/#comment-154179</link>
		<dc:creator><![CDATA[Joel Polowin]]></dc:creator>
		<pubDate>Sat, 11 Jul 2009 20:39:34 +0000</pubDate>
		<guid isPermaLink="false">http://whatever.scalzi.com/?p=7919#comment-154179</guid>
		<description><![CDATA[Dave @ 21: That does look like what happened here.  The first mangled word is &quot;special&quot;, shifted to &quot;sqfdjbm&quot;, and the press release appears to end with a &quot;-- 30 --&quot; shifted to a &quot;==41==&quot; or something like that.  The resolution of the picture isn&#039;t quite good enough to make the text decipherable without a lot of work.]]></description>
		<content:encoded><![CDATA[<p>Dave @ 21: That does look like what happened here.  The first mangled word is &#8220;special&#8221;, shifted to &#8220;sqfdjbm&#8221;, and the press release appears to end with a &#8220;&#8211; 30 &#8211;&#8221; shifted to a &#8220;==41==&#8221; or something like that.  The resolution of the picture isn&#8217;t quite good enough to make the text decipherable without a lot of work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Captain Button</title>
		<link>http://whatever.scalzi.com/2009/07/10/a-handy-tip-for-publicists/#comment-154173</link>
		<dc:creator><![CDATA[Captain Button]]></dc:creator>
		<pubDate>Sat, 11 Jul 2009 17:47:51 +0000</pubDate>
		<guid isPermaLink="false">http://whatever.scalzi.com/?p=7919#comment-154173</guid>
		<description><![CDATA[IIRC, to translate Martian Gibberish you have to start with the Martian periodic table of the elements.]]></description>
		<content:encoded><![CDATA[<p>IIRC, to translate Martian Gibberish you have to start with the Martian periodic table of the elements.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Reid</title>
		<link>http://whatever.scalzi.com/2009/07/10/a-handy-tip-for-publicists/#comment-154172</link>
		<dc:creator><![CDATA[Kevin Reid]]></dc:creator>
		<pubDate>Sat, 11 Jul 2009 17:37:42 +0000</pubDate>
		<guid isPermaLink="false">http://whatever.scalzi.com/?p=7919#comment-154172</guid>
		<description><![CDATA[Some glitch caused the printer (or software renderer, whichever stage converts drawing instructions to image pixels) to start using a different font. The text becomes gibberish because the document representation is using the glyph numbering specific to the intended font, but wrong for the new one, and the spacing is bizarre because the glyphs are pre-placed according to the sizes of the intended glyphs, not the wrong ones.]]></description>
		<content:encoded><![CDATA[<p>Some glitch caused the printer (or software renderer, whichever stage converts drawing instructions to image pixels) to start using a different font. The text becomes gibberish because the document representation is using the glyph numbering specific to the intended font, but wrong for the new one, and the spacing is bizarre because the glyphs are pre-placed according to the sizes of the intended glyphs, not the wrong ones.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

