LATEX-L Archives

Mailing list for the LaTeX3 project


Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender: Mailing list for the LaTeX3 project <[log in to unmask]>
Date: Sat, 29 Jul 2023 13:21:22 +0200
Content-Disposition: inline
Reply-To: Mailing list for the LaTeX3 project <[log in to unmask]>
MIME-Version: 1.0
Message-ID: <[log in to unmask]>
In-Reply-To: <[log in to unmask]>
Content-Type: text/plain; charset=us-ascii
From: LARONDE Thierry <[log in to unmask]>
Parts/Attachments: text/plain (34 lines)
On Sat, Jul 29, 2023 at 01:09:21PM +0200, Ulrike Fischer wrote:
> Am Sat, 29 Jul 2023 12:12:12 +0200 schrieb LARONDE Thierry:
> > OK, let's go to "TeX: The Program": m.537 (p 214):
> Your concrete problem is not the implementation of \input, your
> problem is that your implementation of \pdffilesize (which by the
> way is not mentioned in "TeX: The Program") doesn't use the same
> method to find a file as your \input/\openin. 
> It is  -- as David already wrote -- quite a problem if "\pdffilesize
> filename" reports a size that differs from the size of the file that
> is input with "\input filename". 
> It doesn't make much sense therefore to muse on if or if not the
> current engines implement exactly what "TeX: The Program" says. 
> Simply get \pdffilesize etc in sync with \input, \openin etc.

But this is exactly my question: is it enough for LaTeX? Because I don't
want to have user reporting failure in a couple of weeks because LaTeX
is leveraging another feature that I don't know about and having to go
back modifying things.

So: I will make the new file primitives behaving like \input. But this
does mean that it is not possible for these primitives to deal with a
filename without extension.

Is it OK or not?
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C