Re: scholarly/annotate

Hi Craig, somehow I missed answering this one, and I only realized that after writing several other posts about the topic earlier today ... Am 05.11.2015 um 02:27 schrieb Craig Dabelstein: > Hi Urs, > > Thanks for your detailed email. I agree wholeheartedly with your > examples 1-4 above --

Re: scholarly/annotate

Hi Urs, Thanks for your detailed email. I agree wholeheartedly with your examples 1-4 above -- these would all be very useful for me. The score I'm working on (900-page handwritten manuscript from 1842) has natural horns and trumpets, and clarinets and flutes that change keys regularly

Re: scholarly/annotate

OK, now I'm back again ... As said you should tell me what you want to achieve. - What do you want to communicate? - How (and where) do you think that should be visualized? - How do you think should it be encoded in the annotation? (This goes for your current example or any others you came

Re: scholarly/annotate

No problem Urs. Thanks for all you do. Craig On Mon, 2 Nov 2015 at 17:54 Urs Liska wrote: > Oops, sent instead of saved ... > I'll have to return to this later. > > > Am 2. November 2015 08:50:39 MEZ, schrieb Urs Liska : >> >> Hi Craig, >> >>

Re: scholarly/annotate

Oops, sent instead of saved ... I'll have to return to this later. Am 2. November 2015 08:50:39 MEZ, schrieb Urs Liska : >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 -

Re: scholarly/annotate

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

Re: scholarly/annotate

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 wrote: > I'll have to try this on a PC, but for now two remarks: > > You seem to have

Re: scholarly/annotate

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