Dear Brother Samuel, > Before I post this to the users list I thought I'd post it to the > developers to give them a chance to double check my work. Also, are my > commits immediately available for user download or do they have to wait > for approval? In the latter case I obviously will want to wait for that > approval before posting this to the users (as they wouldn't be able to > find the changes before approval).
Your changes are available as soon as they're committed. I'm not able to test them anyway (I tried to install Mac OSX in a VM but wasn't really able to do so)... > I've made some improvements to my engine for TeXShop: > > Added Error Handling: > The engine will now check to make sure your score exists and will alert > you if it can't find it. If it find a converted version but not the > original gabc, the engine will issue a warning and proceed with the > compiled version. If it doesn't find either it issues an error and > gives you the option to abort immediately to fix the problem. That's good! > Improved Handling of File extensions: > The engine will now accept any extension on the included score. If the > extension is not provided it assumes it's looking for a file with the > extension tex. If it doesn't find the included file, then it looks for > gabc and runs gregorio on it. If it doesn't find that, well see above. Ok! > Added support for variant include commands: > The engine now recognizes \includescore, \includetexscore, and > \greincludescore and will run gregorio on any updated scores using these > commands. Also, \greincludegabcscore and \includegabcscore are also now > supported (the script does not compile these commands but lets lualatex > handle that as usual). Ok! The "gre"-prefixed commands are "internal" commands and not part of what users should use, but it doesn't hurt to support them... > Additional Engine: > For those of you combining modern and chant notation in the same > project, there is now a greg-lily-book.engine. After processing the > scores, this engine calls the LilyPond-Book engine instead of lualatex > so that it can properly process the lilypond portions of the file. Note, > to use this new engine you will need LilyPond-Book.engine v 2.0.4 or > higher. This version was just released 2014/03/23 (yesterday) in > response to a bug I found in it in the process of creating my engine. > You can find the update at > https://sole.dimi.uniud.it/~nicola.vitacolonna/software/lilypond-texshop/ > Also Note that you must provide an extension other than tex for included > scores (I suggest gtex). LilyPond-Book will be unable to find the > included scores if you don't. This is great! It's certainly worth some documentation and maybe a tutorial with some very short examples, I'm sure many people will be interested! What do you think? Thank you! -- Elie _______________________________________________ Gregorio-devel mailing list [email protected] https://mail.gna.org/listinfo/gregorio-devel
