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: Thu, 8 Jul 2021 15:38:36 +0200 [thread overview]
Message-ID: <20210708153836.10b60c1a@homerow> (raw)
In-Reply-To: <120b57e1-961c-a3fb-3a47-fbef1485cb6b@xs4all.nl>
On Thu, 8 Jul 2021 10:34:32 +0200
Hans Hagen <j.hagen@xs4all.nl> wrote:
> Now, to the issue of names like 10.11.12.13 ... here .13 is the
> suffix, like it or not, so in principle we then get
>
> 10.11.12.log
> 10.11.12.tuc
> 10.11.12.pdf
It's not that I use files without (.tex, .mkiv, ...) suffixes, but
your 10.11.12.13 example is processed by MkIV without problems:
10.11.12.pdf
10.11.12.tua
10.11.12.log
LMTX, however doesn't like it:
10.11.pdf
10.11.tua
10.log
> if not then indeed there is some issue.
According to my tests LMTX doesn't work like you describe it should.
> Now, although it's quite some
> work, one can think of seeing .13 as part of the filename, in which
> case the lookupe becomes
>
> 10.11.12.13.tex
Just to make it clear: I don't use files without .tex/.mkvi/etc.
suffix. So I don't expect 10.11.12.13 to work, but 10.11.12.tex
should in fact work as far as I understand.
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
___________________________________________________________________________________
next prev parent reply other threads:[~2021-07-08 13:38 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
2021-07-08 8:34 ` Hans Hagen
2021-07-08 13:38 ` Marco Patzer [this message]
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=20210708153836.10b60c1a@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).