-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Two editions from the same source #71
Comments
Disclaimer: I have never really liked scholarLY annotations can also be directly be created from a span (see "Creating scholarLY Annotations" in the Making annotations invisible is a matter of Finally (although not really relevant to your example) you can encode alternatives using |
Thanks, but I don't quite understand, because it looks like
I still had to use I'd also be interested to know why you don't like |
Hello again,
How should I make two editions from the same LilyPond source:
I’m trying to do this with
\tag
but I can’t get it to work. In the attached small example, I have two tags,#'crit
and#'perf
, for content that is specific to one edition or the other. I want the notegis,
to appear in both editions. In the critical edition, that note should have a green\criticalRemark
. In the performance edition, the note should instead have a footnote (referring to the critical edition) and a fingering.The way I’ve written it in the attached file, the critical edition (with
\keepWithTag #'crit \removeWithTag #'perf
) is rendered correctly. But in the performance edition (with\removeWithTag #'crit \keepWithTag #'perf
), the notegis,
is missing:I guessed that this is because the note is actually wrapped inside the
\criticalRemark
, so if the tag removes the\criticalRemark
, it removes the note, too. So I tried using a post-event instead, like this:But then the
\criticalRemark
doesn't produce any output.The only way I can get it to work is to encode the note twice:
But I would rather not encode the same note redundantly. Is there a better way?
A-Composer-One-Bar-of-Music.ly.zip
The text was updated successfully, but these errors were encountered: