![]() From the terminal, issue the following commands: sudo rm -rf `lsof | grep /x | grep Finder | cut -c 66-139` Another search brought about this hint on how to delete all font caches in Leopard. Much googling ensued, until I found a thread on the mac tex newsgroup which suggested that the problem lay in corrupted font caches. More mysterious was the fact that the same document could render differently on multiple openings. preview.app, skim.app, Texniscope.app, LaTeXit.app, but not adobe reader 8). The punchline is that fonts were not being displayed correctly by any application that used Apple's native pdf engine (e.g. I like TeXniscope much better than Skim because it's much simpler, has better keyboard shorcuts for paging, and Skim makes you manually refresh the pdf every time there's a latex error (otherwise Skim auto-refreshes).Īfter recently upgrading to Leopard, something very strange and terrible began happening with pdf files created by latex (MacTeX 2007 distribution). Alas, it appears I have to give up TeXniscope. It seems I found the answer, from, pasted below. Which will kill the Apple Type Services server daemon (ATSServer) and spawn a new instance, coincidentally rebuilding its cache files. You can actually recover from this problem without rebooting, although you may see it recur with the same document in the same session. Note that Adobe's Acrobat or Reader applications can often display these documents without any problems presumably Adobe's error-checking is more liberal than Apple's. ![]() ![]() Unfortunately, they weren't at all clear about exactly what it is that PDFTeX is doing wrong, which makes fixing it or even reporting the bug to the PDFTeX developers problematic. Their claim is that PDFTeX is embedding the fonts incorrectly, and they have fixed the Apple PDF library to be more strict about what it will and won't accept, which means that you will continue to see problems with PDF documents created with PDFTeX in Preview, TeXShop, or other tools that display PDF using Apple's PDF engine. Apple knows about the problem and isn't planning to fix it (I had a faculty member spend a lot of time testing and submit a bug to Apple).
0 Comments
Leave a Reply. |