Given
\newread \standin
\openin \standin = MM3.dat
I had expected XeTeX to open MM3.dat for input — instead, it opened
MM3.dat.tex
Bug or feature ?
--
/Philip Taylor/
feature, and not xetex specific
$ ls MM*
MM3.dat MM3.dat.tex
$ kpsewhich MM3.dat
./MM3.dat.tex
$ kpsewhich --all MM3.dat
./MM3.dat.tex
./MM3.dat
If both are available kpsearch prefers the .tex as shown by the first call
to kpsewhich
David
On Tue, 20 Sept 2022 at 16:40, Philip Taylor (Helle
On 20/09/2022 17:29, David Carlisle wrote:
feature, and not xetex specific
Thank you, David. Evil, nonetheless, and highly counter-intuitive.
--
/** Phil./
Like most things, it's an option see
try_std_extension_first
in section 6.2 of texdoc kpathsea
On Tue, 20 Sept 2022 at 17:33, Philip Taylor (Hellenic Institute) <
p.tay...@hellenic-institute.uk> wrote:
> On 20/09/2022 17:29, David Carlisle wrote:
>
> feature, and not xetex specific
>
> Thank yo
On 20/09/2022 16:38, Philip Taylor (Hellenic Institute) wrote:
Given
\newread \standin
\openin \standin = MM3.dat
I had expected XeTeX to open MM3.dat for input — instead, it opened
MM3.dat.tex
Bug or feature ?
--
/Philip Taylor/
Have you compared other engines? My TL installation is woe
On 20/09/2022 17:36, Jonathan Kew wrote:
Have you compared other engines? My TL installation is woefully
out-of-date, but with the versions I have on hand, I see similar
behavior in tex/pdftex/luatex.
No, I confess that I haven't, Jonathan — XeTeX is the only engine I ever
use, and has been
