ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: [NTG-context] Re: How to improve appearance of bars in frac, sqrt, etc. on screens?
Date: Fri, 14 Jun 2024 11:44:34 +0200	[thread overview]
Message-ID: <07d58481-6fa8-41d3-b74b-b32dedd6b8e3@freedom.nl> (raw)
In-Reply-To: <eab1c6c1-159f-4e8a-a6ae-f87705944227@fiee.net>

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).

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

> 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 
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
-----------------------------------------------------------------

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2024-06-14 10:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13 11:10 [NTG-context] " Ralph
2024-06-13 20:04 ` [NTG-context] " Otared Kavian
2024-06-13 20:43   ` Bruce Horrocks
2024-06-13 21:13   ` Hans Hagen via ntg-context
2024-06-14  7:35     ` Henning Hraban Ramm
2024-06-14  9:44       ` Hans Hagen via ntg-context [this message]
2024-06-14 11:57         ` Taco Hoekwater
2024-06-15  8:59           ` ralph.2718
2024-06-15  9:17             ` Hans Hagen via ntg-context
2024-10-07  3:28         ` Alan Braslau via ntg-context

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=07d58481-6fa8-41d3-b74b-b32dedd6b8e3@freedom.nl \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@freedom.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).