Dear Elie, sorry, I don't understand what I should do to test your last version: where is it?
Thank you! Sr. Maria Ruth 2013/7/10 <[email protected]> > Send Gregorio-users mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://mail.gna.org/listinfo/gregorio-users > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Gregorio-users digest..." > > > Today's Topics: > > 1. avoiding clef duplication (?lie Roux) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 09 Jul 2013 15:29:39 +0200 > From: ?lie Roux <[email protected]> > To: gregorio-users <[email protected]> > Subject: [Gregorio-users] avoiding clef duplication > Message-ID: <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Dear all, > > I've been working quite hard on avoiding clef duplication at end and > beginning of lines, it has been really difficult (I even spotted a bug > in the LuaTeX core) but also interesting and I learned many things! > > My work has finally reached an usable state, and it's time for some > feedbacks: can you please test the latest svn version and tell me if it > solves your problems? Do no hesitate to criticize! > > There are two things to know though: > > * first in a syllable with a clef change, TeX will now raise errors > where it used to raise only warnings. For example in the example I > had (I'm sorry, I cannot remember from who it was), there were some > > \color{red}S\color{black} > > which is "illegal" in LaTeX, but works with a warning, this won't > work anymore and you'll have to use > > {\color{red}S} > > instead. The commands \hskip and \penalty are also forbidden; for > those who might use it... You can safely replace them by \grehskip > and \grepenalty. > > * second, it will make a good output only if you type a good syntax. > For instance, > > text(::)(c3)text > > will have the same buggy output as before, you have to use > > text(::c3) text > > instead. The recognized forms are (replacing c3 by any key, and :: > by any bar): > - (::c3) > - (c3) > - (z0c3) > - (z0::c3) > > There is still a little something I have to do (the centering on S(::c3) > is not very good), but on the overhaul it's ready for test, so please > test as much as you'd like! > > And also, don't forget it's been a tough and long work and that I'm > without a job for a few months ;) > > Thank you! > -- > Elie > > > > ------------------------------ > > _______________________________________________ > Gregorio-users mailing list > [email protected] > https://mail.gna.org/listinfo/gregorio-users > > > End of Gregorio-users Digest, Vol 55, Issue 8 > ********************************************* >
_______________________________________________ Gregorio-users mailing list [email protected] https://mail.gna.org/listinfo/gregorio-users
