Re: ScholarLY - introduction and call for collaboration

2015-02-02 Thread Craig Dabelstein
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

2015-02-02 Thread Urs Liska
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

2015-02-02 Thread 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 works perfectly. \include "part-init.ily" \include "../N

Re: ScholarLY - introduction and call for collaboration

2015-02-02 Thread 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 "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

2015-02-02 Thread Urs Liska
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

2015-02-02 Thread Urs Liska
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

2015-01-31 Thread 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 locate "main" in >the >folder above, howeve

Re: ScholarLY - introduction and call for collaboration

2015-01-31 Thread 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, however, if I put them all in the same folder I get "cannot find file main-ini

Re: ScholarLY - introduction and call for collaboration

2015-01-31 Thread Craig Dabelstein
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

2015-01-30 Thread Urs Liska
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

2015-01-30 Thread Craig Dabelstein
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

2015-01-30 Thread Urs Liska
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

2015-01-30 Thread Urs Liska
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

2015-01-30 Thread Urs Liska
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

2015-01-30 Thread 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 musical issue to test it out. The generated parts (both the

Re: ScholarLY - introduction and call for collaboration

2015-01-29 Thread 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. I see the offending LaTeX code, but I'll

Re: ScholarLY - introduction and call for collaboration

2015-01-29 Thread 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 : annotate.annotations.inp Description: Binary data annotate.ly Description: Binary dat

Re: ScholarLY - introduction and call for collaboration

2015-01-29 Thread Urs Liska
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

2015-01-29 Thread 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: (./annotate.annotations.inp ./annotate.annotations.inp:1: You

Re: ScholarLY - introduction and call for collaboration

2015-01-29 Thread Urs Liska
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

2015-01-29 Thread Craig Dabelstein
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

2015-01-28 Thread Noeck
> 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

2015-01-28 Thread Urs Liska
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

2015-01-28 Thread Urs Liska
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

2015-01-28 Thread 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 lilypond git. All other repos would be an e

Re: ScholarLY - introduction and call for collaboration

2015-01-28 Thread Craig Dabelstein
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

2015-01-27 Thread tyronicus
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

2015-01-27 Thread tyronicus
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.