[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: \center-column broken

From: Jonas Hahnfeld
Subject: Re: \center-column broken
Date: Sun, 14 Feb 2021 19:41:08 +0100
User-agent: Evolution 3.38.4

Am Sonntag, dem 14.02.2021 um 18:25 +0100 schrieb Jean Abou Samra:
> Hello,
> Le 14/02/2021 à 16:59, Johannes Feulner a écrit :
> > Hi Aron,
> > 
> > the \center-column issue seems to be a problem of the SVG backend. I 
> > compiled LilyPond from master and use a custom backend based on 
> > LilyPond's SVG backend. However, the pictures were made with 
> > LilyPond's standard SVG backend. I've now used the PDF backend,  it is 
> > not affected.
> I am not competent about this. However, I can notice
> that with fresh a build of master, in SVG backend,
> Eye of Gnome displays the file incorrectly; the text
> runs off the box as you describe. The tagline is also
> sloppy. With Firefox, all is fine. With both readers,
> the font used does not resemble LilyPond's default.
> With 2.18, Firefox displays the file correctly with
> LilyPond's default font, and Eye of Gnome does not
> manage to render the text at all (it replaces it
> with ellipsis).
> Attached are screenshots.
> I see that all that ends up in this SVG file is
> (manually wrapped):
> <text font-family="serif"
>        font-weight="bold"
>        font-size="6.9848"
>        text-anchor="start"
>        fill="currentColor">
> <tspan>aaaa</tspan>
> </text>
> so the reader is apparently free to render this text
> with whatever serif font it prefers.
> With 2.18, I see this instead:
> <text transform="translate(30.7267, 18.7229)"
>        font-family="Century Schoolbook L"
>        font-weight="bold"
>        font-size="6.9848"
>        text-anchor="start"
>        fill="currentColor">
> <tspan>
> aaaa</tspan>
> </text>
> There appears to be a real change in behavior
> between versions 2.19.21 and 2.19.22. Outstanding
> commits regarding fonts are:

I think it's the interaction of

> commit 28f58ecc2271956e9377dc61e5135ce3ade4abbd
> Author: Masamichi Hosoda <trueroad@trueroad.jp>
> Date:   Fri Jun 12 17:17:56 2015 +0900
>      Issue 4441 / 4: Define default fonts in fontconfig configuration file
>      This commit defines LilyPond default fonts
>      in local fontconfig configuration file.
>      And, LilyPond uses them.
>      It is possible to combine multiple fonts
>      with different character sets and glyphs each other.
>      e.g. Following fonts can be combined.
>      Latin glyphs: from a font without Cyrillic glyphs
>      Cyrillic glyphs: from another font with Cyrillic glyphs


commit ead2001959fa5bda0338e92a0f301fd1f26ad768
Author: Paul Morris <paulwmorris@gmail.com>
Date:   Sat Feb 20 11:24:04 2016 -0500

    Issue 4776/1 font.scm: better svg defaults for font-family
    if the user has not set the font, use a
    meaningful svg default ('serif' 'sans-serif'
    or 'monospace') for the font-family property

After reading
my understanding is that SVG renderers don't understand the alias
"LilyPond Serif" (how would they?) and it was decided to use the
generic "serif" instead. It would probably be more correct to specify
the font that was used to calculate the layout, but then it might be
that it's not installed on the viewer's system (when distributing the
SVG) and the user would still see garbage...


Attachment: signature.asc
Description: This is a digitally signed message part

reply via email to

[Prev in Thread] Current Thread [Next in Thread]