0

I am using TeXmaker on a MacBook Retina with an additional external display. The documents displayed in the PDF viewer while on the external display are very grainy/blurry and hard to read, while they are completely fine on the MacBook screen and when opening the produced PDF with another software. I didn't find anything related to this online.

naphaneal
  • 2,614
amazon
  • 1
  • 1
  • 1
  • Welcome to TeX.SX! – Heiko Oberdiek Apr 18 '14 at 20:40
  • Please help people to help you by posting a minimal working example (MWE) that illustrates your problem. It will be much easier for us to reproduce your situation and find out what the issue is when we see compilable code, starting with \documentclass{...} and ending with \end{document}. Have you tried adding \usepackage[T1]{fontenc} to your preamble? – cfr Apr 19 '14 at 03:15

2 Answers2

2

I had the same issue and found a work around. Open texmaker on your laptop's screen and adjust the size of the program window so that it fits the external screen (or your needs). If you than drag the texmaker window to the external screen and do not (!) resize the texmaker window, the internal pdf viewer looks normal.

As you might have an external screen larger than the laptop screen, you have to fiddle a bit to first adjust the size of the program window on your laptop screen, but it is worth it. The good thing is that resizing the pdf size within the viewer is fine.

  • If that's the case I would recommend to use an other pdfreader, you'll need one, which does not block writing on the file and updates it when you compile. http://tex.stackexchange.com/questions/43057/macosx-pdf-viewer-automatic-reload-on-file-modification – MaxNoe Aug 08 '14 at 08:04
  • Hey, I tried this and it did not work. The text looks fine on my laptop's screen regardless of window size, and always looks gritty on the external monitor also regardless of window size. – faiuwle Dec 05 '22 at 01:39
1

Don't remember where I read this, but tried MacOsx 10.6 64 bits version and it works without any work around. Apparently MacOsx 10.7 64 bits is the problem. Give it a try.

bes
  • 11