Hi Mason,
thank you for the hint what has to be explained more concisely in the
docs that are still waiting for there incarnation.
In you examples activation of the editions is done with
`\addEdition first`. To only apply edition `second` you can omit
`\addEdition first` or comment that out.
The command `\editionMod first ...` does not need `\addEdition first` to
compile.
Now the idea of the edition-engraver is to separate layout-mods and
editorial stuff from the content. So in a real project one or more files
containing the bare music definitions, e.g. `wind.fluteI = \relative {
c''8 b a ... }`, are included in a file starting the typesetting for a
specific edition.
All editionMods (for all editions) may be placed in another
include-file. Now in the file to typeset the specific edition either
`\addEdition first` for each needed collection of mods is added or in
one command `\setEditions first.second`.
So any edition receives is typeset from its own source file. Those files
are quite short containing the paper, layout and edition settings and
the actual score-creating command.
IIRC I once created one file to create multiple PDFs with different
editions activated and different paper sizes, but that is really tricky.
And in production I always use different files for separate editions.
HTH
Jan-Peter
Am 30.06.2018 um 18:30 schrieb Mason Hock:
> I'm slowly getting a handle on edition-engraver, largely thanks to this[1]
> guide, which very clearly explains basic usage for a single edition. However,
> neither the guide nor the usage examples in the repo demonstrate the use of
> multiple editions, and I'm confused as to how that would be done in a useful
> way. For example, these two snippets
>
> --------------------------------------------------------------
> \version "2.19.82"
>
> \include "oll-core/package.ily"
> \loadPackage edition-engraver
>
> \addEdition first
> \editionMod first 1 0/4 the-staff.Voice ^\markup { 1 }
> \editionMod first 1 2/4 the-staff.Voice ^\markup { 2 }
>
> \consistToContexts #edition-engraver Staff.Voice
>
> \score {
> \new Staff \with { \editionID the-staff } {
> \relative c' {
> c d e f
> }
> }
> }
> --------------------------------------------------------------
>
> --------------------------------------------------------------
> \version "2.19.82"
>
> \include "oll-core/package.ily"
> \loadPackage edition-engraver
>
> \addEdition first
> \editionMod first 1 0/4 the-staff.Voice ^\markup { 1 }
>
> \addEdition second
> \editionMod second 1 2/4 the-staff.Voice ^\markup { 2 }
>
> \consistToContexts #edition-engraver Staff.Voice
>
> \score {
> \new Staff \with { \editionID the-staff } {
> \relative c' {
> c d e f
> }
> }
> }
> --------------------------------------------------------------
>
> produce identical output, so, in the way I've been using edition-engraver so
> far, defining multiple editions does not appear to have a different effect
> from placing all edition-mods in one edition. It is true that I could put the
> edition-mods for each edition in a separate .ily file and only include the
> one I want to use when I compile, but even then there is no reason that the
> edition in each file could be called "first" instead of giving the editions
> different names.
>
> My expectation would be that there is a way of specifying which editions(s)
> should have their edition-mods observed and which should be ignored, but I
> can't find any information about this. Can anyone provide an example of
> correct usage of edition-engraver to maintain multiple editions?
>
> Thanks,
>
> Mason
>
>
> [1] https://lists.gnu.org/archive/html/lilypond-user/2018-01/msg00603.html
>
>
>
> _______________________________________________
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
