ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Henning Hraban Ramm <texml@fiee.net>
Subject: Re: [NTG-context] new units
Date: Sun, 7 May 2023 11:10:39 +0200	[thread overview]
Message-ID: <62e368a7-9883-113e-a2eb-ee0089b5e188@fiee.net> (raw)
In-Reply-To: <e2714c76-61ea-dddb-1f8d-d695b9f8cbad@xs4all.nl>

Am 04.05.23 um 10:01 schrieb Hans Hagen via ntg-context:
> Hi,
> 
> We now officially have three new units. These were officially introducd 
> at the 2023 BachoTeX meeting in a presentation where the chair of the 
> four person strong team also did the final live callibration (using the 
> edithorial callibration instrument made for that purpose). An upcoming 
> article in TB will explain the details of the process and also a careful 
> mathematical annalysis of how we reached the right value with a high 
> precission. The actual implementation is the most boring part.

Hi Hans, can I have the article also for CGJ, please?

I didn’t understand all details, and I guess some spelling errors are 
intentional – was there a Calli? Does “precission” refer to anything? 
And what’s the abbreviation for Theodores?

Hraban

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

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2023-05-07  9:12 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04  8:01 Hans Hagen via ntg-context
2023-05-06 16:45 ` Alan Braslau via ntg-context
2023-05-06 19:40   ` Hans Hagen via ntg-context
2023-05-06 21:53 ` Arthur Rosendahl via ntg-context
2023-05-06 23:29   ` Hans Hagen via ntg-context
2023-05-07  9:10 ` Henning Hraban Ramm via ntg-context [this message]
2023-05-07  9:29   ` Mojca Miklavec via ntg-context
2023-05-07 10:04     ` Hans Hagen via ntg-context
2023-05-07 10:06     ` Hans Hagen via ntg-context
2023-05-07  9:45   ` Hans Hagen via ntg-context
2023-05-07 10:09     ` Henning Hraban Ramm via ntg-context
2023-05-07 10:29       ` Hans Hagen via ntg-context
2023-05-07 15:56         ` Henning Hraban Ramm via ntg-context
2023-05-07 14:56       ` Hans Hagen via ntg-context
2023-05-07 12:00     ` Bruce Horrocks via ntg-context
2023-05-07 13:07       ` Hans Hagen via ntg-context
2023-05-07 15:58       ` Alan Braslau via ntg-context
2023-05-07  0:10 skyhorse--- via ntg-context
2023-05-07  2:43 ` Michael Urban via ntg-context
2023-05-07  6:09   ` Mikael Sundqvist via ntg-context
2023-05-07  8:15   ` Hans Hagen via ntg-context
2023-05-07  2:51 ` Alan Braslau via ntg-context
2023-05-07  8:22 ` Hans Hagen 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=62e368a7-9883-113e-a2eb-ee0089b5e188@fiee.net \
    --to=ntg-context@ntg.nl \
    --cc=texml@fiee.net \
    /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).