ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: lmtx
Date: Thu, 12 Dec 2019 07:04:58 +0100	[thread overview]
Message-ID: <6E742C4F-B37B-4FC1-AB26-9D6BDAC5B7BE@gmail.com> (raw)
In-Reply-To: <20E14EC8-2BED-4DD6-989C-B6CA1453BFB1@gmail.com>

Actually I did the update with a new install.sh downloaded from Pragma's site, but in fact I got again the older version 2019.12.06 21:40…
So the issues I was reporting concern 2019.12.06 21:40 version.

> On 12 Dec 2019, at 06:28, Otared Kavian <otared@gmail.com> wrote:
> 
> Hi Hans,
> 
> Thank you for the new beta. I tested a few things and they work nicely as expected. 
> 
> However I would like to ask you to put back into lmtx the nice error messages handling we had in early November: now when there is an error it is impossible to locate it and the file filename-status.html contains nothing (though the colored « error » pdf produced is nice looking…).
> In early November the error messages were very precise and the file filename-status.html was very helpful.
> 
> There is also an issue in lmtx (since the version 2019.12.06, including the latest) where in some situations using \startitemize... \stopitemize produces some garbled items and some numbered items completely disappear. I could not make a minimal example, but I can send you the PDF which shows the issue.
> 
> Many thanks, and best regards: OK
> 
> 
>> On 12 Dec 2019, at 01:37, Hans Hagen <j.hagen@xs4all.nl> wrote:
>> 
>> Hi,
>> 
>> The last few days there have been reports about garbled files in the lmtx installation so I did some test oinon a linux machine and indeed there was some issue (I'm not sure what causes it). Anyway, I made new zips so maybe one needs to reinstall (using the installer zip). It installs okay on wsl so probably also on other linuxes.
>> 
>> This version (luametatex 2.03.3) has (again) a little smaller mem footprint as I still want it all to perforem ok on relative small devices or vm's and as side effect a bit smaller format file, not that that matters much (compared to general mem usage). There is not much to gain anyway, in terms of memory usage and performance so it's more an occasional challenge than a neccessity I guess.
>> 
>> Anyway, hopefully nothing got broken. Peter Rolf and I are updating some of the pdf validation related stuff (additional formats), so that can be in flux.
>> 
>> 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
>> ___________________________________________________________________________________
> 

___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2019-12-12  6:04 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-12  0:37 lmtx Hans Hagen
2019-12-12  5:28 ` lmtx Otared Kavian
2019-12-12  6:04   ` Otared Kavian [this message]
2019-12-12 10:08   ` lmtx Hans Hagen
2019-12-12  6:36 ` lmtx Richard Mahoney | Indica et Buddhica
2019-12-12 16:59 ` lmtx Pablo Rodriguez
2019-12-12 20:13   ` lmtx Pablo Rodriguez
  -- strict thread matches above, loose matches on Subject: below --
2022-02-03 21:00 lmtx Hans Hagen via ntg-context
2021-02-19 12:32 lmtx Hans Hagen
2021-01-18 18:20 lmtx Hans Hagen
2021-01-19 10:57 ` lmtx Floris van Manen
2021-01-19 11:10   ` lmtx Hans Hagen
2021-01-19 11:31     ` lmtx Jano Kula
2021-01-19 19:12 ` lmtx Jan U. Hasecke
2021-01-19 23:03   ` lmtx Hans Hagen
2020-10-30 22:29 lmtx Hans Hagen
2020-10-31  2:50 ` lmtx Jairo A. del Rio
2020-11-02 19:43   ` lmtx Hans Hagen
2020-06-19 10:11 lmtx Hans Hagen
     [not found] <mailman.1.1576234801.28358.ntg-context@ntg.nl>
2019-12-13 19:29 ` lmtx Jeong Dal
     [not found] <mailman.310.1576128525.1207.ntg-context@ntg.nl>
2019-12-12 23:48 ` lmtx Jeong Dal
2019-12-13  8:39   ` lmtx Otared Kavian
2019-08-05 12:38 lmtx Hans Hagen
2019-04-02  9:05 lmtx Hans Hagen
2019-04-02 19:03 ` lmtx Taco Hoekwater
2019-04-02 20:11 ` lmtx Henri Menke
2019-04-02 20:19   ` lmtx Hans Hagen
2019-04-02 20:30     ` lmtx Henri Menke
2019-04-02 20:47       ` lmtx Hans Hagen

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=6E742C4F-B37B-4FC1-AB26-9D6BDAC5B7BE@gmail.com \
    --to=otared@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).