Hi Ben,
I was about to write about the three dimension to watch. But I have
to think about it, if I can change this.
For now there will one set of editiontags per compilation. So every
call to \addEdition and \removeEdition will affect the list of
active modification-layers for the whole run. The compilation of a
file is done in multiple steps. The called commands act on in the
first step, the actual typesetting is done in another step.
In my use-cases, I always have one edition-set per file, e.g.
full-score or part for single instruments. But your use-case looks
reasonable. I attached your example slightly modified, where the
first score is modified, but not the second. To achieve this, I used
\applyContext, so that the \removeEdition command is performed, when
beginning typesetting th second score. The command could be wrapped
inside a little helper command.
This technique has the pro, that it matches your use-case, but a big
con, in that it remixes content and design again.
So I would not recommend this over the solution, you already found.
Perhaps another solution is found another day ;-)
HTH for now
Cheers
Jan-Peter
Am 22.01.2016 um 22:00 schrieb Ben
Strecker:
I’m working on a project that would have the same melody appearing in different ranges in the same document. Each range has its own set of modifications through the edition-engraver, but using \removeEdition anywhere in the file appears to remove that edition for all of the scores. What is the best practice for managing multiple editions in the same file?
I have attached a very simple example where I have two scores: one that should have a color modification applied, and another that should not have any editionMods applied.
Thanks,
Ben
_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user