Assets
6
First round of fixes for v2.8.
Assets
6
Changes since v2.7:
- Support Luatex 1.0 (tested with 1.0.3 from SVN).
- Fix issues #382, #389, #390, #393.
- New configuration option
designsize-dimen. - Improvements to the assignment of complex font families.
Assets
6
phi-gamma
released this
New loader and fixes.
Assets
6
phi-gamma
released this
Use with caution.
Assets
5
Early release with lots of bugs just for testing.
Assets
5
This marks the third follow-up to the TeX Live 2016 edition of Luaotfload.
- Fontloader in sync with Context as of 2016-06-16. Highlight: Improvements
in the support for Type1 fonts. - Addresses issues #356 / #363, #359 / #325, #358, #357, #349, #344, #361.
Many thanks to Hans Hagen, @dohyunkim, @grizzilus, @ralessi, @u-fischer, and
@jfbu for contributing or reporting bugs, respectively.
Assets
6
This is the second round of bug fixes to the TeX Live 2016 edition of Luaotfload.
-
Update the fontloader with Context version 2016-05-01 09:57:00.
-
Fix a number of crashes in letterspacing and font handling.
-
Allow configuration of the default (anonymous) lookups.
-
Handle unsupported versions of Luatex gracefully instead of crashing.
As always, the fontloader improvements were by Hans Hagen. A number of
contributors on Github also deserve thanks: @schlcht, @ralessi, @7Z0t99, @jfbu,
and @hvoss49.
Assets
6
Apart from updating the Fontloader code to the state of 2016-04-27,
this release addresses a number of flaws in the initial 2.7 release.
All fontloader improvements courtesy of Hans Hagen. Thanks to users
@dohyunkim, @h-kitagawa, @schlcht, @aminophen, and @u-fischer for
the numerous bug reports and contributions.
Assets
6
Release for this year’s TeX Live. Apart from the usual bugfixes, small improvements, pruning
of legacy code and general maintenance, the most important changes are:
- Update the fontloader code to Context 2016.04.19 17:16. As a consequence, Luatex’s
builtinfontloaderlibrary is not used anymore because all the font handling has been
moved to the Lua end. - Font combinations: Using a new request syntax, virtual fonts can now be created on the
fly from other fonts by importing glyph sets A special case of this is specifying a fallback
font.
Many thanks to Hans Hagen for the smooth cooperation; also the input of @dohyunkim and
others on Github proved very valuable.