bug-lilypond
[Top][All Lists]
Advanced

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

Re: LaTeX embedding of after staff editorial annotation


From: Urs Liska
Subject: Re: LaTeX embedding of after staff editorial annotation
Date: Tue, 30 Jun 2020 19:31:16 +0200
User-agent: Evolution 3.36.3-1

Am Dienstag, den 30.06.2020, 14:44 +0200 schrieb Claire Meyer:
> I recently wanted to reproduce an old score, on which an editorial
> annotation is located after the score. For fidelity's sake, I wanted
> to
> reproduce the annotation.
> I used a solution found on music stack exchange
> <https://music.stackexchange.com/a/101207/68804> and it didn't work
> right
> away. So I investigated, and it seems that the problem is apparent
> when the
> score is integrated via latex. Now, I know this mailing list is for
> lilypond related bugs, not latex' ones, but I'm not sure the bug is
> related
> to the package I use, just that it becomes apparent when I integrate
> with
> latex, thus the bug report.

Well, all the main developers of lyluatex are on the LilyPond lists, so
you have come to the right place ;-)

> 
> Onto the issue :
> When trying to add after staff editorial annotation, my score looks
> fine
> when I compile with lilypond directly, but the annotation doesn't
> appear on
> my document when I integrate the score in my document via latex.
> 
> Documents attached :
> - MWE : pianoTest.ly (14 lines, 336 chars)  and latex.tex (6 lines,
> 150
> chars)
> - what it looks like compiled with lilypond : pianoTest.pdf
> - what it looks like integrated via latex : latex.pdf
> 
> Configuration :
> - lilypond v2.20.0
> - texlive-full 20200626-1 w/ texlive-music 2019.52275-1
> - latex package used : lyluatex
> - OS : Manjaro KDE (arch-based linux)
> 

I don't have the opportunity to do a full test right now, but I'm 95%
sure it's about the following issue (which you should fix in the
LilyPond file).

1)
lyluatex uses the *cropped* output created with "lilypond-book-
preamble.ly".

2)
When you combine stencils the way you do LilyPond doesn't automatically
know the "extent" of the combined stencil.

3)
This can lead to the extended stencil being cropped.

3a)
You should be able to replicate this when compiling with LilyPond but
including the line
  \include "lilypond-book-preamble.ly"


I can't test a proper solution but basically somewhere in your stencil
callback you should do a 
  (ly:grob-set-property! grob 'X-extent <some-pair>)

where <some-pair> provides the actual extent of the combined stencil.
This is something the people on this list should be able to help you
with.

HTH
Urs

> Claire
> _______________________________________________
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-lilypond




reply via email to

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