From: Joseph Wright <joseph.wright@morningstar2.co.uk>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: Why LuaMetaTex is so slow?
Date: Thu, 18 Jan 2024 21:33:04 +0000 [thread overview]
Message-ID: <1f063907-bb6e-4698-8b9c-c9dc074ac2bb@morningstar2.co.uk> (raw)
In-Reply-To: <729BA5F9-953E-4AAD-A9A0-92272BD0A54B@icloud.com>
On 18/01/2024 20:55, Gavin via ntg-context wrote:
> That’s fast enough for me.
That's surely the key statement - 'fast' here is a personal thing, and
40 pages a second is fast enough for many people. It's certainly fast
when you look at what LuaMetaTeX is doing, as Hans has said.
Joseph
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2024-01-18 21:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 17:24 [NTG-context] " Shiv Shankar Dayal
2024-01-18 17:47 ` [NTG-context] " Pablo Rodriguez via ntg-context
2024-01-18 18:40 ` Henning Hraban Ramm
2024-01-18 18:56 ` Shiv Shankar Dayal
2024-01-18 19:08 ` Mikael Sundqvist
2024-01-18 19:31 ` Hans Hagen
2024-01-18 23:34 ` Aditya Mahajan
2024-01-19 0:09 ` Hans Hagen via ntg-context
2024-01-19 0:33 ` Aditya Mahajan
2024-01-19 8:51 ` Hans Hagen
2024-01-18 22:15 ` Bruce Horrocks
2024-01-19 9:31 ` Hans Hagen
2024-01-19 10:00 ` Henning Hraban Ramm
2024-01-19 10:35 ` Taco Hoekwater
2024-01-19 10:49 ` Hans Hagen
2024-01-19 18:13 ` Bruce Horrocks
2024-01-19 18:30 ` Hans Hagen
2024-01-18 20:55 ` Gavin via ntg-context
2024-01-18 21:33 ` Joseph Wright [this message]
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=1f063907-bb6e-4698-8b9c-c9dc074ac2bb@morningstar2.co.uk \
--to=joseph.wright@morningstar2.co.uk \
--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).