Hi Craig,

actually I see there's nothing *I* have to look into right now. Rather
you should tell me what you would like to achieve. Tell me what - from
your experience with an actual project - would be good to have in
ScholarLY. While not exactly rich in time I'm more than ready to bring
this package further.

So far custom properties are just translated into key-value properties
to the LaTeX command. It's then the task of LaTeX to do something useful
with them. As I said the current set-up simply guarantees that

Am 29.10.2015 um 22:58 schrieb Craig Dabelstein:
> Thanks Urs. I'm working on a 900-page score from 1842 and
> scholarly/annotate is proving invaluable. Thanks for all your hard
> work on this.
>
> Craig
>
>
> On Thu, 29 Oct 2015 at 18:05 Urs Liska <u...@openlilylib.org
> <mailto:u...@openlilylib.org>> wrote:
>
>     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
>     <craig.dabelst...@gmail.com <mailto:craig.dabelst...@gmail.com>>:
>
>         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:craig.dabelst...@gmail.com <mailto:craig.dabelst...@gmail.com>
>         <http://www.facebook.com/craig.dabelstein> 
> <http://au.linkedin.com/pub/craig-dabelstein/b2/5b8/389/en>
>
>         
> ------------------------------------------------------------------------
>
>         lilypond-user mailing list
>         lilypond-user@gnu.org <mailto:lilypond-user@gnu.org>
>         https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>     -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9
>     Mail gesendet.
>
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to