last build of tl18 tonight
simon at simifilm.ch
Thu Feb 28 15:34:47 CET 2019
> On 28 Feb 2019, at 13:33, Greg' Ar Tourter <artourter at gmail.com> wrote:
> This is actually a bug in microtype that was exposed by the latest change in luaotfload.
> the current workaround is to load `luatexbase` before loading microtype.
> https://tex.stackexchange.com/questions/476740/microtype-error-with-lualatex-attempt-to-call-field-warning-a-nil-value <https://tex.stackexchange.com/questions/476740/microtype-error-with-lualatex-attempt-to-call-field-warning-a-nil-value>
> https://github.com/u-fischer/luaotfload/issues/46 <https://github.com/u-fischer/luaotfload/issues/46>
> sorry for the noise
While this is a bug in microtype and while there is an easy workaround, I think it still makes sense to discuss whether a TL freeze at this very moment is indeed a smart decision. Many documents will break because of this bug and I am not sure whether it is wise to freeze TL exactly at a point where such a prominent bug appears.
I have no idea how long it will take until microtype is updated, but it might make sense to wait a few days before TL18 is frozen.
Telephon: ++41 44 451 5334
Mobophon: ++41 76 459 6039
„Etwas ist immer.“ Kurt Tucholsky
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the tex-live