-
Notifications
You must be signed in to change notification settings - Fork 8
luaotfload seems not to recognize LuaTeX 1.0.0 #387
Comments
see #382 |
Although texlive won't be using 1.0 by default until tl2017 miktex is apparently already using it, so this will start to hit end users. Any chance of a ctan release if only for this? |
As it starts to hit the miktex users here the work-around for miktex users until the package is updated officially: Get the prerelease of luaotfload https://github.com/lualatex/luaotfload/releases. Use the |
u-fischer, I followed your instructions but still encountered the problem despite removing the luaotfload package with the MiKTex package manager.
4. The missing step appears to be renaming the folder C:\Users$username\AppData\Local\Programs\MiKTeX 2.9\tex\luatex\luaotfload. In my case, I renamed it to luaotfload.bad. |
@brentpayton you are right, I forgot that in a multiuser installation a luaotfload installed by the package manager of the user is found first (I have a singleuser installation). In this case you should either deinstalll the package with the package manager or separate UserInstall and UserConfig, https://sourceforge.net/p/miktex/bugs/2534/ |
Hi pinging here again, could I ask for a ctan release fixing the version check so it can get to miktex and texlive by default? We are considering adjusting the default encoding for lualatex and xelatex to be Unicode, at the next release (nominally 1st January) but currently this issue would mean that lualatex doesn't wok at all with the distributed files. Thanks. |
we hope to release latex 2017/01/01 this weekend, which loads luaotfload-main in everyjob, could I ask again if there is any progress towards a ctan release with the version check fixed? a minimal change would be to just change the test to |
New release is on its way to CTAN, sorry for the delay. |
Running a document loading
luaotfload
with LuaTeX 1.0.0 seems to result in an error:Reference: http://tex.stackexchange.com/questions/336875/bug-in-miktex-2-9-6147
The text was updated successfully, but these errors were encountered: