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: Sat, 15 Jun 2024 11:17:16 +0200 [thread overview]
Message-ID: <4f03a99d-9fd6-44ba-a2f3-9e9ca70c27b4@freedom.nl> (raw)
In-Reply-To: <171844198766.3523835.14898538478293451218@cgl.ntg.nl>
On 6/15/2024 10:59 AM, ralph.2718@email-postfach.info wrote:
> Hi,
>
> thank you all for your replies so far. I guess I’ll have to live with that for now (of course this isn’t really a problem, but a bit unpleasant to look at when you’re used to the straight lines in LaTeX). Just wanted to add that I can see this artifacts quite clearly on a 13 inch 1080p screen in the PDF viewer (depends on zoom level, on some zoom levels I see nothing) and not only when enlarging a screenshot. After all, it’s visible in my attached screenshots even if displayed in their original resolution. (Naming of my screenshots wasn’t very clear, zoomed.png is zoomed-in in the pdf viewer, not a zoomed-in screenshot.)
The "left radical + rule" isn't perfect either, because it depends on
overlap. Depending on the font you can see issues at the connection
(actually these might be obscured by aliasing at low res). You can try
that outside lmtx with different fonts.
Also, because rules are often rendered differently from glyphs (and
rules can use either a line or rectangle fill) it's always been an issue
(which is also why engines have some heuristics for choosing one or the
other method).
And, as mentioned, vertical extenders also use the same etechnology as
we now use for radicals, it's just that there was never a concept like
that in engines for radicals. Arrows sit in the same category and also
use the same glyphs so there one can observe the same. Actually, even in
traditional tex arrows are made from minusus and an arrowhead
overlapping piecewise.
Maybe viewers will catch up.
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
___________________________________________________________________________________
next prev parent reply other threads:[~2024-06-15 9:17 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
2024-06-14 11:57 ` Taco Hoekwater
2024-06-15 8:59 ` ralph.2718
2024-06-15 9:17 ` Hans Hagen via ntg-context [this message]
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=4f03a99d-9fd6-44ba-a2f3-9e9ca70c27b4@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).