[tex-live] fc-cache documentation ?

Philip Taylor P.Taylor at Rhul.Ac.Uk
Mon Sep 5 11:26:23 CEST 2016

Dear Akira-san --

Akira Kakuto wrote:
> It seems that I was wrong:
> By experiments, I found that the renaming,
> cachefile.NEW --> cachefile, almost always
> fails if executed from the XeTeX binary even
> in a user's writable directory. 
Thank you -- further experiments after installing a further new font have indeed shewn this to be the case.  It would also seem that, in my case at least, that I have write access to the default location for FC_CACHEDIR so the effect of explicitly setting that to C:\TeX\Live\2016\FC_cache was to allow the initial creation of a new cache (which of course helped) but did not address the real problem that you have identified with :

#ifdef _WIN32
   unlink ((const char *) atomic->file);
   /* fails always if executed from the XeTeX binary */
> Thus if you find a delay of time, run fc-cache -v.
> If messages
> invalid cache file: ...
> are shown, run
> fc-cache -v
> once more.
Thank you, and noted for future reference.
** Phil.

Philip Taylor
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tug.org/pipermail/tex-live/attachments/20160905/0c34fd94/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Signature.jpg
Type: image/jpeg
Size: 12104 bytes
Desc: not available
URL: <http://tug.org/pipermail/tex-live/attachments/20160905/0c34fd94/attachment-0001.jpg>

More information about the tex-live mailing list