Re: Text listing output in .txt file

[Jan-Peter Voigt]

Hi Daniel and all others,

you wrote about a critrical edition. There is scholarly: https://github.com/openlilylib/scholarly
where you can add annotations to your score which then can be collected in another file.
If you want to use the EE for tracking, you might use \applyContext #(lambda (context) ... ) .
Of course you can use this function right inside your code.

I am not at my computer right now, so I can not provide an example (yet). But perhaps someone else can make use of this idea.

HTH
Jan-Peter

Am 2. August 2017 19:02:34 MESZ schrieb Kieren MacMillan <address@hidden>:

Hi Daniel,

 For example, if I change a g-sharp to a g-natural, I would
 like to write on a line of code "g-sharp changed to g-natural" that then
 would be listed on a text file that I can copy to my critical commentary.

Have you looked at the edition engraver? That kind of edition control is *precisely* its fundamental purpose — and I wouldn't think it would take much to transform a list of editionMod-s (i.e., tweaks) into a text file in any format you desired.

(Note: I use the EE extensively, in every score I engrave, but only for aesthetic/tweak purposes, not to track changes as you are suggesting.)

Hope that helps,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: address@hidden



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

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.