From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Alan Braslau <braslau.list@comcast.net>,
"T. Kurt Bond" <tkurtbond@gmail.com>,
Marco Patzer <lists@homerow.info>
Subject: Re: LMTX: different output if dots are used in the file name
Date: Thu, 8 Jul 2021 11:01:54 +0200 [thread overview]
Message-ID: <65448529-40ad-1664-275f-d5fe8a17f362@xs4all.nl> (raw)
In-Reply-To: <20210707122529.7829e517@poo.hsd1.co.comcast.net>
On 7/7/2021 8:25 PM, Alan Braslau wrote:
> Windows, I believe, does not take kindly to filenames containing
> multiple dots.
windowes is very kind to multiple dots but it (normally) sees the last
suffix as an indication of what file is it (other operating system needs
some 'open' command while windows works with associations)
> Therefore, Hans never uses such filenames and does not expect them,
> either, so I am not surprised that this yields unpredictable results.
actually, mkiv will append a suffix for converted files, so foo.eps.pdf
is made ... works ok
> An unfortunate side-effect of dealing with Windows.
more an unfortunate side effect of the way users and porograms construct
filenames and expect systems that use some heuristic to deal with that
to work fine (unless one accepts that foo.tex gets a foo.tex.log and
foo.tex.pdf file as result)
(inconsistent font and file filenames can even make life even more
misserable)
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 9:01 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
2021-07-08 9:01 ` Hans Hagen [this message]
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=65448529-40ad-1664-275f-d5fe8a17f362@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=braslau.list@comcast.net \
--cc=lists@homerow.info \
--cc=ntg-context@ntg.nl \
--cc=tkurtbond@gmail.com \
/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).