ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Marco Patzer <lists@homerow.info>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: LMTX: different output if dots are used in the file name
Date: Wed, 7 Jul 2021 22:13:06 +0200	[thread overview]
Message-ID: <20210707221306.292ac550@homerow> (raw)
In-Reply-To: <20210707122529.7829e517@poo.hsd1.co.comcast.net>

On Wed, 7 Jul 2021 12:25:29 -0600
Alan Braslau <braslau.list@comcast.net> wrote:

Thank you for your reply.

> Windows, I believe, does not take kindly to filenames containing
> multiple dots.

Disclaimer: I don't use Windows, I know nothing about Windows. But I
downloaded a Windows 10 VM and fired it up, installed LMTX, created
a file (in the default editor):

  # file name: 10.10.10.tex
  \starttext
  foo
  \stoptext

Then I ran

install.bat
setpath.bat

# LMTX
context 10.10.10.tex
  → 10.10.pdf
  → 10.log

# MkIV
context --luatex 10.10.10.tex
  → 10.10.10.pdf
  → 10.10.10.log

So I can't confirm your findings. MkIV works exactly the same on a
vanilla Windows 10 VM than it does on a Unix system and produces
correct output files with multiple dots. No issues there.

> Therefore, Hans never uses such filenames and does not expect them,
> either, so I am not surprised that this yields unpredictable results.
> 
> An unfortunate side-effect of dealing with Windows.

My short test above seems to suggest that it's not an OS issue since
Unix and Windows behave exactly the same. MkIV (which seems to work
fine on Windows) as well as the LMTX issue. But maybe I did
something wrong there, in that case please let me know.

And Hans said “I'll look at it” a while back, so I just wanted to
send a reminder.

Since it worked in MkIV it looks like a regression. I mean it used
to work. Several of my projects rely on source files with multiple
dots. I know it's not common to have multiple dots, but I hope
there's chance it might be fixed.

But maybe Hans can chime in and clarify.

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
___________________________________________________________________________________

  parent reply	other threads:[~2021-07-07 20:13 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
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 [this message]
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=20210707221306.292ac550@homerow \
    --to=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).