Open wspr opened 4 years ago
Isn't this only an issue if you haven't configured fontconfig to look in the texlive fonts area?
XeTeX itself can tell FontConfig to look into additional font directories without user action, though I hesitated doing this when I was still working on XeTeX as TeX Live often include multiple version of the same font (e.g. TrueType, OpenType and/or Type 1 versions) and which version FontConfig would end up picking did not seem to be very defined.
Using fontconfig makes a document completely unportable and unreliable wrt fonts chosen. I can't tell you how much time I've lost because of this. So I give +1 to Will's original idea, although I admit I've never needed any kind of fallback like "mktexxefont" or something; when a font lookup fails, I need to fix it in the document.
Doesn't XeTeX only use fontconfig on certain platforms? I've never come across it on a Mac.
@kberry — I'm 100% with you, but for some reason people REALLY LIKE using a font's real name :)
xetex uses fontconfig on every platform except Macs.
As for real names ... well, they are just wrong :).
Description
XeTeX can only look up fonts in a texmf tree by filename, and when it fails then looks to Metafont to fill the gaps, which it can never do obviously. It would actually be quite sensible to patch the XeTeX engine to allow the fallback here to run some other script instead to make it all work...
Check/indicate