ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] update
Date: Mon, 11 Mar 2024 18:48:40 +0100	[thread overview]
Message-ID: <de83f26c-c7dc-4cf1-8ff6-3e973b645b52@xs4all.nl> (raw)

Hi,

Todays update has a fix for the compact mode slant interference (as 
explained by Wolfgang a few days ago). Hopefully that works out well.

We (MS and HH) also managed to make curve detection more accurate (the 
decision routine that is responsible for straight lines in the MP 
output) so that extreme paths with control points way beyond reasonable 
still produce the right output (before we could get a wrong bbox due to 
clipping the curve in the backend). One can actually also force "always 
curve" with "withcurvature 1" (more variants might follow) but that is 
more or us to have a test option. Curvature detection is mostly a pdf 
efficiency feature and normally users should rely on the default to work 
okay.

Other new mp features are relative and absolute points which makes it 
possible to define paths in a turtle graphics way (a bit like hlineto 
and vline in postscript), a native "--" operator (equivalent but 
somewehat more efficient on huge generated paths). The luametafun manual 
has a chapter on paths that describes some of this.

Yet another new feature is "firstcontrol" and "secondcontrol" that is an 
addendum to controls that makes both control points the same when only 
one is given.

Finally there is a fix in mp where some directions, think { dir 120 }, 
gave the wrong result due to sign swapping (so it was seen as { dir 200} 
or { dir -60 }) as side effect of negative zeros fed into tan2. This 
became obvious when MS reprocessed a graphic, as last year we switched 
from scsled (no bug) to double (long time bug exposed). (The bug is also 
present in LuaTeX double/binary mode but it will be fixed there too.)

The rest is not (yet) worth mentioning,

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-03-11 17:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11 17:48 Hans Hagen [this message]
2024-03-11 18:23 ` [NTG-context] update Pablo Rodriguez via ntg-context
2024-03-11 19:14   ` Emanuel Han via ntg-context
  -- strict thread matches above, loose matches on Subject: below --
2024-01-08 10:36 [NTG-context] update Hans Hagen via ntg-context
2023-06-04 17:01 Hans Hagen via ntg-context
2023-04-26 21:55 Hans Hagen via ntg-context
2023-04-26 23:54 ` Jairo A. del Rio via ntg-context
2023-04-27  2:25   ` Rik Kabel via ntg-context
2023-04-27  2:34     ` Jairo A. del Rio via ntg-context
2023-04-27  7:52   ` Hans Hagen via ntg-context
2023-04-27  0:50 ` lynx--- via ntg-context
2023-04-27  1:52   ` Aditya Mahajan via ntg-context
2023-04-27  5:11     ` Max Chernoff via ntg-context
2023-04-27  7:58       ` Hans Hagen via ntg-context
2023-04-27  7:38   ` Hans Hagen via ntg-context
2023-04-27  8:32     ` Max Chernoff via ntg-context
2023-04-27 21:51       ` lynx--- via ntg-context
2023-04-27 23:54         ` Max Chernoff 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=de83f26c-c7dc-4cf1-8ff6-3e973b645b52@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=ntg-context@ntg.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).