Closed phst closed 12 years ago
Maybe letting users' file overwrite the system defaults completely is not a good idea. There can be various reasons for a font to be included in the black-list. For example the font in a particular version of OS is broken a particular version of LuaTeX. Though the binary files in TL are frozen after release, some users may use TLContrib to update binaries. A system default should be working out of box for most users.
I think it maybe more useful to implement a white-list feature such that the white-list has priority over black-list. This way, users' black-list can supplementary systems' default while the white-list can overwritten part but not all of system defaults.
I think the patch in #39 solves this issue.
That pull request indeed solves bullet points two and three, thanks for that! Regarding bullet point one, on my system I can comment out all the fonts in the blacklist except Last Resort, without any apparent problems. What have been the reasons for having them in the blacklist originally? Maybe they don't apply any more.
They were blacklisted by Will stating that all ttc fonts on mac crash luatex, the bug in luatex might have been fixed since then.
There were some fixes in LuaTeX, see http://tracker.luatex.org/view.php?id=397 but I don't know if this applies here. I'd suggest to remove everything from the blacklist except for "last resort".
I have a few problems with the blacklist (
otfl-blacklist.cnf
):I think the blacklist system should be rethought:
read_blacklist
inotfl-font-nms.lua
should scan only the first file found so that users can overwrite the system defaults.