From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Marco Patzer <lists@homerow.info>
Subject: Re: LMTX: different output if dots are used in the file name
Date: Fri, 9 Jul 2021 01:07:08 +0200 [thread overview]
Message-ID: <800c79a2-7374-7c64-0ce4-5bea41d53233@xs4all.nl> (raw)
In-Reply-To: <20210708153836.10b60c1a@homerow>
On 7/8/2021 3:38 PM, Marco Patzer wrote:
> 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
actually that's also not ok as it should be a .tuc file
> 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.
i'll check it
(in retrospect tex could better have enforced a suffix and not fallback
on .tex but i suppose the usage scenarios were hard to foresee let alone
the restart-the-program-time-penalty when you forgot to add .tex)
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:[~2021-07-08 23:07 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
2021-07-08 23:07 ` Hans Hagen [this message]
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=800c79a2-7374-7c64-0ce4-5bea41d53233@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).