Re: ScholarLY

\setOption stylesheets.span.use-colors ##f did the trick. Thanks Urs On Wed, 17 Oct 2018 at 15:40, Urs Liska wrote: > > > Am 17.10.2018 um 03:00 schrieb Craig Dabelstein: > > Hi all, > > Is this the right code to use to turn off the colors in ScholarLy? I'm > using the latest version, but I'm

Re: ScholarLY

Am 17.10.2018 um 03:00 schrieb Craig Dabelstein: Hi all, Is this the right code to use to turn off the colors in ScholarLy? I'm using the latest version, but I'm using the \editorialMarkup commands. This line is having no effect. I'm sure I'm doing something wrong somewhere. \setOption s

Re: Scholarly question

Hi Craig, Am 10.04.2018 um 01:01 schrieb Craig Dabelstein: Hi all, Is this the correct way to ignore critical remarks in the output file? \ignoreAnnotationTypes #'() No, it isn't. And while looking into the files I realize that this option isn't commented properly. The proper command to

Re: ScholarLy and Latex

Urs, The "temp-print-message" branch worked perfectly first time. You are amazing! One small problem for me though -- the output is rendering the measure and beat with the lilyglyphs ({1}{4.\,\crotchet}). How can I get it back to just {1}{4} without the lilyglyph? I know I've seen how to do it som

Re: ScholarLy and Latex

Hi Urs, Thanks very much for all that information. I'll check out the "temp-print-message" branch and let you know how I go. All the best, Craig On 8 March 2018 at 02:12, Urs Liska wrote: > Hi Craig, > > sorry for the delay, but I had quite reduced capacities during the past > week. > > I'm

Re: ScholarLy and Latex

Hi Craig, sorry for the delay, but I had quite reduced capacities during the past week. I'm even more sorry to inform you that what you experience is "expected behaviour" and the result of incomplete implementation :-( The exported annotations put a number of information items (including t

Re: ScholarLy and Latex

Hi Urs, I hope you can understand these files. I think the report.sty file was borrowed from your Scores of Beauty post a long time ago (maybe). My problem is trying to get the content of the "message" field to be displayed. All the best, Craig On 1 March 2018 at 19:05, Urs Liska wrote: > Hi

Re: ScholarLy and Latex

Hi Craig, Am 23.02.2018 um 10:07 schrieb Craig Dabelstein: Hi Lilyponders, I'm having a minor problem with getting my ScholarLy inp file to work with Latex. The Latex output for each annotation looks like this: \criticalRemark    [grob={DynamicText},     grob-location={Can't display grob lo

Re: Scholarly editorial functions

Still not at my PC, but does that page help? https://github.com/openlilylib/scholarly/blob/master/editorial-functions/README.md Am 3. Februar 2018 22:18:47 MEZ schrieb Urs Liska : >Hi Craig, > >first you should mention that you are using openLilyLib and the >scholarly package. Most people will n

Re: Scholarly editorial functions

Hi Craig, first you should mention that you are using openLilyLib and the scholarly package. Most people will not recognise that. Second: I'll have to look up how that works (I'm not at my PC ATM) Urs Am 3. Februar 2018 22:11:26 MEZ schrieb Craig Dabelstein : >Hi all, > >I have two questions:

Re: ScholarLy and polymetric music? (bar numbering, \RemoveEmptyStaffContext)

Hi all, What about a radical alternative? What if each non-reference part has an additional “tick” barline (numbered according to the reference context) whereever the barlines don’t line up? Just a thought… Kieren. Kieren MacMillan, composer ‣ website: www.kier

Re: ScholarLy: unknown escaped string: `\colorAnnotations'

On Thu, 2015-11-19 at 13:57 +0100, Urs Liska wrote: > > > > % ScholarLy options: see > > > > > > > > https://github.com/openlilylib-archives/scholarly/wiki/Configuring-Annotations > > > It looks like you ran into an undocumented change (although I > > > can't remember). Please

Re: ScholarLy: unknown escaped string: `\colorAnnotations'

Am 19.11.2015 um 13:46 schrieb Graham King: > On Thu, 2015-11-19 at 13:31 +0100, Urs Liska wrote: >> >> >> Am 19.11.2015 um 13:01 schrieb Graham King: >> >>> Apologies for troubling you with this under-researched problem, but >>> I've just hit it as a deadline looms. >>> >>> I'm trying to turn of

Re: ScholarLy: unknown escaped string: `\colorAnnotations'

Graham King writes: > On Thu, 2015-11-19 at 13:31 +0100, Urs Liska wrote: > >> \setOption scholarly.colorize ##f >> >> should give you what you want. > > Brilliant! that works :) It causes lilypond to exit with return code 1 > and the message > > 2: error: unknown escaped string: `\scho

Re: ScholarLy: unknown escaped string: `\colorAnnotations'

On Thu, 2015-11-19 at 13:31 +0100, Urs Liska wrote: > > > > Am 19.11.2015 um 13:01 schrieb Graham King: > > > > > Apologies for troubling you with this under-researched problem, but > > I've just hit it as a deadline looms. > > > > I'm trying to turn off the colouring of ScholarLy annotation

Re: ScholarLy: unknown escaped string: `\colorAnnotations'

Am 19.11.2015 um 13:41 schrieb David Kastrup: > Urs Liska writes: > >> Am 19.11.2015 um 13:01 schrieb Graham King: >>> Apologies for troubling you with this under-researched problem, but >>> I've just hit it as a deadline looms. >>> >>> I'm trying to turn off the colouring of ScholarLy annotatio

Re: ScholarLy: unknown escaped string: `\colorAnnotations'

Urs Liska writes: > Am 19.11.2015 um 13:01 schrieb Graham King: >> Apologies for troubling you with this under-researched problem, but >> I've just hit it as a deadline looms. >> >> I'm trying to turn off the colouring of ScholarLy annotations, before >> final publication: [...] >> % Schola

Re: ScholarLy: unknown escaped string: `\colorAnnotations'

Am 19.11.2015 um 13:01 schrieb Graham King: > Apologies for troubling you with this under-researched problem, but > I've just hit it as a deadline looms. > > I'm trying to turn off the colouring of ScholarLy annotations, before > final publication: > > \version "2.19.21" > > \include "ope

Re: ScholarLy fails with \RemoveEmptyStaffContext

Graham King writes: > This took a little while to nail down, but it seems that ScholarLy's > annotation engine fails silently when \RemoveEmptyStaffContext is > active. Almost-minimal example attached. > \layout { > %{ %Toggle this block comment to reveal problem: > \context { > \Re

Re: ScholarLy fails with \RemoveEmptyStaffContext

Thank you for tracking that down, and sorry I didn't have time to reply to your personal message. Am 15.11.2015 um 12:15 schrieb Graham King: > This took a little while to nail down, but it seems that ScholarLy's > annotation engine fails silently when \RemoveEmptyStaffContext is > active. Almost

Re: ScholarLy fails with \RemoveEmptyStaffContext

On Mon, 2015-11-16 at 09:24 +0100, David Kastrup wrote: > Graham King writes: > > > This took a little while to nail down, but it seems that ScholarLy's > > annotation engine fails silently when \RemoveEmptyStaffContext is > > active. Almost-minimal example attached. > > > \layout { > > %{ %

Re: ScholarLy fails with \RemoveEmptyStaffContext

Graham King writes: > On Mon, 2015-11-16 at 09:24 +0100, David Kastrup wrote: > >> Graham King writes: >> >> > This took a little while to nail down, but it seems that ScholarLy's >> > annotation engine fails silently when \RemoveEmptyStaffContext is >> > active. Almost-minimal example attache

Re: ScholarLy fails with \RemoveEmptyStaffContext

On Mon, 2015-11-16 at 09:24 +0100, David Kastrup wrote: > Graham King writes: > > > This took a little while to nail down, but it seems that ScholarLy's > > annotation engine fails silently when \RemoveEmptyStaffContext is > > active. Almost-minimal example attached. > > > \layout { > > %{ %

Re: ScholarLy and polymetric music? (bar numbering, \RemoveEmptyStaffContext)

On Thu, 2015-11-12 at 10:38 -0600, David Wright wrote: > On Tue 10 Nov 2015 at 13:52:33 (+), Graham King wrote: > > On Mon, 2015-11-09 at 21:53 -0600, David Wright wrote: > > On Mon 09 Nov 2015 at 23:22:14 (+), Graham King wrote: > > > On Mon, 2015-11-09 at 14:55 -0600, Christopher

Re: Scholarly footnotes

Am 13. November 2015 13:29:30 MEZ, schrieb Graham King : >On Thu, 2015-11-12 at 12:45 +0100, Urs Liska wrote: > >> >> Am 12.11.2015 um 09:09 schrieb Urs Liska: >> > Having had a night over it I realized that there is an obvious >first >> > step towards b) and c) and that the infrastructure is a

Re: Scholarly footnotes

On 13.11.2015 13:29, Graham King wrote: I might struggle a bit at first to get from Scheme to lilypond markup In case you don’t know about that already: might help. Yours, Simon __

Re: Scholarly footnotes

On Thu, 2015-11-12 at 12:45 +0100, Urs Liska wrote: > > Am 12.11.2015 um 09:09 schrieb Urs Liska: > > Having had a night over it I realized that there is an obvious first > > step towards b) and c) and that the infrastructure is already there for it! > > I will add support for writing out the raw

Re: ScholarLy and polymetric music? (bar numbering, \RemoveEmptyStaffContext)

On Tue 10 Nov 2015 at 13:52:33 (+), Graham King wrote: > On Mon, 2015-11-09 at 21:53 -0600, David Wright wrote: > On Mon 09 Nov 2015 at 23:22:14 (+), Graham King wrote: > > On Mon, 2015-11-09 at 14:55 -0600, Christopher R. Maden wrote: > > On 11/09/2015 02:47 PM, Kieren MacM

Re: Scholarly footnotes

Am 12.11.2015 um 09:09 schrieb Urs Liska: > Having had a night over it I realized that there is an obvious first > step towards b) and c) and that the infrastructure is already there for it! > I will add support for writing out the raw Scheme object and simply > integrate it as an additional expo

Re: Scholarly footnotes

Am 11.11.2015 um 19:16 schrieb Urs Liska: > > > Am 10.11.2015 um 17:39 schrieb Urs Liska: >> >> >> Am 10.11.2015 um 17:08 schrieb Graham King: >>> ... long snip ... >>> >>> I confess I'm a bit daunted by the LaTeX learning curve, and it is >>> possible that I'm not uniquely inadequate in that re

Re: ScholarLy and polymetric music? (bar numbering, \RemoveEmptyStaffContext)

On Wed, 2015-11-11 at 18:44 +0100, Urs Liska wrote: > > > > Am 11.11.2015 um 11:14 schrieb Graham King: > > > > > > > > > > > > annotate "installs" itself in the Score context, and in polymetric > > > > > scores the timing-translator has to be removed from that context. > > > > > > > > >

Re: Scholarly footnotes

Am 10.11.2015 um 17:39 schrieb Urs Liska: > > > Am 10.11.2015 um 17:08 schrieb Graham King: >> ... long snip ... >> >> I confess I'm a bit daunted by the LaTeX learning curve, and it is >> possible that I'm not uniquely inadequate in that respect. So a >> Lilypond-only solution would be ideal f

Re: ScholarLy and polymetric music? (bar numbering, \RemoveEmptyStaffContext)

Am 11.11.2015 um 11:14 schrieb Graham King: > annotate "installs" itself in the Score context, and in polymetric scores the timing-translator has to be removed from that context. So to approach the issue one would have to remove \annotationProcessor from the Score contex

Re: ScholarLy and polymetric music? (bar numbering, \RemoveEmptyStaffContext)

On Wed, 2015-11-11 at 09:18 +0100, Urs Liska wrote: > > > > Am 11.11.2015 um 01:32 schrieb Graham King: > > > > > On Tue, 2015-11-10 at 22:50 +0100, Urs Liska wrote: > > > > > Am 10.11.2015 um 18:06 schrieb Graham King: > > > > On Tue, 2015-11-10 at 10:09 +0100, Urs Liska wrote: > > > >>

Re: ScholarLy and polymetric music? (bar numbering, \RemoveEmptyStaffContext)

Am 11.11.2015 um 01:32 schrieb Graham King: > On Tue, 2015-11-10 at 22:50 +0100, Urs Liska wrote: >> Am 10.11.2015 um 18:06 schrieb Graham King: >> > On Tue, 2015-11-10 at 10:09 +0100, Urs Liska wrote: >> >> >> >> >> >> Am 09.11.2015 um 17:34 schrieb Graham King: >> >> >> >>> (This note describes

Re: ScholarLy and polymetric music? (bar numbering, \RemoveEmptyStaffContext)

On Tue, 2015-11-10 at 22:50 +0100, Urs Liska wrote: > Am 10.11.2015 um 18:06 schrieb Graham King: > > On Tue, 2015-11-10 at 10:09 +0100, Urs Liska wrote: > >> > >> > >> Am 09.11.2015 um 17:34 schrieb Graham King: > >> > >>> (This note describes an issue arising from the separate thread, > >>> "Sch

Re: ScholarLy and polymetric music? (bar numbering, \RemoveEmptyStaffContext)

Am 10.11.2015 um 18:06 schrieb Graham King: > On Tue, 2015-11-10 at 10:09 +0100, Urs Liska wrote: >> >> >> Am 09.11.2015 um 17:34 schrieb Graham King: >> >>> (This note describes an issue arising from the separate thread, >>> "Scholarly footnotes" [1]) >>> >>> I would like to use Urs' annotate.ily[

Re: ScholarLy and polymetric music? (bar numbering, \RemoveEmptyStaffContext)

On Tue, 2015-11-10 at 10:09 +0100, Urs Liska wrote: > > > > Am 09.11.2015 um 17:34 schrieb Graham King: > > > > > (This note describes an issue arising from the separate thread, > > "Scholarly footnotes" [1]) > > > > I would like to use Urs' annotate.ily[2] to add some footnotes to an > > ed

Re: Scholarly footnotes

Am 10.11.2015 um 17:08 schrieb Graham King: > ... long snip ... > > I confess I'm a bit daunted by the LaTeX learning curve, and it is > possible that I'm not uniquely inadequate in that respect. So a > Lilypond-only solution would be ideal for me, and would save others > the prospect of learni

Re: Scholarly footnotes

Hi Urs, first, I'm deeply grateful for your time and thoughtful insights. Further comments interjected, below... all the best -- Graham On Tue, 2015-11-10 at 10:43 +0100, Urs Liska wrote: > Hi Graham, > > now I'll try to go into that somewhat more detailed. > > > Am 09.11.2015 um 17:33 schri

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 -- these

Re: ScholarLy and polymetric music? (bar numbering, \RemoveEmptyStaffContext)

On Mon, 2015-11-09 at 21:53 -0600, David Wright wrote: > On Mon 09 Nov 2015 at 23:22:14 (+), Graham King wrote: > > On Mon, 2015-11-09 at 14:55 -0600, Christopher R. Maden wrote: > > > > On 11/09/2015 02:47 PM, Kieren MacMillan wrote: > > > The very first thing they said to me was, “A

Re: ScholarLy and polymetric music? (bar numbering, \RemoveEmptyStaffContext)

Am 10.11.2015 um 14:28 schrieb Kieren MacMillan: > Hi Urs, > >> I have no idea if it is also appropriate for ancient music. > > Well, the absence of [any] barlines makes barline numbering more complex… ;) Of course it depends on the way an edition deals with that. > >> Aren't there any usefu

Re: ScholarLy and polymetric music? (bar numbering, \RemoveEmptyStaffContext)

Hi Urs, > I have no idea if it is also appropriate for ancient music. Well, the absence of [any] barlines makes barline numbering more complex… ;) > Aren't there any useful references, how have others dealt with that challenge? I can’t find any! Cheers, Kieren. ___

Re: ScholarLy and polymetric music? (bar numbering, \RemoveEmptyStaffContext)

Hi Graham, > On the positive side: > +1This scheme guarantees a unique id for each bar. The id increases in a > sensible manner. > +2The scheme is robust with respect to re-formatting, if systems are > split or joined. > +3Since Lilypond's default behaviour is to break lines only wh

Re: Scholarly footnotes

Hi Graham, now I'll try to go into that somewhat more detailed. Am 09.11.2015 um 17:33 schrieb Graham King: > I'm preparing an edition of sixteenth-century polyphony, using the > book-titling template[1]. The edition would benefit from some > footnotes/endnotes (the sort that say things like: "c

Re: ScholarLy and polymetric music? (bar numbering, \RemoveEmptyStaffContext)

Am 09.11.2015 um 17:34 schrieb Graham King: > (This note describes an issue arising from the separate thread, > "Scholarly footnotes" [1]) > > I would like to use Urs' annotate.ily[2] to add some footnotes to an > edition of sixteenth-century polyphony. But, before investing too > much time, I n

Re: ScholarLy and polymetric music? (bar numbering, \RemoveEmptyStaffContext)

Am 10.11.2015 um 00:56 schrieb Kieren MacMillan: > Hi Graham, > >> I've just realised that, under my system as I described it, a part could >> have the same bar number twice. > My proposed solution would be an “analytic continuation” (to borrow a > mathematical term) of the non-polymetric measu

Re: ScholarLy and polymetric music? (bar numbering, \RemoveEmptyStaffContext)

On Mon 09 Nov 2015 at 23:22:14 (+), Graham King wrote: > On Mon, 2015-11-09 at 14:55 -0600, Christopher R. Maden wrote: > > On 11/09/2015 02:47 PM, Kieren MacMillan wrote: > > The very first thing they said to me was, “Add measure numbers.” > > > > That’s sufficient reason for

Re: Scholarly footnotes

Hi Urs, What can I do to help you advance ScholarLY (or any of your other projects)? E.g. do I need to learn scheme? Do I play around with incorporating ScholarLY into Latex? What would be the most helpful for you? Craig On Tue, 10 Nov 2015 at 03:42 Urs Liska wrote: > Just shortly: > > I do t

Re: ScholarLy and polymetric music? (bar numbering, \RemoveEmptyStaffContext)

Hi Graham, > I've just realised that, under my system as I described it, a part could have > the same bar number twice. My proposed solution would be an “analytic continuation” (to borrow a mathematical term) of the non-polymetric measure numbering scheme: 1. A “reference context” would be est

Re: ScholarLy and polymetric music? (bar numbering, \RemoveEmptyStaffContext)

On Mon, 2015-11-09 at 14:55 -0600, Christopher R. Maden wrote: > On 11/09/2015 02:47 PM, Kieren MacMillan wrote: > > The very first thing they said to me was, “Add measure numbers.” > > > > That’s sufficient reason for me. =) > > Good answer. > > In that case, I would pick one part, and force t

Re: ScholarLy and polymetric music? (bar numbering, \RemoveEmptyStaffContext)

On 11/09/2015 02:47 PM, Kieren MacMillan wrote: The very first thing they said to me was, “Add measure numbers.” That’s sufficient reason for me. =) Good answer. In that case, I would pick one part, and force those measure numbers in as numeric rehearsal marks in the other parts. Otherwis

Re: ScholarLy and polymetric music? (bar numbering, \RemoveEmptyStaffContext)

Hi Chris, > What do you need the bar numbers for? I suspect rehearsal marks would fit > the bill, no? If not, why not? The score runs 105 measures in the piano part. I have 9 rehearsal marks (A-I), for an average of ~12 measures per rehearsal mark. In anticipation of officially [self-]publis

Re: ScholarLy and polymetric music? (bar numbering, \RemoveEmptyStaffContext)

On 11/09/2015 01:47 PM, Kieren MacMillan wrote: Is there a standard/convention/best practice on measure numbering in polymetric scores? I’m running into an issue of that myself (in my song “The Country Wife”), and can’t find anything definitive. Note: Gould (p. 484) writes, “Bar numbers should n

Re: ScholarLy and polymetric music? (bar numbering, \RemoveEmptyStaffContext)

Hi all, Is there a standard/convention/best practice on measure numbering in polymetric scores? I’m running into an issue of that myself (in my song “The Country Wife”), and can’t find anything definitive. Note: Gould (p. 484) writes, “Bar numbers should not be used in music in which individua

Re: Scholarly footnotes

Just shortly: I do think we'll find a good way for you, and I also think this is a good opportunity to continue work on ScholarLY. Especially considering that just a few days ago Craig Dabelstein also asked about ScholarLY. Urs Am 09.11.2015 um 17:33 schrieb Graham King: > I'm preparing an edit

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 throughout.

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 across

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, >> >> actually I see there's nothing *I* have to look int

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 - from >your experience wi

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 pack

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 misplaced the space befo

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 i

Re: ScholarLy newbie, running annotate.ly, gets error message

On Mon, 2015-10-19 at 16:48 +0200, Urs Liska wrote: > > > > Am 19.10.2015 um 16:36 schrieb Urs Liska: > > > > > You didn't do anything wrong but stumbled over a stupid bug I didn't > > have the time to look into. It seems that at some point I have > > reversed the logic of an 'if' statement s

Re: ScholarLy newbie, running annotate.ly, gets error message

Am 19.10.2015 um 16:53 schrieb David Kastrup: > Urs Liska writes: > >> Am 19.10.2015 um 16:36 schrieb Urs Liska: >>> You didn't do anything wrong but stumbled over a stupid bug I didn't >>> have the time to look into. It seems that at some point I have >>> reversed the logic of an 'if' statement

Re: ScholarLy newbie, running annotate.ly, gets error message

Urs Liska writes: > Am 19.10.2015 um 16:36 schrieb Urs Liska: >> You didn't do anything wrong but stumbled over a stupid bug I didn't >> have the time to look into. It seems that at some point I have >> reversed the logic of an 'if' statement so it spits out that error >> when everything is OK. >

Re: ScholarLy newbie, running annotate.ly, gets error message

Am 19.10.2015 um 16:36 schrieb Urs Liska: > You didn't do anything wrong but stumbled over a stupid bug I didn't > have the time to look into. It seems that at some point I have > reversed the logic of an 'if' statement so it spits out that error > when everything is OK. > > So if the results are

Re: ScholarLy newbie, running annotate.ly, gets error message

You didn't do anything wrong but stumbled over a stupid bug I didn't have the time to look into. It seems that at some point I have reversed the logic of an 'if' statement so it spits out that error when everything is OK. So if the results are what you expect please ignore *this* kind of error mes

Re: ScholarLY - introduction and call for collaboration

It is now working ABSOLUTELY BRILLIANTLY! Thanks for all your help. Craig On Tue Feb 03 2015 at 11:15:18 AM Urs Liska wrote: > > Am 03.02.2015 um 01:55 schrieb Craig Dabelstein: > > Dear Urs, > > Thanks so much for your advice. I tried both methods you suggest and > neither one worked, but th

Re: ScholarLY - introduction and call for collaboration

Am 03.02.2015 um 01:55 schrieb Craig Dabelstein: Dear Urs, Thanks so much for your advice. I tried both methods you suggest and neither one worked, but this did ... Originally I had: \include "../Notes/flute.ily" \include "part-init.ily" I reversed the order of these two lines and now it wo

Re: ScholarLY - introduction and call for collaboration

Dear Urs, Thanks so much for your advice. I tried both methods you suggest and neither one worked, but this did ... Originally I had: \include "../Notes/flute.ily" \include "part-init.ily" I reversed the order of these two lines and now it works perfectly. \include "part-init.ily" \include "../N

Re: ScholarLY - introduction and call for collaboration

Dear Urs, Thanks so much for your advice. I tried both methods you suggest and neither one worked, but this did ... Originally I had \include "part-init.ily" \include "../Notes/flute.ily" On Tue Feb 03 2015 at 9:51:03 AM Urs Liska wrote: > Hi Craig, > > it's like I expected (and not related

Re: ScholarLY - introduction and call for collaboration

Hi Craig, it's like I expected (and not related to \anntoate): Am 03.02.2015 um 00:00 schrieb Craig Dabelstein: Hi Urs, Here is a zip of the complete project. There are 2 issues: [1] If I put "part-init.ily" and "score-init.ily" in the top-most folder (the same folder as "main-init.ily"), li

Re: ScholarLY - introduction and call for collaboration

Am 31.01.2015 um 18:23 schrieb Urs Liska: Am 31. Januar 2015 18:14:23 MEZ, schrieb Craig Dabelstein : Urs, Another question ... Is there a reason why "main.init.ily", "part-init.ily" and "score-init.ily" can't be in the same folder? If I put "part" and "score" in a sub folder they can locat

Re: ScholarLY - introduction and call for collaboration

Am 31. Januar 2015 18:14:23 MEZ, schrieb Craig Dabelstein : >Urs, > >Another question ... Is there a reason why "main.init.ily", >"part-init.ily" >and "score-init.ily" can't be in the same folder? > >If I put "part" and "score" in a sub folder they can locate "main" in >the >folder above, howeve

Re: ScholarLY - introduction and call for collaboration

Urs, Another question ... Is there a reason why "main.init.ily", "part-init.ily" and "score-init.ily" can't be in the same folder? If I put "part" and "score" in a sub folder they can locate "main" in the folder above, however, if I put them all in the same folder I get "cannot find file main-ini

Re: ScholarLY - introduction and call for collaboration

Hi Urs, I followed your advice re: file structure -- "main-init.ily" has annotate, and "part.init.ily" and "score-init.ily" include "main.init.ily". When engraving the score it all works perfectly, but when engraving a part, it gives errors because it can't find "annotate". Any ideas? Craig O

Re: ScholarLY - introduction and call for collaboration

Am 31. Januar 2015 03:05:24 MEZ, schrieb Craig Dabelstein : >Thanks Urs, > >And you put the "\include annotate" code in the main-init.ily file? > Yes, and any similar code like the include of global-defs.ily etc. too. Urs >Craig > > >On Sat Jan 31 2015 at 8:05:57 AM Urs Liska wrote: > >> Hi

Re: ScholarLY - introduction and call for collaboration

Thanks Urs, And you put the "\include annotate" code in the main-init.ily file? Craig On Sat Jan 31 2015 at 8:05:57 AM Urs Liska wrote: > Hi Craig, > > Am 30.01.2015 um 17:59 schrieb Craig Dabelstein: > > Urs, > > Here is a zip of the complete project. > > > Thank you, this was indeed instr

Re: ScholarLY - introduction and call for collaboration

Hi Craig, Am 30.01.2015 um 17:59 schrieb Craig Dabelstein: Urs, Here is a zip of the complete project. Thank you, this was indeed instructive (and a nice score BTW). There is an issue with your set-up which I had immediately noticed and wanted to tell you about, even before I realized you h

Re: ScholarLY - introduction and call for collaboration

Am 30.01.2015 um 08:16 schrieb Urs Liska: Am 30.01.2015 um 08:13 schrieb Philippe Massart: Probably not. I assume that hash hasn't been properly filtered. Could you please post the generated .inp and maybe also the LilyPond file? Urs These are based on the sample file included : Ah, OK.

Re: ScholarLY - introduction and call for collaboration

Am 30.01.2015 um 09:35 schrieb Craig Dabelstein: Hi Urs, I put \include "scholarly/annotate.ily" in each of my 24 files -- one for each instrument. In the score I put: \include "scholarly/annotate.ily" \setAnnotationExportTargets #'("plaintext" "latex") I added 1 criticalremark and 1 musica

Re: ScholarLY - introduction and call for collaboration

Hi Urs, I put \include "scholarly/annotate.ily" in each of my 24 files -- one for each instrument. In the score I put: \include "scholarly/annotate.ily" \setAnnotationExportTargets #'("plaintext" "latex") I added 1 criticalremark and 1 musical issue to test it out. The generated parts (both the

Re: ScholarLY - introduction and call for collaboration

Am 30.01.2015 um 08:13 schrieb Philippe Massart: Probably not. I assume that hash hasn't been properly filtered. Could you please post the generated .inp and maybe also the LilyPond file? Urs These are based on the sample file included : Ah, OK. I see the offending LaTeX code, but I'll

Re: ScholarLY - introduction and call for collaboration

> > Probably not. I assume that hash hasn't been properly filtered. Could you > please post the generated .inp and maybe also the LilyPond file? > > Urs > These are based on the sample file included : annotate.annotations.inp Description: Binary data annotate.ly Description: Binary dat

Re: ScholarLY - introduction and call for collaboration

Am 30.01.2015 um 08:07 schrieb Philippe Massart: Hello, I’ tried the LaTeX package. Annotations are well included and it looks promising. But the beginning of the file causes an error due to the sharp symbol in the first part of the file (the part before the \musicalissue ) Error: (./annot

Re: ScholarLY - introduction and call for collaboration

Hello, I’ tried the LaTeX package. Annotations are well included and it looks promising. But the beginning of the file causes an error due to the sharp symbol in the first part of the file (the part before the \musicalissue ) Error: (./annotate.annotations.inp ./annotate.annotations.inp:1: You

Re: ScholarLY - introduction and call for collaboration

Dear Craig, thank you for the report. Am 30.01.2015 um 03:28 schrieb Craig Dabelstein: Dear Urs, I incorporated annotate into one of my current scores and it is fantastic. Great. Just to let me know: did you experience any troubles or is it as simple as I think to get it to run? I can'

Re: ScholarLY - introduction and call for collaboration

Dear Urs, I incorporated annotate into one of my current scores and it is fantastic. I can't wait for the Latex package to go along with it. Thanks for all you hard work. Craig On Wed Jan 28 2015 at 8:35:07 PM Noeck wrote: > > I hope my other reply is a sufficient answer to this? > > Yes, of

Re: ScholarLY - introduction and call for collaboration

> I hope my other reply is a sufficient answer to this? Yes, of course (and I agree). ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: ScholarLY - introduction and call for collaboration

Am 28.01.2015 um 11:11 schrieb Noeck: why we use so many discrete projects and repositories I would like to second this. I am much more likely to check things out (and perhaps contribute to things) that are in the openlilylib snippets as this is the only repo I have checked out besides the lily

Re: ScholarLY - introduction and call for collaboration

Hi Samuel, thanks for your thoughts. They are not offending at all but express valid concerns. However, I think there are good reasons to go the way I (and others) are going. All these things have to be seen in the context of an idea/project you can't know yet - "specifications" for a common

Re: ScholarLY - introduction and call for collaboration

> why we use so many discrete projects and repositories I would like to second this. I am much more likely to check things out (and perhaps contribute to things) that are in the openlilylib snippets as this is the only repo I have checked out besides the lilypond git. All other repos would be an e

Re: ScholarLY - introduction and call for collaboration

Dear Urs, Bravo! This is excellent work. I really appreciate all the time and effort you put into Lilypond. Craig maximesmusic.com On Wed Jan 28 2015 at 9:58:13 AM tyronicus wrote: > I must immediately excuse myself for not reading the blog post first and > seeing that ScholarLY is a part of

Re: ScholarLY - introduction and call for collaboration

I must immediately excuse myself for not reading the blog post first and seeing that ScholarLY is a part of openlilylib. But I still wonder about the rest. -- View this message in context: http://lilypond.1069038.n5.nabble.com/ScholarLY-introduction-and-call-for-collaboration-tp171140p171152.ht

Re: ScholarLY - introduction and call for collaboration

I am all in favor of the collaboration, but I wonder if I might pessimistically ask why we use so many discrete projects and repositories. It seems to me that we could accomplish much more by using one git project instead of having openlilylib, the LSR, and our newest projects, ScholarLY and GASP.