Ian Hulin <[email protected]> writes:
> The main thing you'll need to look at for possible side-effects is the
> coding of the tagline in scm/titling-init.ly, as this is potentially
> used by default in any LilyPond compilation. Here's the stuff from
> scm/titling-init.ly.
>
> tagline = \markup {
> \with-url
>
> #"http://lilypond.org/";
> \line {
>
> %% 2014 = em dash.
>
> #(ly:export
> (format #f "Music engraving by LilyPond ~a~awww.lilypond.org"
> (lilypond-version)
> (ly:wide-char->utf-8 #x2014)
> ))
> }
> }
>
> If as part of this patch you can re-code so we don't have to use this
> nonsense, so much the better, it's a major PITA for Guile V2 migration
> as it crashes Guile in phase 2 of LilyPond initialization and I can't
> yet see why.
Likely because of a half-working format override. You could try using
string-append instead of format here and see how you fare.
Anyway, the replacement done by convert-ly would be just
$(format #f "Music engraving by LilyPond ~a~awww.lilypond.org"
(lilypond-version)
(ly:wide-char->utf-8 #x2014)
)
So I have my doubts that the situation would change either way, as the
code paths would remain similar.
--
David Kastrup
_______________________________________________
lilypond-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
