From: Hans Hagen <j.hagen@xs4all.nl>
To: Marco Patzer <lists@homerow.info>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: LMTX: different output if dots are used in the file name
Date: Fri, 29 May 2020 09:48:00 +0200 [thread overview]
Message-ID: <2f2ebdf7-e152-4ec4-4236-2594f1d9603f@xs4all.nl> (raw)
In-Reply-To: <20200528203139.2459c3b8@homerow>
On 5/28/2020 8:31 PM, Marco Patzer wrote:
> On Thu, 28 May 2020 18:18:51 +0200
> Hans Hagen <j.hagen@xs4all.nl> wrote:
>
>>> MkIV (everything's predictable and fine):
>>> 10.10.10.tex → 10.10.10.pdf
>>> 10.10.11.tex → 10.10.11.pdf
>>> 11.10.11.tex → 11.10.11.pdf
>>>
>>> LMTX:
>>> 10.10.10.tex → 10.10 (not even a PDF suffix)
>>> 10.10.11.tex → 10.10 (file 10.10 is over-written)
>>> 11.10.11.tex → 11.10 (no suffix)
>>>
>>> MkIV is way more predictable and consistent in that regard.
>> I'll look at it but not today ... first I need to play with some
>> other (neat) stuff and run tests.
>
> OK, thanks. No hurry. The production projects run on some oldish
> 2019 MkIVs anyway. I'm trying to get my feet wet with lmtx and run
> it on some projects to check how usable and compatible it is.
It should be compatible, although at some point there will be
functionality that is only in lmtx. Okay, metapost is an exception,
because there is a lot in lmtx that is not in mkiv, but that's a
separate subsystem anyway.
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 prev parent reply other threads:[~2020-05-29 7:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 12:49 Marco Patzer
2020-05-28 15:33 ` Hans Hagen
2020-05-28 15:59 ` Marco Patzer
2020-05-28 16:18 ` Hans Hagen
2020-05-28 18:31 ` Marco Patzer
2020-05-29 7:48 ` Hans Hagen [this message]
2021-07-06 20:43 ` Marco Patzer
2021-07-07 0:08 ` T. Kurt Bond
2021-07-07 18:25 ` Alan Braslau
2021-07-07 19:57 ` Ulrike Fischer
2021-07-08 18:13 ` Alan Braslau
2021-07-08 19:34 ` Hans Hagen
2021-07-07 20:13 ` Marco Patzer
2021-07-08 8:34 ` Hans Hagen
2021-07-08 13:38 ` Marco Patzer
2021-07-08 23:07 ` Hans Hagen
2021-07-08 9:01 ` Hans Hagen
2020-05-28 16:07 ` Marco Patzer
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=2f2ebdf7-e152-4ec4-4236-2594f1d9603f@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=lists@homerow.info \
--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).