[luatex] luaotfload problems (MiKTeX/Windows 7) | not solved

Philipp Gesang Philipp.Gesang at alumni.uni-heidelberg.de
Sat Jul 6 02:27:09 CEST 2013

Hi Reinhard!

···<Datum: Saturday, 06. July 2013>···<Von: Reinhard Kotucha>···

> On 2013-07-05 at 16:29:12 -0400, Evan Cooch wrote:
>  > luaotfload | cache : Could not write lookup cache
>  > luaotfload | cache: Could not write to cache
>  > luaotfload | cache : Could not write to cache [1
> Certainly a problem with file permissions.  Philipp, it would be very
> helpful if luaotfload prints the full path+filename to the log file
> before opening the file.

The filenames are listed with absolute paths when running
luaotfload-tool --help.  Anyways, I just rewrote [1] the writer
functions in question to be more verbose on failure.

>                           "Could not write" can either mean that the
> the target directory isn't writable, but it can also mean that it
> tries to create the file somewhere else.

The strange thing is, though, that the fontloader apparently
writes to the font cache without issue, even though it uses the
exact same mechanism as the database writer ...

> However, file permissions are a pain under Windows.  A colleague has
> two files with the same name but different content in one and the same
> directory.  When he logs in as a mortal user he gets the the older
> version but when he logs in as administrator he gets the newer one.
> These things are extremely difficult to debug.  Good luck!

I’m aware of some but by no means all of the pitfalls. That’s why
luaotfload relies heavily on Hans’s code (tested on Win) for
filesystem related stuff.


[1] https://github.com/phi-gamma/luaotfload/commit/c917abdd4c6032b1e715555bc626a987b014e4ab
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://tug.org/pipermail/luatex/attachments/20130706/b8591f58/attachment-0001.bin>

More information about the luatex mailing list