Sujet : Re: aunclfamily and fontspec
De : ram (at) *nospam* zedat.fu-berlin.de (Stefan Ram)
Groupes : comp.text.texDate : 24. Jul 2024, 11:50:30
Autres entêtes
Organisation : Stefan Ram
Message-ID : <files-20240724104713@ram.dialup.fu-berlin.de>
References : 1 2 3 4 5
Jens-Olaf Lindermann <
j.lindermann@fu-berlin.de> wrote or quoted:
Then you (should) get "No file B1lmr.fd".
Correct. I get this message.
(Windows folks, the next paragraph's your jam.
Linux gang, you'll want to chew on both of these nuggets.)
When you're in a pickle like that on Windows, firing up "Procmon"
can be a real lifesaver. Just filter for processes with "tex"
in the image name, and bam - you'll see exactly where the program's
sniffing around for files. Then it's a cinch to drop the file
right where it needs to be.
For the Linux crowd, you *might* be able to pull off something
similar by running "strace -ff -o textrace <texcommandline>".
That'll spit out some "textrace" files that *might* clue you
in, but I'm not gonna lie, I'm out of my depth on that one.
It's about as clear to me as the fog rolling into the Bay!