You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to use \defaultfontfeatures{Renderer=OpenType} before configuring any font to set OpenType as the renderer for all fonts in place of node, that is the LuaLaTeX default.
The motivation is that LuaLaTeX appears to be way faster (twice as fast on small documents) when using HarfBuzz in place of the lua coded renderer. Currently my experiments are targeted at identifying problems and benchmarking. In perspective it would be nice to use \defaultfontfeatures to default to HarfBuzz and ask for the node renderer only in a few fonts where HarfBuzz mode can cause issues.
The problem is that by adding the Renderer=OpenType option to the individual fonts the compilation time is effectively slashed, while using \defaultfontfeatures{Renderer=OpenType} before loading the fonts actually makes the compilation slowlier as if node was still used (or maybe used in addition to HarfBuzz).
The fact that the fonts do not really switch to an HarfBuzz-only management is further confirmed by the fact that OpenType Math fonts have issues with HarfBuzz and cause LuaLaTeX to error out on many documents with them. However, using \defaultfontfeatures{Renderer=OpenType} which should cause all fonts to use OpenType does not trigger the error with the Math fonts.
Check/indicate
Relevant for XeTeX
Relevant for LuaTeX
Issue tracker has been searched for similar issues?
Links to <tex.stackexchange.com> discussion if appropriate
Description
I am trying to use
\defaultfontfeatures{Renderer=OpenType}
before configuring any font to set OpenType as the renderer for all fonts in place of node, that is the LuaLaTeX default.The motivation is that LuaLaTeX appears to be way faster (twice as fast on small documents) when using HarfBuzz in place of the lua coded renderer. Currently my experiments are targeted at identifying problems and benchmarking. In perspective it would be nice to use
\defaultfontfeatures
to default to HarfBuzz and ask for the node renderer only in a few fonts where HarfBuzz mode can cause issues.The problem is that by adding the
Renderer=OpenType
option to the individual fonts the compilation time is effectively slashed, while using\defaultfontfeatures{Renderer=OpenType}
before loading the fonts actually makes the compilation slowlier as if node was still used (or maybe used in addition to HarfBuzz).The fact that the fonts do not really switch to an HarfBuzz-only management is further confirmed by the fact that OpenType Math fonts have issues with HarfBuzz and cause LuaLaTeX to error out on many documents with them. However, using
\defaultfontfeatures{Renderer=OpenType}
which should cause all fonts to use OpenType does not trigger the error with the Math fonts.Check/indicate
Minimal example demonstrating the issue
The text was updated successfully, but these errors were encountered: