On 6/14/2024 9:35 AM, Henning Hraban Ramm wrote:
Am 13.06.24 um 23:13 schrieb Hans Hagen via ntg-context:
On 6/13/2024 10:04 PM, Otared Kavian wrote:
Hi Ralph,
I don’t see any pixels in the PDF file when I typeset your code snipet (on MacOS 11.7.10). Here is what I get. No problems on windows on chrome-os either. Mikael S and I checked it on his linux box and one can indeed see anti aliasing when taking a screen dump (depends on resolution).
So it's a linux rendering issue when taking dumps.
Not only. It also happens with all(?) PDF viewers on MacOS – at least 10.14 and 10.15, can anyone confirm with current versions?
So it’s dependend on the screen rendering, anti aliasing settings (that you usually can’t influence).
It doesn’t affect printing – or does it for anyone? I can imagine printing from Firefox, i.e. pdf.js, is affected, since it prints only in screen resolution. it's not related to math then, as there are also ligatures built this way, although often they often are less sensitive to thsi due to generous overlaps (unless they use a sequence of connecting strokes in
hm, so i have to stick to windows for viewing (and an ancient hardware laptop in order to avoid copilot and recall) but i'll check ubuntu anyway the same direction) also keep in mind that looking at a blown up character is not that realistic (for instance a traditional bitmap font might look great at 600 or 1200 dpi at intended size so zooming in showing raggedness is not the normal way to see it) btw, if one wants to observe inaccuracy, just zoom in in graphics made by drawing programs (even of famous companies) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------