| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
* --database-dir is useless anyway since we don't support loading names
database from arbitrary path.
* --sys (and mkluatexfontdb-sys) are dangerous since we will load user
specific fonts (in ~/.fonts for example) which can not be loaded by
other users (can be security concern as well). If there is real need,
we should then implement it properly.
+ some clean up and less code duplication in mkluatexfontdb.
|
|
|
|
|
| |
The database building/updating that the, unusual, progress bar is not
needed.
|
| |
|
|
|
|
| |
Utilize lualibs functions when apporiate.
|
|
|
|
|
|
| |
We no longer query fontconfig cache rendering this option useless.
Someone have to test it, I can't run the script here.
|
|
|
|
| |
(hope that's enough. too late for much thought.)
|
|
|
|
| |
This reverts commit ef220e625c6741cc15f29a77e457c7094fc79541.
|
|
|
|
| |
Related question: do Manuel and I have to add our
names to the copyright?
|
| |
|
| |
|
|
|
|
|
| |
The |status| table need not to reside in a separate file, it is now part
of the font names database itself.
|
| |
|
| |
|
|
|
|
|
| |
Per Manuel's suggestion, we now use TEXMVAR/luatex/generic/luaotfload/
instead of TEXMVAR/luatex-cache/latex/.
|
|
|
|
|
| |
Simplify the database and the code to reflect recent changes in font
matching logic.
|
|
|
|
|
| |
There is no performance difference, so it doesn't make sense to keep
removed fonts in the database.
|
| |
|
| |
|
|
|
|
|
| |
Now $TEXMFVAR/luatex-cache/latex/names/ which looks more logical than
$TEXMFVAR/scripts/luatexfontdb/.
|
| |
|
|
|
|
|
| |
Use os.type and os.name instead, if os.name doesn't return cygwin then
luatex need to be fixed.
|
|
|
|
|
|
|
| |
Group all our font names functions in |otfl-font-nms.lua| and make
|luaotfload.lua| load it. Now |otfl-font-dum.lua| is an unmodified,
we instead override the needed functions in the names module. This
decreases the redundancy that we had.
|
|
|
|
| |
We were always generating a new one.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
It seems that there is no performance regressions with purge... can you
test, maybe it would be better to make it default?
|
|
|
|
|
|
|
|
|
|
|
|
| |
* the info on a font now contains the checksum (might be needed for
font caching)
* very small optimizations in force mode
* database version bumping
* a new purge option (not taken into consideration yet)
* new mechanism to remove old entries in the database without
rebuilding everything, activated all the time but (for performance
reasons) will be activated only with the purge options in the very near
future.
|
| |
|
|
|
|
| |
Also stronger checks on status
|
|
|
|
|
|
|
| |
- the status is now externalized in another file name (in the same
directory), so that it's not loaded when just asking for a font
- the status is now filename->last-modification-timestamp so that we
don't have to checksum the files (much faster)
|
| |
|
| |
|
| |
|
|
|