Menu

#1007 Weird behaviour of font rendering

PDFKit
closed-cant-fix
nobody
None
5
2014-10-18
2014-10-18
yuggib
No

This is a strange one. I have just upgraded to Yosemite, and I immediately noted a bad rendering of the anti-aliased text:

I am editing latex (with aquamacs); and this was part of my output. Then I changed the font in the latex file (while in fullscreen in skim), and then changed back (always in full-screen, with auto-refresh). This procedure gave me a greatly improved rendering:

I was able to replicate the result repeating the exact procedure (changing font and recompiling while in fullscreen with auto-refresh), but exiting full-screen, opening the file again, or almost anything else revert the rendering to the "bad" one.

Any ideas?

2 Attachments

Discussion

  • Christiaan Hofman

    • status: unread --> closed-cant-fix
     
  • Christiaan Hofman

    Unfortunately there is nothing we can o about this, because the rendering of the PDF is done by Apple's PDFKit. This needs to be fixed by Apple.

     
  • yuggib

    yuggib - 2014-10-18

    Ok, thanks. Just to understand better: I imagine it is not possible (or viable) to do the pdf rendering by any other means, is it right? From what I have read in other bug reports this pdfkit seems very unreliable...

     
    • Christiaan Hofman

      No, there is nothing we can do to influence that, PDFKit rendering is a black box for us.

       

Log in to post a comment.

MongoDB Logo MongoDB