W dniu 16.02.2021 o 18:33, Jonas Hahnfeld pisze:
Usual disclaimer that LilyPond doesn't fully support Guile 2.2 (yet),
so you'll definitely see worse performance (mostly slower startup) and
might run into occasional issues, like this one. Guile 1.8 should be
the safer choice for now (if you
Am Dienstag, dem 16.02.2021 um 15:44 +0100 schrieb Arusekk:
> Hello lilypond crew!
>
> Reporting the bug here, since I saw on the bug link that you prefer mail
> over GitLab issues.
>
> When trying to process any file with \layout{} directive, lilypond
> crashes (Segmentation fault / address
Hello lilypond crew!
Reporting the bug here, since I saw on the bug link that you prefer mail
over GitLab issues.
When trying to process any file with \layout{} directive, lilypond
crashes (Segmentation fault / address not mapped).
I was able to reproduce it on current git master
> Inkscape works very well to convert PDFs to SVG, but if we expect
> our users to do that, then it's debatable whether we should have an
> SVG backend at all.
I agree. However, my SVG knowledge is very small; this means I'm not
qualified to make any decisions.
> (I mean this seriously: the
On Tue, 16 Feb 2021 at 08:44, Werner LEMBERG wrote:
>
>
> > How about hosting the fonts on www.lilypond.org and referencing them
> > in the @font-face definition?
>
> I think this is not a good idea.
I agree that hosting fonts would be a headache: everyone's svg
documents would suddenly depend
> How about hosting the fonts on www.lilypond.org and referencing them
> in the @font-face definition?
I think this is not a good idea.
* LilyPond fonts change from version to version, quite often in a
backwards-incompatible way. Hosting them for SVG access would
enforce us to completely
