On Sat, Dec 18, 2021 at 11:09 PM Paolo Prete wrote:
> The vertical-fill method does exactly what I asked in the very first post.
> But soon after, thanks to this thread, I saw some limitations in a
> pure-LilyPond approach, which I did not know: therefore I stated, *before*
> you made this exampl
p.s. Also compare with Urs's "ScholarLY" framework
(https://github.com/openlilylib/scholarly), which is "a library for annotating
LilyPond scores".
— K
> On Dec 19, 2021, at 9:58 AM, Kieren MacMillan
> wrote:
>
> Hi Valentin,
>
>> I've created this small mockup of how we can store additional
Hi Valentin,
> I've created this small mockup of how we can store additional information in
> scores and let Lilypond manage it. The idea is: One might have different
> versions of a part of a score, be it different sources or different edits
> within a source.
>
> So instead of selecting som
Hello,
I've created this small mockup of how we can store additional information in
scores and let Lilypond manage it. The idea is: One might have different
versions of a part of a score, be it different sources or different edits
within a source.
So instead of selecting some version (and mayb
