| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
This code proved to cause harm than good; unicode-math is doing better
without it. So, revert it back, until we are ready for it.
|
|
|
|
|
|
|
| |
Previously, we relied in the fact that origname contains the subfont in
the form of |foo.otf(subfoo)| and that luatex would then load the right
font, but this is not what the rest of the code expects and cause some
bugs. We now return the filename and subfont properly (i.e.separately).
|
|
|
|
| |
The difference is negligible, but this make the code more consistent.
|
| |
|
|
|
|
|
|
|
|
|
| |
Modules that provide OpenType and Unicode math related functionality,
not very tested yet, but it seems to magically fix some of unicode-math
issues.
May be it should be trimmed a bit, since a good chunk of the code is of
no use to us.
|
| |
|
|
|
|
|
|
|
|
| |
If the family name is matching but no matching style, we would not
return any thing, we now just return a random match (e.g. the user asks
for XITS Math/Regular but gets XITS Math/Math), I hope in such rare
cases there is only one match, else one is better giving proper style or
fullname.
|
|
|
|
|
|
|
| |
Code scrapped from ConTeXt, AFAIK, no font implements OpenType optical
bounds (on of Linux Libertine font has traces of it), but I plan to use
it in my fonts. The committed feature file is prepared for Pagella, we
can later have font specific feature files like this.
|
|
|
|
| |
When we fallback to filename lookup, we should return the original name.
|
| |
|
|
|
|
| |
This way we can load font names database from working directory etc.
|
|
|
|
|
| |
Simplify the database and the code to reflect recent changes in font
matching logic.
|
|
|
|
|
|
|
|
|
|
| |
With the previous commit, if we don't found a font with the requested
optical size, we return nothing, though we might have a matching font
name.
Now we store all matching names with no matching optical size and return
the first one, then we return the closest match (i.e. if the requested
size is 15pt and we have 10pt and 5pt match, we return the 10pt one).
|
|
|
|
|
|
| |
We now simply loop over the whole data.mappings table, so loading font
by family, fullname, psname etc is all the same, but it is a bit slower
now (~0.25s with syatemfonts.tex).
|
|
|
|
| |
Now, if we didn't find a matching family name, we then try fullname.
|
|
|
|
|
| |
Some fonts give only design size with no range, in this case we now will
assume range top == range bottom == design size.
|
|
|
|
|
| |
Update from ConTeXt, changes to save fonts under
TEXMFVAR/luatex-cache/latex/fonts.
|
|
|
|
| |
Also, fix date and version number to match that of latex package.
|
| |
|
|
|
|
|
| |
There is no performance difference, so it doesn't make sense to keep
removed fonts in the database.
|
|
|
|
| |
Patch from Taco.
|
|
|
|
| |
To protect against lua complaining about non existing file.
|
| |
|
| |
|
|
|
|
|
| |
Move function documentation inside the function block, and make
multi-line documents look better.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Now $TEXMFVAR/luatex-cache/latex/names/ which looks more logical than
$TEXMFVAR/scripts/luatexfontdb/.
|
| |
|
|
|
|
| |
Fixes a regression with legacy TeX ligatures (``'' etc.)
|
| |
|
|
|
|
| |
+ remove some unused compatibility code.
|
|
|
|
| |
+ some cosmetics
|
| |
|
| |
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
It is actually worse than that, I only test against trunk, once
texlive2010 binaries are frozen we will test against it.
|