Using fonts from the LaTeX Font Catalogue
Paulo Ney de Souza
pauloney at gmail.com
Sat May 8 00:55:44 CEST 2021
On Fri, May 7, 2021 at 3:43 PM David Carlisle <d.p.carlisle at gmail.com>
wrote:
>
> On Fri, 7 May 2021 at 22:47, Reinhard Kotucha <reinhard.kotucha at web.de>
> wrote:
>
>> On 2021-05-07 at 21:12:44 +0200, Ulrike Fischer wrote:
>>
>> Ulrike, this is easier said than done. The installer doesn't know
>> where fontconfig files are located and deriving it from fc-conflist
>> isn't sufficient either. There is no fontconfig directory in the
>> user's HOME directory by default and the one in /etc is not writable
>> by mortal users. The only reliable solution is to give some hints in
>> the documentation.
>>
>> Regards,
>> Reinhard
>>
>
> That is true but.... How feasible would it be to not configure fontspec to
> look in the telive tree and instead use a kpathsearch aliases file?
> That was originally because someone was mad enough to name the longtable
> package with more than 8 letters but could we re-write
> texmf-var/luatex-cache/generic/names/luaotfload-lookup-cache.lua
> in that format so kpathsea can find the fonts using their internal font
> names?
>
> David
>
This is an important issue because releasing such an amount of fonts on a
system is not an unconsequential move. I do remember that a couple of
releases ago, the fc-cache move would break Evince display due to similarly
named, but distinct fonts.
Paulo Ney
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://tug.org/pipermail/texhax/attachments/20210507/e5d351c8/attachment.html>
More information about the texhax
mailing list.