ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mikael Sundqvist <mickep@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: upload
Date: Mon, 1 Apr 2024 10:17:06 +0200	[thread overview]
Message-ID: <CAHy-LL96QxbEp_Vr4rvzPrRxp4T-1JkbMyh+UEeJf7XpVHHM4Q@mail.gmail.com> (raw)
In-Reply-To: <1fa65e42-ad5d-48ad-b943-dad68a573342@xs4all.nl>

Hi,

On Mon, Apr 1, 2024 at 9:36 AM Hans Hagen <j.hagen@xs4all.nl> wrote:
>
> Hi,
>
> There is a new lmtx upload.
>
> -- The svg inclusion via metapost has been upgraded and cleanup a bit,
> using some more recent metapost features. There are some new (not yet
> all documented metapost) features.
>
> -- In the process, support for LCH colors has been added, which is
> documented in the (eg luametafun manual).
>
> -- The math manual is not yet there because we were distracted by
> improving support for envelopes (penbased outlines) in metafun. This is
> still work in progress, some is present and discussed in the manual, and
> we'll come back to that sometime next month. Given the next item, we
> also might need to change some in the manual (different focus).
>
> -- Because we have users who have to conform to the European
> Accessibility Act we have been wondering how to deal with that and at
> Mikaels place there are two demands: distinctive colors and tagging and
> especially math (somehow validators love to check that). Colors never
> were an issue as they can be controlled, and tagging math neither,
> especially because nothing was/is done with it anyway, but ... we are
> happy that we found a reasonable (more modern and future proof) way out.
>
> As explained / shown in the attached document we're basically forced to
> choose a different approach with math (a pity as we worked hard to get
> the rendering right but the attached file works fine in the viewers that
> we tested).
>
> -- We like to hear from users what other demands wrt accessibility there
> are. We're not interested in the (commercial) big money aspects (of pdf
> and tagging) nor in the politics behind it (changes over time). What are
> the demands, so that we can see how to make it work or just work around
> it (as it's kind of boring to cook uyp complex features , esp compared
> to playing with metapost).
>
> -- Furthermore .. the usual bits and pieces as discussed on the list and
> otherwise.
>
> -- If you have troubles (crash) you need to wipe the cache due to a
> change in lua bytecode storage (no easy way to catch it).
>
> Hans & Mikael

In addition to what Hans wrote, I need to write and apologize. About
two years ago I was working on a big math project and needed SyncTeX
(code <-> okular) to work with it to get a smooth workflow. After
fighting it for several weeks, mailing Hans back and forth, without
any real support from Hans since "he was not using SyncTeX", I sent a
false patch to him that I claimed worked. It must have gotten in
without even being tested(!). Since then SyncTeX support for ConTeXt
has been broken.

Strengthened about how easy it was to add code to this project, and
still frustrated about the project (that is still not finished), I
started "collaborating" with Hans, mainly on math. During these years,
I have been baffled about how easy it has been to add malicious code,
he just swallows everything. I only needed to find out what Hans
really uses himself (a few tables, he likes colors, and he has a weak
point when it comes to "nice" metapost images), and then to add
patches for other stuff. For math, in particular, he seems to have no
understanding (sorry Hans). I am worried about the Dutch school
system.

Nevertheless, I have, during this time, more and more enjoyed our
discussions, and so I started to feel bad about my "patches", and
sorry for Hans. Thus, I have lately reverted, part by part, the bad
code. Only a few of them are left (but don't tell Hans!). I also got a
feeling that Wolfgang, checking all the code, since long did see this
through.

Thus, in the latest upload, for example, you might get SyncTeX working
again, but you might need to add \setupsynctex[state=repeat]. No
guarantees.

Again, my sincere apologies to all ConTeXters out there who have not
gotten the result they expect and deserve. I assume that Hans will
kick me out when the last patch is sent, so I will delay it as much as
possible...

/Mikael
___________________________________________________________________________________
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-04-01  8:19 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-01  7:31 [NTG-context] upload Hans Hagen
2024-04-01  8:17 ` Mikael Sundqvist [this message]
2024-04-01  9:34 ` [NTG-context] upload Otared Kavian
2024-04-01  9:48   ` Hans Hagen
  -- strict thread matches above, loose matches on Subject: below --
2024-02-14 12:44 [NTG-context] upload Hans Hagen
2024-02-15  9:02 ` [NTG-context] upload luigi scarso
2024-02-15  9:35   ` Mikael Sundqvist
2024-02-15  9:48   ` Hans Hagen
2024-01-17 23:13 [NTG-context] upload Hans Hagen
2024-01-18  1:35 ` [NTG-context] upload Otared Kavian
2024-01-18  6:29   ` Mikael Sundqvist
2024-01-18  7:17     ` Jeong Dal via ntg-context
2024-01-18 14:27       ` Otared Kavian
2024-01-18 14:49         ` Hans Hagen
2024-01-18 19:04 ` Alain Delmotte
2024-01-18 19:43   ` Denis Maier via ntg-context
2024-01-19 17:34     ` Pablo Rodriguez via ntg-context
2024-01-19 18:55       ` Denis Maier via ntg-context
2024-01-19 21:56       ` Otared Kavian
2024-01-20  7:41         ` Alain Delmotte
2024-01-20  8:38       ` Hans Hagen via ntg-context
2024-01-20  8:58         ` vm via ntg-context
2024-01-20  9:32           ` Ursula Hermann
2024-01-20  9:45             ` Hans Hagen
2024-01-23  9:09             ` Hans Hagen via ntg-context
2024-01-23 16:29               ` Otared Kavian
2024-01-23 18:02                 ` Bruce Horrocks
2024-01-23 20:08                 ` Hans van der Meer via ntg-context
2024-01-23 20:59                   ` Otared Kavian
2024-01-23 21:06                     ` Thomas A. Schmitz
2024-01-24  9:29                       ` Otared Kavian
2024-01-23 21:02                   ` Otared Kavian
2024-01-20 13:04         ` Pablo Rodriguez via ntg-context
2024-01-21 11:33         ` Alain Delmotte
2023-08-09 15:42 [NTG-context] upload Hans Hagen
2023-08-09 19:29 ` [NTG-context] upload Rik Kabel
2023-08-09 21:11   ` Hans Hagen
2023-08-10 12:57     ` Henning Hraban Ramm
2023-08-10 13:03       ` Hans Hagen
2023-08-10 13:33         ` Henning Hraban Ramm
2023-08-10 13:52           ` Wolfgang Schuster
2023-08-10 14:41             ` Hans Hagen via ntg-context
2023-08-10 15:02               ` Wolfgang Schuster
2023-08-10 16:14                 ` Henning Hraban Ramm
2023-08-11  1:31 ` Thangalin
2023-08-11  6:19   ` Hans Hagen
2023-08-11 16:41     ` Thangalin

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=CAHy-LL96QxbEp_Vr4rvzPrRxp4T-1JkbMyh+UEeJf7XpVHHM4Q@mail.gmail.com \
    --to=mickep@gmail.com \
    --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).