<?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>KeynoteUser.com &#124; Keynote Themes, News, Tips and other goodies &#187; Bugs</title>
	<atom:link href="http://www.keynoteuser.com/category/bugs/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.keynoteuser.com</link>
	<description>The place for all things Keynote</description>
	<lastBuildDate>Tue, 24 Jan 2012 12:14:50 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>K09 Tip: Fix the &#8220;Not enough memory&#8221; Quicktime export error</title>
		<link>http://www.keynoteuser.com/2009/02/25/k09-tip-fix-the-not-enough-memory-quicktime-export-error/</link>
		<comments>http://www.keynoteuser.com/2009/02/25/k09-tip-fix-the-not-enough-memory-quicktime-export-error/#comments</comments>
		<pubDate>Wed, 25 Feb 2009 18:44:24 +0000</pubDate>
		<dc:creator>Brian Peat</dc:creator>
				<category><![CDATA[Bugs]]></category>
		<category><![CDATA[Tips]]></category>

		<guid isPermaLink="false">http://www.keynoteuser.com/?p=2013</guid>
		<description><![CDATA[We spend a lot of time on the Apple discussions and this particular thread regarding an error when exporting to QuickTime recently surfaced. Users have been getting this error: error -108Â There is not enough disk space or there is a problem with the file. UserÂ ericrmyers finally got a fix from AppleCare: &#8220;In your home folder, [...]]]></description>
			<content:encoded><![CDATA[<p>We spend a lot of time on the Apple discussions and <a href="http://discussions.apple.com/thread.jspa?threadID=1875860&amp;tstart=0" target="_blank">this particular thread</a> regarding an error when exporting to QuickTime recently surfaced. Users have been getting this error:</p>
<ul>
<li>error -108Â There is not enough disk space or there is a problem with the file.</li>
</ul>
<p><span id="more-2013"></span></p>
<p>UserÂ ericrmyers finally got a fix from AppleCare:</p>
<p>&#8220;In your home folder, open the library folder. Find the caches folder and drag it to the trash. Then go to the preferences folder and find the com.apple.iWork.Keynote.plist file and drag it to the trash. Restart your computer, and empty the trash. Like magic it fixed my problem with no re-dos of the files or turning off the all keyframes option. Apparently the preferences/cache files from iWork 08 can seriously screw up the new iWork 09.&#8221;</p>
<p>We&#8217;re hoping this is all that&#8217;s needed for this particular bug&#8230;it sure is annoying to create a huge presentation only to be stuck when you go to export it.</p>
<script type="text/javascript">(function() {var s = document.createElement('SCRIPT'), s1 = document.getElementsByTagName('SCRIPT')[0];s.type = 'text/javascript';s.async = true;s.src = 'http://widgets.digg.com/buttons.js';s1.parentNode.insertBefore(s, s1);})();</script><a class="DiggThisButton DiggCompact" href="http://digg.com/submit?url=http%3A%2F%2Fwww.keynoteuser.com%2F2009%2F02%2F25%2Fk09-tip-fix-the-not-enough-memory-quicktime-export-error%2F"></a>]]></content:encoded>
			<wfw:commentRss>http://www.keynoteuser.com/2009/02/25/k09-tip-fix-the-not-enough-memory-quicktime-export-error/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Jens NÃ¶ckel provides Keynote/Preview fix</title>
		<link>http://www.keynoteuser.com/2008/04/11/jens-nockel-provides-keynotepreview-fix/</link>
		<comments>http://www.keynoteuser.com/2008/04/11/jens-nockel-provides-keynotepreview-fix/#comments</comments>
		<pubDate>Fri, 11 Apr 2008 11:49:47 +0000</pubDate>
		<dc:creator>Ken Drake</dc:creator>
				<category><![CDATA[Bugs]]></category>
		<category><![CDATA[Tips]]></category>

		<guid isPermaLink="false">http://www.keynoteuser.com/news/?p=315</guid>
		<description><![CDATA[Copying from Preview to Keynote is easy again...]]></description>
			<content:encoded><![CDATA[<p>For some time now, Keynote (and indeed all of iWork) under Leopard has been suffering from a problem. Namely, if you attempt to Crop a .PDF in Preview then copy that cropped PDF into Keynote, you would get an image of the ENTIRE page, not just the cropped area. With the upgrade from Tiger&#8217;s version of Preview, to Leopard&#8217;s version, a very useful and efficient workflow had been halted. Now, to perform the same action required several steps <em>and</em> a separate application. While it was an effective workaround, we&#8217;ve still been waiting for a fix.</p>
<p><span id="more-315"></span></p>
<p>I had some idea of the PasteBoard interactions that were behind the problem, but I wasn&#8217;t aware of the specifics until I read <a href="http://tug.org/pipermail/macostex-archives/2008-April/034796.html" target="_blank">this post</a> by Martin Costabel. My initial suspicions were verified when I read that Preview had introduced some additional dimensions into the cropped image that weren&#8217;t there with Tiger&#8217;s Preview. Specifically, there&#8217;s now an /ArtBox parameter being set in the PDF that gets copied to the System PasteBoard. What I didn&#8217;t know (and why it works for other apps) is that while there is a properly dimensioned /CropBox parameter, Keynote is instead using the /ArtBox definitions&#8230; and those are set to the size of the entire page. This is why the cropped PDF copied into Keynote appears to have a box that&#8217;s the right size, but shows the entire PDF extending to the right and below <strong>outside the bounds of the box</strong>.</p>
<p>The fix for this is to alter /ArtBox so that it&#8217;s either removed OR equals /CropBox, and Jens&#8217; initial script does this, using ghostscript to properly re-create the altered PDF (many advanced Keynote users may already have ghostscript installed by way of a <a href="http://www.uoregon.edu/~noeckel/Keynote.html" target="_blank">TeX distribution</a>). Once I was aware of the specifics of the fix, I used iClip lite as a kind of PasteBoard peeker in order to see if I could apply the same fix in such a way that it would not require ghostscript to be installed. I discovered that, for the purposes of someone just wanting a properly cropped image in Keynote, massaging the data that gets placed on the PasteBoard was indeed good enough for that purpose. However, lacking the skills of Jens, I contacted him with my findings inquiring if he thought it would be possible as well. Not only did he reply that it was possible, he then prepared and made available a <em>separate</em> script which does <strong>NOT</strong> require ghostscript!</p>
<p>You can find the ghostscript enabled version, the no ghostscript version AND the instructions for their installation and use <a href="http://www.uoregon.edu/~noeckel/PreviewLeopard.html" target="_blank">on this page</a>.</p>
<script type="text/javascript">(function() {var s = document.createElement('SCRIPT'), s1 = document.getElementsByTagName('SCRIPT')[0];s.type = 'text/javascript';s.async = true;s.src = 'http://widgets.digg.com/buttons.js';s1.parentNode.insertBefore(s, s1);})();</script><a class="DiggThisButton DiggCompact" href="http://digg.com/submit?url=http%3A%2F%2Fwww.keynoteuser.com%2F2008%2F04%2F11%2Fjens-nockel-provides-keynotepreview-fix%2F"></a>]]></content:encoded>
			<wfw:commentRss>http://www.keynoteuser.com/2008/04/11/jens-nockel-provides-keynotepreview-fix/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Leopard loves iWork 06</title>
		<link>http://www.keynoteuser.com/2007/11/05/leopard-loves-iwork-06/</link>
		<comments>http://www.keynoteuser.com/2007/11/05/leopard-loves-iwork-06/#comments</comments>
		<pubDate>Mon, 05 Nov 2007 22:15:53 +0000</pubDate>
		<dc:creator>Brian Peat</dc:creator>
				<category><![CDATA[Bugs]]></category>
		<category><![CDATA[Tips]]></category>

		<guid isPermaLink="false">http://www.keynoteuser.com/news/?p=259</guid>
		<description><![CDATA[Leopard doesn't seem to like iWork 06 and iWork 08 on the same drive...]]></description>
			<content:encoded><![CDATA[<p>Over the last few days we&#8217;ve noticed a pattern with Leopard upgraders&#8230;many have complained that their old presentations no longer work in Keynote under Leopard. While there may actually be some strange compatibility issues, this one is most likely a very fixable bug in Leopard regarding iWork 06. If you have a copy of iWork 06 and iWork 08 on the same Leopard machine and you double click a .key file, you may find that Leopard launches Keynote 3 instead of Keynote 08 (v4). The best way to tell if this is happening is to watch your dock. If you see a blue podium bouncing in the dock, and NOT the new brown podium, you&#8217;ve been bit by the bug. The result is Keynote 3 trying to open a Keynote 4 file and telling you it can&#8217;t open it.</p>
<p>So what can you do to fix this? Well, normally, you can simply click on the .key file, choose Get Info from the File menu, and change the &#8220;Open with&#8221; setting to the correct copy of Keynote. Unfortunately, this is where the bug kicks in. In our tests, changing the default app did NOT stick, and in fact, if we hit the Change All&#8230; button, we could visibly see the setting switch BACK to Keynote 3 right before our eyes.</p>
<p>The solution was to rename Keynote in the iWork 06 folder to Keynote 3. Renaming it so that there weren&#8217;t two copies of an app called Keynote on the machine seemed to fix the problem right away (though you might find you still need to use the Get Info window to change the default Keynote app). We hope this tip will help some of you who might be experiencing this same problem.</p>
<script type="text/javascript">(function() {var s = document.createElement('SCRIPT'), s1 = document.getElementsByTagName('SCRIPT')[0];s.type = 'text/javascript';s.async = true;s.src = 'http://widgets.digg.com/buttons.js';s1.parentNode.insertBefore(s, s1);})();</script><a class="DiggThisButton DiggCompact" href="http://digg.com/submit?url=http%3A%2F%2Fwww.keynoteuser.com%2F2007%2F11%2F05%2Fleopard-loves-iwork-06%2F"></a>]]></content:encoded>
			<wfw:commentRss>http://www.keynoteuser.com/2007/11/05/leopard-loves-iwork-06/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Apple updates QuickTime to 7.1.1</title>
		<link>http://www.keynoteuser.com/2006/05/31/apple-updates-quicktime-to-711/</link>
		<comments>http://www.keynoteuser.com/2006/05/31/apple-updates-quicktime-to-711/#comments</comments>
		<pubDate>Wed, 31 May 2006 18:29:13 +0000</pubDate>
		<dc:creator>Ken Drake</dc:creator>
				<category><![CDATA[Bugs]]></category>
		<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://www.keynoteuser.com/news/?p=133</guid>
		<description><![CDATA[Fixes a problem specific to Keynote exporting to iDVD...]]></description>
			<content:encoded><![CDATA[<p>Available from both Software Update <i>and</i> Apple&#8217;s QuickTime <a href="http://www.apple.com/quicktime/download/mac.html">download page</a>, version 7.1.1 of QuickTime &#8220;addresses an issue with 3rd party start-up items on Intel Macs.&#8221; Of interest to OUR visitors is the vastly more important &#8220;This release also fixes an issue exporting Keynote presentations to iDVD&#8221;.</p>
<p>As would be expected from such a Mac targeted release, there is no attendant Windows version available (current version remains 7.1).</p>
<script type="text/javascript">(function() {var s = document.createElement('SCRIPT'), s1 = document.getElementsByTagName('SCRIPT')[0];s.type = 'text/javascript';s.async = true;s.src = 'http://widgets.digg.com/buttons.js';s1.parentNode.insertBefore(s, s1);})();</script><a class="DiggThisButton DiggCompact" href="http://digg.com/submit?url=http%3A%2F%2Fwww.keynoteuser.com%2F2006%2F05%2F31%2Fapple-updates-quicktime-to-711%2F"></a>]]></content:encoded>
			<wfw:commentRss>http://www.keynoteuser.com/2006/05/31/apple-updates-quicktime-to-711/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Fixing Sorenson 3 Pro transition bug</title>
		<link>http://www.keynoteuser.com/2005/12/21/fixing-sorenson-3-pro-transition-bug/</link>
		<comments>http://www.keynoteuser.com/2005/12/21/fixing-sorenson-3-pro-transition-bug/#comments</comments>
		<pubDate>Wed, 21 Dec 2005 13:05:08 +0000</pubDate>
		<dc:creator>Ken Drake</dc:creator>
				<category><![CDATA[Bugs]]></category>

		<guid isPermaLink="false">http://www.keynoteuser.com/news/?p=79</guid>
		<description><![CDATA[Keynote has a bug when exporting using Sorenson when Sorenson 3 Pro is installed. This is how to resolve it...]]></description>
			<content:encoded><![CDATA[<p>Is your Flip half flipping? Experiencing Drop stop? Having problems with your Dissolve only partially dissolving? You&#8217;re not alone (If you haven&#8217;t seen it, it looks like someone&#8217;s thrown a wood block into your screen to keep your transition from playing all the way when exporting as a QuickTime movie). We&#8217;ve seen this several times before and have determined what may be the cause of your malady if you&#8217;re using the Sorenson 3 Pro codec.</p>
<p>Using the Sorenson 3 codec means that your viewers only need to have QuickTime 5. Having Sorenson 3 Pro opens you up to many more compression options, but it also defaults the problem option, bidirectional prediction, active. Briefly, this is the little piece of magic that allows a Sorenson coded .mov to play backwards as smoothly as forwards (for allowing your viewers to cue/review smoothly like a DVD player). This is wonderful for regular movies, but, since this type of frame creation is not what Keynote expects, it causes a problem when the frame doesn&#8217;t line up with Keynote&#8217;s sprite track. All you really need to do is just turn it off, but, since you won&#8217;t find Sorenson in your System Preferences, we&#8217;ve mapped out how you get TO it in order to DO it.</p>
<p>You can do this with most any program that exports QuickTime (strangely, except for Keynote) but to make sure we&#8217;re all on the same page, we&#8217;ll use the QuickTime Player. Open the QuickTime Player then open a movie (you need to go into the Export options and you can&#8217;t get there without having media open).</p>
<p>Change the Export popup menu to Movie to QuickTime Movie and click the Options&#8230; button.<br />
<img src="http://www.keynoteuser.com/~newsimages/exportwindow.gif" align=left"/></p>
<p>Now you should be in the Movie Settings window. In the video area, click the Settings&#8230; button.<br />
<img src="http://www.keynoteuser.com/~newsimages/moviesettings.gif" align=left"/></p>
<p>In the Compression Settings sheet, click the popup tab at the top and choose Sorenson Video 3, then click the Options&#8230; button.<br />
<img src="http://www.keynoteuser.com/~newsimages/compsettings.gif" align=left"/></p>
<p>And what do you know, we&#8217;re here!</p>
<p>Set B-Frames<br />
The Sorenson settings open up to a nice Summary screen which should show your problem right there.<br />
<img src="http://www.keynoteuser.com/~newsimages/bframeset.gif" align=left"/></p>
<p>You&#8217;ll see that Use B-Frames has a check beside it. Since this IS only a summary screen, we&#8217;ll need to go to the Encode tab to turn it off. Where Bidirectional Prediction: shows Allow, click this and change to Off,<br />
<img src="http://www.keynoteuser.com/~newsimages/allowtooff.gif" align=left"/><br />
then click OK.<br />
<img src="http://www.keynoteuser.com/~newsimages/sorensonbottom.gif" align=left"/></p>
<p>This will take you back to the Compression Settings sheet. Since our change was OK&#8217;d in Sorenson&#8217;s preferences, you don&#8217;t need to click OK in the windows that are still open, so just Cancel your way back to the movie and quit the QuickTime Player.</p>
<p>Now you&#8217;re free to use Sorenson as much as you like without having to worry about incomplete transitions. If you need this feature for other movie exports, DON&#8217;T forget to go and turn it back on after working with Keynote.</p>
<script type="text/javascript">(function() {var s = document.createElement('SCRIPT'), s1 = document.getElementsByTagName('SCRIPT')[0];s.type = 'text/javascript';s.async = true;s.src = 'http://widgets.digg.com/buttons.js';s1.parentNode.insertBefore(s, s1);})();</script><a class="DiggThisButton DiggCompact" href="http://digg.com/submit?url=http%3A%2F%2Fwww.keynoteuser.com%2F2005%2F12%2F21%2Ffixing-sorenson-3-pro-transition-bug%2F"></a>]]></content:encoded>
			<wfw:commentRss>http://www.keynoteuser.com/2005/12/21/fixing-sorenson-3-pro-transition-bug/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Possible fix for Windows QuickTime 7 bug?</title>
		<link>http://www.keynoteuser.com/2005/11/28/possible-fix-for-windows-quicktime-7-bug/</link>
		<comments>http://www.keynoteuser.com/2005/11/28/possible-fix-for-windows-quicktime-7-bug/#comments</comments>
		<pubDate>Mon, 28 Nov 2005 14:28:23 +0000</pubDate>
		<dc:creator>Brian Peat</dc:creator>
				<category><![CDATA[Bugs]]></category>

		<guid isPermaLink="false">http://www.keynoteuser.com/news/?p=71</guid>
		<description><![CDATA[A user on the Apple Keynote forums has posted a possible fix for a problem plaguing Windows users with QuickTime 7 who want to play Keynote videos...]]></description>
			<content:encoded><![CDATA[<p>We&#8217;re not sure how we missed the solution back on November 14th, but here&#8217;s a link to the thread:<br />
<a href="http://discussions.apple.com/thread.jspa?threadID=154423&#038;tstart=0" target=_new>Keynote QuickTime Issues on Windows QT 7</a><br />
The solution is near the end of the thread.</p>
<p>So what&#8217;s the big deal?<br />
It seems that when Internet Explorer is set as the default browser in Windows, Interactive QT movies made from Keynote don&#8217;t work properly in QuickTime 7. The solution up to this point was to go back to using QT 6.5.2. User gillettebl found a better solution, which is to change the default browser to something else (in this case Firefox).</p>
<p>Here&#8217;s a quote from his post:<br />
&#8220;Yup, the error manifests when IE is the default browser&#8230; but not if using Firefox. Try this: Start&#8230;Set Program Access and Defaults (or Start&#8230;Control_Panel&#8230;Add or Remove Programs; choose the lowest tab on the left), and tell it to use Firefox as the default browser.&#8221;</p>
<p>Another user points out that this is still a problem since most of the world won&#8217;t know to change their default browser, but at least it&#8217;s a good start to getting full interactive functionality on a Windows machine.</p>
<script type="text/javascript">(function() {var s = document.createElement('SCRIPT'), s1 = document.getElementsByTagName('SCRIPT')[0];s.type = 'text/javascript';s.async = true;s.src = 'http://widgets.digg.com/buttons.js';s1.parentNode.insertBefore(s, s1);})();</script><a class="DiggThisButton DiggCompact" href="http://digg.com/submit?url=http%3A%2F%2Fwww.keynoteuser.com%2F2005%2F11%2F28%2Fpossible-fix-for-windows-quicktime-7-bug%2F"></a>]]></content:encoded>
			<wfw:commentRss>http://www.keynoteuser.com/2005/11/28/possible-fix-for-windows-quicktime-7-bug/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Rendering problem on Arabic/Hebrew text builds</title>
		<link>http://www.keynoteuser.com/2005/06/06/rendering-problem-on-arabichebrew-text-builds/</link>
		<comments>http://www.keynoteuser.com/2005/06/06/rendering-problem-on-arabichebrew-text-builds/#comments</comments>
		<pubDate>Mon, 06 Jun 2005 16:36:18 +0000</pubDate>
		<dc:creator>Ken Drake</dc:creator>
				<category><![CDATA[Bugs]]></category>

		<guid isPermaLink="false">/?p=43</guid>
		<description><![CDATA[Text blocks with certain characters only render the rightmost character...]]></description>
			<content:encoded><![CDATA[<p>This one comes from Apple&#8217;s discussion boards. A user found that after typing an Arabic word in Keynote, applying a build to that word makes only the FIRST character build onto the screen. Another user found the same problem with Hebrew text as well. Grouping the text block with another <i>transparent</i> object such as an empty text block or a shape with it&#8217;s fill and stroke set to &#8220;None&#8221; allows the entire object to build.</p>
<script type="text/javascript">(function() {var s = document.createElement('SCRIPT'), s1 = document.getElementsByTagName('SCRIPT')[0];s.type = 'text/javascript';s.async = true;s.src = 'http://widgets.digg.com/buttons.js';s1.parentNode.insertBefore(s, s1);})();</script><a class="DiggThisButton DiggCompact" href="http://digg.com/submit?url=http%3A%2F%2Fwww.keynoteuser.com%2F2005%2F06%2F06%2Frendering-problem-on-arabichebrew-text-builds%2F"></a>]]></content:encoded>
			<wfw:commentRss>http://www.keynoteuser.com/2005/06/06/rendering-problem-on-arabichebrew-text-builds/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>QuickTime export problem and workaround</title>
		<link>http://www.keynoteuser.com/2005/06/06/quicktime-export-problem-and-workaround/</link>
		<comments>http://www.keynoteuser.com/2005/06/06/quicktime-export-problem-and-workaround/#comments</comments>
		<pubDate>Mon, 06 Jun 2005 06:35:38 +0000</pubDate>
		<dc:creator>Ken Drake</dc:creator>
				<category><![CDATA[Bugs]]></category>

		<guid isPermaLink="false">/?p=42</guid>
		<description><![CDATA[A workaround to the "unable to export" problem was posted to our <a href="http://groups.yahoo.com/group/applekeynote/">Yahoo mailing list...</a>]]></description>
			<content:encoded><![CDATA[<p>If you&#8217;re exporting your presentation to QuickTime and get this error, <img src="http://www.keynoteuser.com/~newsimages/quicktimeerror.png" align=center alt="QuickTime error"/><br />
you&#8217;ve run into a problem introduced with Keynote 2.0.1. The solution to delete your Keynote preferences WILL work, but it will reset any other settings you&#8217;ve made back to default as well. The easier way to solve the problem is to go into Keynote -> Preferences, choose the Slideshow preferences and place a check beside &#8220;Exit presentation after last slide&#8221;.<br />
<img src="http://www.keynoteuser.com/~newsimages/qtprefs.png" align=center alt="Slideshow Preferences"/><br />
Once this is done, you&#8217;ll be able to export to QuickTime again.</p>
<script type="text/javascript">(function() {var s = document.createElement('SCRIPT'), s1 = document.getElementsByTagName('SCRIPT')[0];s.type = 'text/javascript';s.async = true;s.src = 'http://widgets.digg.com/buttons.js';s1.parentNode.insertBefore(s, s1);})();</script><a class="DiggThisButton DiggCompact" href="http://digg.com/submit?url=http%3A%2F%2Fwww.keynoteuser.com%2F2005%2F06%2F06%2Fquicktime-export-problem-and-workaround%2F"></a>]]></content:encoded>
			<wfw:commentRss>http://www.keynoteuser.com/2005/06/06/quicktime-export-problem-and-workaround/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>Unable to export imported .ppt&#8217;s as PowerPoint?</title>
		<link>http://www.keynoteuser.com/2005/05/03/unable-to-export-imported-ppts-as-powerpoint/</link>
		<comments>http://www.keynoteuser.com/2005/05/03/unable-to-export-imported-ppts-as-powerpoint/#comments</comments>
		<pubDate>Tue, 03 May 2005 13:07:04 +0000</pubDate>
		<dc:creator>Ken Drake</dc:creator>
				<category><![CDATA[Bugs]]></category>

		<guid isPermaLink="false">/?p=32</guid>
		<description><![CDATA[Certain PowerPoint files are causing problems during export to .ppt...]]></description>
			<content:encoded><![CDATA[<p>We&#8217;ve found an example PowerPoint file here <a href="http://www.cs.princeton.edu/~sudhakar/talks/memerr.ppt">http://www.cs.princeton.edu/~sudhakar/talks/memerr.ppt</a> (You will get errors because it includes vertical text and two fonts you may not have installed) that will fail on export back to PowerPoint. However, if you go into the Master Slides and remove the Title &#038; Bullets Master, it will then export successfully.</p>
<p>The problem in this case appears to be the way the Body text is formatted on the Titles &#038; Bullets Master. If you go into the Text Inspector pane, choose the Bullets &#038; Numbering tab, and choose any of the options there, this will reformat the Body and it should export properly. More information will be posted as we discover more about this issue.</p>
<script type="text/javascript">(function() {var s = document.createElement('SCRIPT'), s1 = document.getElementsByTagName('SCRIPT')[0];s.type = 'text/javascript';s.async = true;s.src = 'http://widgets.digg.com/buttons.js';s1.parentNode.insertBefore(s, s1);})();</script><a class="DiggThisButton DiggCompact" href="http://digg.com/submit?url=http%3A%2F%2Fwww.keynoteuser.com%2F2005%2F05%2F03%2Funable-to-export-imported-ppts-as-powerpoint%2F"></a>]]></content:encoded>
			<wfw:commentRss>http://www.keynoteuser.com/2005/05/03/unable-to-export-imported-ppts-as-powerpoint/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>DivX 5.2.1 incompatible with iWork?</title>
		<link>http://www.keynoteuser.com/2005/05/02/divx-521-incompatible-with-iwork/</link>
		<comments>http://www.keynoteuser.com/2005/05/02/divx-521-incompatible-with-iwork/#comments</comments>
		<pubDate>Tue, 03 May 2005 01:31:13 +0000</pubDate>
		<dc:creator>Brian Peat</dc:creator>
				<category><![CDATA[Bugs]]></category>

		<guid isPermaLink="false">/?p=30</guid>
		<description><![CDATA[According to Macintouch.com and at least one Apple forum reader, the DivX QT Codec causes problems with both Pages and Keynote 2...]]></description>
			<content:encoded><![CDATA[<p>According to <a href="http://www.macintouch.com/tigerreview/incompatibility.html" target=new>Macintouch.com</a> and at least one <a href="http://discussions.info.apple.com/webx?14@295.zO0zaeMwQl7.0@.68adc950" target=new>Apple forum reader</a>, the DivX QT Codec causes problems with both Pages and Keynote 2. The symptoms are a double help menu in both Pages and Keynote and possible instabilities with Keynote. Since we don&#8217;t have it installed on our Tiger machine, we can&#8217;t test this out, but removing the codec should fix the problem.</p>
<script type="text/javascript">(function() {var s = document.createElement('SCRIPT'), s1 = document.getElementsByTagName('SCRIPT')[0];s.type = 'text/javascript';s.async = true;s.src = 'http://widgets.digg.com/buttons.js';s1.parentNode.insertBefore(s, s1);})();</script><a class="DiggThisButton DiggCompact" href="http://digg.com/submit?url=http%3A%2F%2Fwww.keynoteuser.com%2F2005%2F05%2F02%2Fdivx-521-incompatible-with-iwork%2F"></a>]]></content:encoded>
			<wfw:commentRss>http://www.keynoteuser.com/2005/05/02/divx-521-incompatible-with-iwork/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Keynote 2 crashes when exporting using H.264</title>
		<link>http://www.keynoteuser.com/2005/04/30/keynote-2-has-issues-with-h264-exporting/</link>
		<comments>http://www.keynoteuser.com/2005/04/30/keynote-2-has-issues-with-h264-exporting/#comments</comments>
		<pubDate>Sat, 30 Apr 2005 22:39:28 +0000</pubDate>
		<dc:creator>Brian Peat</dc:creator>
				<category><![CDATA[Bugs]]></category>

		<guid isPermaLink="false">/?p=28</guid>
		<description><![CDATA[One user on Apple's forums has discovered problems when trying to export a presentation using the new H.264 codec in QuickTime 7...]]></description>
			<content:encoded><![CDATA[<p>One user on Apple&#8217;s forums has discovered problems when trying to export a presentation using the new H.264 codec in QuickTime 7. If you use the custom QuickTime export functions in Keynote and choose H.264 as the codec, Keynote will crash on export. While we&#8217;re not sure if this happens under Panther using QuickTime 7 (we assume it does) we&#8217;ve been able to reproduce it in Tiger.</p>
<p>The fix is to UNCHECK the box labeled &#8220;Key frame every _ frames.&#8221; Doing this allows Keynote to export the movie properly. Hopefully Apple will have a fix for this soon.</p>
<script type="text/javascript">(function() {var s = document.createElement('SCRIPT'), s1 = document.getElementsByTagName('SCRIPT')[0];s.type = 'text/javascript';s.async = true;s.src = 'http://widgets.digg.com/buttons.js';s1.parentNode.insertBefore(s, s1);})();</script><a class="DiggThisButton DiggCompact" href="http://digg.com/submit?url=http%3A%2F%2Fwww.keynoteuser.com%2F2005%2F04%2F30%2Fkeynote-2-has-issues-with-h264-exporting%2F"></a>]]></content:encoded>
			<wfw:commentRss>http://www.keynoteuser.com/2005/04/30/keynote-2-has-issues-with-h264-exporting/feed/</wfw:commentRss>
		<slash:comments>14</slash:comments>
		</item>
	</channel>
</rss>

