| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
| |
This reverts commit 7250ac958d842f45d28220db87203506d3ae65c0.
As per issue #405.
|
|
|
|
| |
Fix attempt for issue #391
|
| |
|
| |
|
|
|
|
|
|
|
| |
Includes @zhouyan’s description of the conversion in case we’ll ever add
further units.
Reviewed-by: Yan Zhou <zhouyan@me.com>
|
|\ |
|
| | |
|
|\ \ |
|
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
As discussed in issue #398.
Ad futuram rei memoriam the gist of it:
- For the index, all values are scaled (decipoints * sp) / 10 *
(7227 / 7200).
- The ``bp`` case (the default, OT-standard), needs no conversion
because it matches how values are stored in the index.
- The ``pt`` case essentially reverts the bp→pt part of scaling
done for the database by scaling the asked size by the same
factor, i. e. by 7227 / 7200.
- The ``dd`` needs an extra 1238 / 1157.
Requesting a font at 10pt will then:
- ask for a size of 655360 for ``bp`` / default;
- ask for 657817 for ``pt``;
- ask for 703870 for ``dd``.
|
| |
| |
| |
| |
| |
| | |
Fix #397
These four features should not be inserted automatically.
|
|\| |
|
| |
| |
| | |
The conversion from reported design size etc., to "true `sp` value" is actually converting from `bp` to `pt`.
|
|/
|
|
| |
These have stabilized a long time ago and will be supported.
|
|
|
|
|
|
| |
Fix #394
Due to an oversight, all files except AFM got scanned twice.
|
| |
|
|
|
|
|
| |
Store design sizes in sp in index. Lookups are performed using sp
so the design size factor can be applied at runtime.
|
| |
|
| |
|
|
|
|
| |
Fix #389
|
|
|
|
|
|
| |
Fix #390
Suggested by @davidcarlisle.
|
| |
|
|
|
|
|
|
| |
With 1.0.3 the test pln-letterspace-12-double-ligature-issue-350.tex
causes a crash on account of a double free. Remove the code that calls
nodedirect.free() on the removed nodes until this is better understood.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Fix assignment of LM series fonts. Currently these are broken because of
borked typosub identifiers like “8oblique” that prevent exact name
matching and at the same time exclude matching the (usable) subfamily.
Introduce a heuristic based on the italic angle value that assigns
italic as a fallback in these cases.
Test: https://bitbucket.org/phg/lua-la-tex-tests/src/857c83ca98cb35153979a0613d3a742bfd93f834/lua/tla-names-3-lm.lua
|
|
|
|
|
| |
The config option must go since the FF based code was removed already
some time ago.
|
| |
|
| |
|
|
|
|
| |
Subfont loading seems to have been broken for a while but no reports …
|
|
|
|
|
| |
These only make the loader emit warnings because of the missing runtime
environment. They weren’t needed to begin with.
|
|
|
|
|
|
|
| |
Fixes #382
Luaotfload will fail with an up to date Luatex on account on a buggy
minimum version check. Many thanks to @davidcarlisle for the report.
|
|
|
|
|
|
|
|
|
| |
Credits to Taco for the talk at Kalenberg that inspired the feature.
Extending the parser is required so we can have proper name for the
feature.
Happy Luatex 1.0.0
|
| |
|
|
|
|
|
| |
Fontloader crashes during loading. Hans is notified, let’s wait for him
to fix it properly.
|
|
|
|
| |
This incorporates our patch for issue #377.
|
|
|
|
| |
Patch has been upstreamed for a while but no response yet.
|
|
|
|
|
|
| |
The loader makes some assumptions about available lookup functions early
on. Since fonts-syn.lua only installed dummies for most of these, we
might as well do that too.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
addfeature() and the likes -- with less extensive logging -- is now
provided directly by means of font-otc.lua so we don’t need to keep
these parts around any longer. The loader installs anum features
identical to ours and a slightly different “tlig” one which we override.
Clean up locals and misleading comments while we’re at it.
|
| |
|
|
|
|
|
| |
CAVEAT LECTOR This adds font-otc.lua part of which has already been
included in our feature handler.
|
|
|
|
| |
No need for patching font-tfm.lua any longer.
|
|
|
|
| |
Hans appears to have heard our pleas =)
|
|
|
|
|
|
|
|
|
|
| |
This makes our own features work with otf.addfeature().
However, for TFM it’s still not functional out of the box since the
enhancer is installed at a time when it has not been defined yet. An
answer from Hans is pending. In the meantime, we put a crude hack into
our font-tfm.lua to allow injecting the enhancer retroactively on
Luaotfload init.
|
|
|
|
|
| |
The AFM one is still preferable when passed a PFB because of the extra
checking it does.
|