Re: scholarly/annotate

[Urs Liska]

I'll have to try this on a PC, but for now two remarks:

You seem to have misplaced the space before \transposition so this can't be expected to produce anything meaningful. 

The custom properties that end up in the optional argument (square brackets) don't have any implementation so far. This is jzst a state where you can enter arbitrary stuff in the annotation and have *valid* LaTeX produced.

Please remind me if I fail to come back to this. 

Urs

Am 29. Oktober 2015 08:45:06 MEZ, schrieb Craig Dabelstein <address@hidden>:

Dear Urs (or any other Annotate experts),

I have created this entry in my input file, taking the idea from the example given on git:

\criticalRemark \with {

    message = "Originally \\textit{Flauti in F} which is an E\flat\ transposition."

    original-instrument-key = \key ef \major

    original-score-key = \key c \major

  }

Can anyone tell me how this should translate into the latex file? Is it expected to produce a real key signature in the latex file?

The console output produces:

  \criticalRemark \with {

Measure 1184, beat 1

Context: Flute 1

Affected Item: NoteHead

Message: Originally \textit{Flauti in F} which is an E\flat\ transposition.

original-instrument-key: Key: #<Pitch ees >

original-score-key: Key: #<Pitch c >

The .inp file produces:

\criticalRemark

   [original-score-key={Key: #<Pitch c >},

    original-instrument-key={Key: #<Pitch ees >}]

    {1184}{1}

    {Flute 1}

    {NoteHead}

    {Originally \textit{Flauti in F} which is an E\flat\ transposition.}

How would you have this display in your latex Critical report?

I hope this makes sense.

All the best,

Craig

Craig Dabelstein

e:address@hidden

 

lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.