Re: ScholarLY - introduction and call for collaboration

[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 musical issue to test it out.

The generated parts (both the log and the inp) are printing each of the issues 25 times. See inp file attached.

Could you please also send the LilyPond files (or at least a few of the part files and the score)?

Urs

Craig

On Fri Jan 30 2015 at 5:16:33 PM Urs Liska <address@hidden> wrote:

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 have to look into the reason why this is generated.
The #f in the first line of the .inp file is the result of exporting something that evaluates to false.

Urs

Philippe

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

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