From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: lmtx update
Date: Thu, 19 Aug 2021 19:57:19 +0200 [thread overview]
Message-ID: <f3fc9ab5-3ef0-fae0-5a96-bbc32a41fe88@xs4all.nl> (raw)
Hi,
Here are the highlights of todays update:
- somewhat more compact tuc files, not for all documents, but it can
accumulate; also less memory used then; i could bring down an extreme
2000 page 5 column doc tuc file down to 5% -- it was 70 MB; for the
luametatex manual it reducec the tuc more than 30%; hard to tell if
there will be an associated performance hit, but i'm sure thomas will
complain if that's the case
- more mp-tex-lua interfacing upgraded plus extra preliminary chapter
for luametafun about extensions - for taco
- a slightly more compact cache files for fonts with many (pseudo)
ligatures; hopefully no side effects (nothing that can't be fixed fast
if noted); quite probably no performance hit and maybe even some room
for optimization (not done yet)
- a split in the cache directory for luametatex so that we can more
easilly experiment without interference (so, although the above works in
mkiv it's not enabled there currently)
- some minor things (also in the process of splitting the codebase)
- no real changes in / additions to the luametatex binary (we're in
cosmetics mode now)
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 / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2021-08-19 17:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 17:57 Hans Hagen via ntg-context [this message]
2021-08-19 20:07 ` Aditya Mahajan via ntg-context
2021-08-20 5:52 ` Hans Hagen via ntg-context
-- strict thread matches above, loose matches on Subject: below --
2023-02-06 17:21 Hans Hagen via ntg-context
[not found] <mailman.0.1629453601.23792.ntg-context@ntg.nl>
2021-08-22 22:55 ` Benjamin Buchmuller via ntg-context
2021-08-23 6:21 ` Hans Hagen via ntg-context
2020-09-16 15:52 ebohoyod
2020-09-16 16:23 ` Wolfgang Schuster
[not found] ` <6f2953c3-4b09-e824-da78-46347ef5f4af@disroot.org>
2020-09-17 8:14 ` Eduardo Bohoyo
2020-09-17 10:35 ` Wolfgang Schuster
2020-09-17 10:50 ` Eduardo Bohoyo
2020-09-17 11:11 ` Eduardo Bohoyo
2020-07-31 8:32 Hans Hagen
2020-07-31 8:40 ` Taco Hoekwater
2020-07-31 10:18 ` Hans Hagen
2020-08-01 13:20 ` Otared Kavian
2020-08-01 14:17 ` Hans Hagen
2020-08-01 16:20 ` Otared Kavian
2020-08-01 16:41 ` Henning Hraban Ramm
2020-08-01 16:57 ` Otared Kavian
2020-08-02 3:30 ` Aditya Mahajan
2020-08-03 17:37 ` Pablo Rodriguez
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=f3fc9ab5-3ef0-fae0-5a96-bbc32a41fe88@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.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).