Thanks for all the tips. On Mon, 11 Nov 2019 at 22:13, Carl Sorensen <c_soren...@byu.edu> wrote:
> Here’s a solution that worked in the past -- it describes how DPI settings > get set in fonconfig to 96 dpi, instead of 1200 (the lilypond default): > > https://lists.gnu.org/archive/html/bug-lilypond/2017-01/msg00022.html > > Carl > My fontconfig already has it set to 96. I have another machine with the same operative system and general settings, equally up to date, and there, lilypond works fine (they are not a perfect mirror of each other). To clarify my situation, anything I compile has that error, even if the version declared is the current one, and the failure happens from both frescobaldi and the command line. /David.
