> 
> even though somewhere along between the release of 2023 and shortly after, 
> some more changes took shape reflecting I presume, the aformentioned issue to 
> have such an option as KpseOny. And there we go! The whole story repeated 
> itself again with changing certain parts of the document to accomodate 
> whatever the modifications that took effect and were coming from the engines.
> 
> But I also remember that something happened. The Extension had to be thus, 
> specified. Not so much as an option but also for every font or for the whole 
> family such as {fontname.otf} or individually 
> 
> e.g one could have \setmainfont[whateveroption=font.extension]{font} or 
> \setmainfont[whateveroption=font]{font.extension} 

Fe de errata here. 

e.g one could have \setmainfont[whatevervariant=font.extension]{font} or 
\setmainfont[whatevervariant=font]{font.extension} 
> 
> Now both XeTeX (v3.14) and LuaTeX (v1.18) only undertand the path of system 
> fonts such as /usr/share/ and /usr/local/share or whatever the path happens 
> to be to find them. There's no room to have any engine work successfully for 
> a lookup under kpathsea or wherever the variable texmflocal points to. Nope. 
> not such a thing.
> 
> 
> -- 
> 
> 

-- 

Reply via email to