<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">David,<div><br></div><div>As often happens, Ross gets to the crux of the matter. Below are your comments, his comments, and my take on them.</div><div><br><div><div>On May 12, 2009, at 5:35 PM, Ross Moore wrote:</div><div><br></div><blockquote type="cite"><div>Beware, this "small PDF" is actually the whole page, with cropping<br>set to display just the portion you selected.<br>At least that is how it used to be, a few years back.<br>RK could confirm whether this has changed more recently.<br></div></blockquote><div><br></div>It changed when support for Leopard was added. The old code didn't work on Leopard. The current code works like this: an offscreen view is created and given an image consisting of the current pdf page. Then PDF data is created from a rectangle on this page using Apple's routine</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>[myView dataWithPDFInsideRect: myRectangle]</div><div><br></div><div>Thus everything depends on what "dataWithPDFInsideRect" actually does. I don't know for sure, but I doubt very much that it takes the entire page's PDF and adds a bounds rectangle. I'll bet that it does "the right thing."</div><div><br></div><div>Next David wrote</div><div><br></div><div><blockquote type="cite"><div><blockquote type="cite"><blockquote type="cite"><font class="Apple-style-span" color="#000000"><br></font></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I HAVE installed the font-cache-bug fix. (Several times, now...)<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">After not too terribly long a time, now, whether TeXShop or LaTeXiT, characters in the output (not just stuff I drag out of either) start disappearing (or sometimes replaced by exclamation points). Tends to get worse the longer I wait before rebooting. Both in TeXShop's preview and/or LaTeXiT -- once it starts in one I start seeing it in the other.<br></blockquote></blockquote></div></blockquote><div><br></div>It wouldn't be enough to install the bug fix. To be certain of no problems, all of those pdf documents used to construct the snippets would need to be retypeset. This will be easier in LaTeXiT since that program automatically saves the TeX code. I suspect that you have ONE (or at any case only a small number) of bad snippets.</div><div><br></div><div>Two keys points: "once it starts in one I start seeing it in the other" --- this is very characteristic of the font cache bug. Also "tends to get worse the longer I wait before rebooting" suggests that rebooting fixes the problem, another characteristic of the font cache bug.</div><div><blockquote type="cite"><div><br>What does it look like in Adobe Reader ?<br>... or in Keynote, or whatever viewer that you'll be using for<br>the presentation?<br></div></blockquote><div><br></div>Testing with Adobe Reader would be particularly interesting since it doesn't use Apple's pdf display code and thus is immune to the bug. If your slides work in Adobe Reader, that might clinch the matter.</div><div><br></div><div>On the other hand, Keynote probably uses Apple's pdf display code, so once the bug rears its head I'd guess that Keynote will show the problem.</div><div><br></div><div>Dick Koch</div><div><br></div><div><br></div></div></body></html>