-
Notifications
You must be signed in to change notification settings - Fork 15
Faulty luatex-fonts-names.lua under Cygwin #33
Comments
Unless I'm mistaken, the goal of this Can you try removing the |
Hi Manuel, sorry for answering so late. I've been busy abroad from my Cygwin installation. If I remove But as I remarked above: I doubt that the job of eliminating duplicates can be achieved by this function because the dir path portion is truncated at the end (if file.collapse_path does what its name states). I'm not an experienced TeX Live user on the Cygwin platform. Some weeks ago it was the first time ever I installed it and looked at it a little bit. I walked through the luaotfload code with a simple text editor. No Lua IDE, I haven't checked if path_normalize is used elsewhere. No test suite to check if my local changes in path_normalize affect other parts. Here my settings, probably they are also relevant to avoid duplicates: $ luatools --var-value OPENTYPEFONTS $ luatools --var-value OSFONTDIR $ kpsewhich --var-value OPENTYPEFONTS $ kpsewhich --var-value OSFONTDIR I still have no deep understanding if LuaTeX's kpse library is merely an OO interface or a re-implementation of kpsearch. And if texmfcnf.lua is used only by ConTeXt MkIV or also by LuaLaTeX. But investigating such issues is a good chance for me to get deeper into the material. Bye |
Sorry to be more than late on the issue, but what about something like: if os.type == "windows" or os.type == "msdos" then (not tested) ? If you are not able to test anymore, I'll try it on a VM... Thank you, |
mkluatexfontdb generates lines like
["filename"]={ "minionpro-regular.otf", false },
under Cygwin. Because file names in Cygwin are case-sensitive, the font MinionPro-Regular.otf e.g. cannot be found at runtime.
The local function path_normalize in otfl-font-nms.lua has these lines of codes:
For Cygwin all of the tree lines are unnecessary or defective:
This shows once more that Cygwin behaves much more like Unix/Linux than Windows or DOS.
For os.name == "cygwin" these three lines of code should not be executed.
The text was updated successfully, but these errors were encountered: