kberry

That would be a good improvement. But I was thinking of something even stronger: make kpseonly the default behavior when filename lookups are requested. Why would I want system fonts...

Marcel - As far as I know, the only way fontspec provides (documents) to specify a filename lookup is by specifying a filename (foo.otf, Path=, etc.). If that syntax also...

Karl I find your terminology confusing here, I find your confusion confusing! A filename lookup uses the system filename of the font file I don't know what the "system filename...

Marcel - thanks for all the information. I forgot that luatex does not use fontconfig, only xetex does, so all that was off the mark. Sorry. dc> I meant just...

I hope "I won't change anything now" doesn't mean you don't consider any of this a bug?

The sad story continues. First of all, with {LucidaBrightOT}, it reads lucidabrightot.fontspec, but maybe those definitions don't take effect and it is still using system fonts? That would make sense,...

Second, the mac people are saying the .fontspec file is only found if the case matches, LucidaBrightOT.fontspec. And I see now that the doc actually says that. But, this requirement...

For the (long and confusing) thread about this: https://tug.org/pipermail/lucida/2019-January/000778.html I hope you will have time to look into this and keep the things that have always worked still working. I...

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...

xetex uses fontconfig on every platform except Macs. As for real names ... well, they are just wrong :).