Re: LMTX: different output if dots are used in the file name

[Marco Patzer <lists@homerow.info>]

On Thu, 28 May 2020 17:33:19 +0200
Hans Hagen <j.hagen@xs4all.nl> wrote:

> On 5/28/2020 2:49 PM, Marco Patzer wrote:
> > Hi!
> > 
> > LMTX and MkIV behave differently if dots are used in the file
> > name. Example:
> > 
> >    printf '%s\n' '\starttext\null\stoptext' > foo.10.tex && context
> > foo.10.tex
> > 
> > MkIV: → foo.10.pdf
> > LMTX: → foo.pdf
> > 
> > Is this intentional?  
> 
> consider it to be so

That's unfortunate.

1) The editor workflow with simple suffix replacement .tex → .pdf to
   open the corresponding PDF file doesn't work any more with lmtx.
   New logic is needed to find the correct pdf file name.

2) A project (of mine) that uses item numbers as file names
   (containing dots) compile to the same pdf:

   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.

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