{"action":"created","issue":{"url":"https://api.github.com/repos/lualatex/luaotfload/issues/313","labels_url":"https://api.github.com/repos/lualatex/luaotfload/issues/313/labels{/name}","comments_url":"https://api.github.com/repos/lualatex/luaotfload/issues/313/comments","events_url":"https://api.github.com/repos/lualatex/luaotfload/issues/313/events","html_url":"https://github.com/lualatex/luaotfload/issues/313","id":123229182,"number":313,"title":"luaotfload | load : path lookup unsuccessful","user":{"login":"simifilm","id":208344,"avatar_url":"https://avatars.githubusercontent.com/u/208344?v=3","gravatar_id":"","url":"https://api.github.com/users/simifilm","html_url":"https://github.com/simifilm","followers_url":"https://api.github.com/users/simifilm/followers","following_url":"https://api.github.com/users/simifilm/following{/other_user}","gists_url":"https://api.github.com/users/simifilm/gists{/gist_id}","starred_url":"https://api.github.com/users/simifilm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/simifilm/subscriptions","organizations_url":"https://api.github.com/users/simifilm/orgs","repos_url":"https://api.github.com/users/simifilm/repos","events_url":"https://api.github.com/users/simifilm/events{/privacy}","received_events_url":"https://api.github.com/users/simifilm/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-12-21T08:13:56Z","updated_at":"2015-12-28T12:11:24Z","closed_at":"2015-12-22T05:27:40Z","body":"This isn't really a bug, but something I just don't understand. I already posted this [tex.stackechange](http://tex.stackexchange.com/questions/283884/luaotfload-load-path-lookup-unsuccessful), but got no answer so far.\r\n\r\nWhen I typeset documents with `LuaLaTeX` and OpenType fonts I regularly get messages like this in the `.log` file\r\n\r\n     luaotfload | load : path lookup of \"Palatino Linotype.ttf\" unsuccessful,      \r\n     falling back to file:(compiling luc: /usr/local/texlive/2015/texmf-var/luatex-cache/generic/fonts/otf/palatino-linotype.luc)(compiling luc:      \r\n     /Users/simi/Library/texlive/2015/texmf-var/luatex-cache/generic/fonts/otf/palatino-linotype.luc)(save: \r\n     /Users/simi/Library/texlive/2015/texmf-var/luatex-cache/generic/fonts/otf/palatino-linotype.lua)(save: \r\n     /Users/simi/Library/texlive/2015/texmf-var/luatex-cache/generic/fonts/otf/palatino-linotype.luc)\r\n     luaotfload | load : path lookup of \"Palatino Linotype.ttf\" unsuccessful, falling back to file: \\g__fontspec_family_PalatinoLinotype_int=\\count161\r\n     luaotfload | load : path lookup of \"PalatinoLinotype.ttf\" unsuccessful, falling back to file:(compiling luc: /usr/local/texlive/2015/texmf-var/luatex-cache/generic/fonts/otf/palatinolinotype.luc)(compiling luc: \r\n     /Users/simi/Library/texlive/2015/texmf-var/luatex-cache/generic/fonts/otf/palatinolinotype.luc)(save: /Users/simi/Library/texlive/2015/texmf-var/luatex-cache/generic/fonts/otf/palatinolinotype.lua)(save: /Users/simi/Library/texlive/2015/texmf-var/luatex-cache/generic/fonts/otf/palatinolinotype.luc)\r\n     luaotfload | load : path lookup of \"PalatinoLinotype.ttf\" unsuccessful, falling back to file:\r\n\r\nThere are several strange things about this:\r\n\r\n- `LuaLaTeX` does actually compile the document with the defined font. Typesetting doesn't fail (which it normally does if `fontspec` fails to find a font).\r\n- `/usr/local/texlive/2015/texmf-var/luatex-cache/generic/fonts/otf/palatino-linotype.luc` which is given as first fallback, doesn't exist.\r\n- `/Users/simi/Library/texlive/2015/texmf-var/luatex-cache/generic/fonts/otf/palatino-linotype.luc` does exist, but it looks like it's recreated every time. At least, when I delete this directory before the `LuaLaTeX` run, it gets recreated.\r\n- In the last part of this error message, simply no path is given, it just says `falling back to file:`\r\n\r\nContrary to the errors given, `LuaLaTeX/luaotfload` actually *does* seem to find the needed font file. So what is the meaning of this message then?"},"comment":{"url":"https://api.github.com/repos/lualatex/luaotfload/issues/comments/167554448","html_url":"https://github.com/lualatex/luaotfload/issues/313#issuecomment-167554448","issue_url":"https://api.github.com/repos/lualatex/luaotfload/issues/313","id":167554448,"user":{"login":"phi-gamma","id":1437713,"avatar_url":"https://avatars.githubusercontent.com/u/1437713?v=3","gravatar_id":"","url":"https://api.github.com/users/phi-gamma","html_url":"https://github.com/phi-gamma","followers_url":"https://api.github.com/users/phi-gamma/followers","following_url":"https://api.github.com/users/phi-gamma/following{/other_user}","gists_url":"https://api.github.com/users/phi-gamma/gists{/gist_id}","starred_url":"https://api.github.com/users/phi-gamma/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/phi-gamma/subscriptions","organizations_url":"https://api.github.com/users/phi-gamma/orgs","repos_url":"https://api.github.com/users/phi-gamma/repos","events_url":"https://api.github.com/users/phi-gamma/events{/privacy}","received_events_url":"https://api.github.com/users/phi-gamma/received_events","type":"User","site_admin":false},"created_at":"2015-12-28T12:11:24Z","updated_at":"2015-12-28T12:11:24Z","body":"···<date: 2015-12-21, Monday>···<from: Simon Spiegel>···\n> Does the closing of the bug mean that there's no intention of\n> improving these messages? I think they're really not very\n> helpful, at the moment.\n\nThere’s another item pending:\n\n    https://github.com/lualatex/luaotfload/issues/263\n\nThis is closely related since the ``anon`` style lookup is how\nmost accesses by Fontspec are handled. The goal is to provide\na mechanism that resembles Xetex’s by default but can be\nconfigured by the user. (Giving preference to path lookups is a\nhorrible mess IMO so we should at least provide means to opt out\nof it.)\n\nI expect the status messages to change in the course of this\nplanned overhaul but ATM I can’t say exactly when it’ll be ready.\n\n>                         As the lack of reaction on\n> tex.stackexchange indicates, no one really seems to know what\n> they mean.\n\nI’d supply some reaction if that idiotic forum software would\nstop treating me as a robot. The issue has been known for over a\nyear:\n\n    http://meta.tex.stackexchange.com/questions/4410\n\nwithout anyone showing the willingness to fix it. In any case,\ntex.sx is by no means authoritative, the asker can always consult\nthe relevant mailing lists.\n\n"}}