These old version numbers are actually very useful -- it allows the output to be updated with convert-ly. Now ideally somebody would update those scripts to use 2.12 syntax and output a 2.12 number, but in the absence of anybody willing to do this, I think the status quo is the best option.
Python is very easy to learn, so I would urge you to seriously consider updating the files -- the chance of anybody else doing it is quite low. Cheers, - Graham On Wed, Jun 17, 2009 at 06:44:15AM +0200, Villum Sejersen wrote: > > Hello group > From LilyPond version 2.13.2 in master branch, compiled two hours ago. > Some legacy hard-codings have survived in the output (I stumbled to the > fact > using midi2ly, but believe the other scripts should be updated to a more > automatic approach too): > In line 835 of the midi2ly script: version "2.7.18" > In line 1409 of abc2ly: version "2.7.40" > In line 1164 of etf2ly: version "2.3.25" > My Python skills being nill I cannot offer to rewrite the lines. > -- > yours sincerely Villum Sejersen > Nørregade 1 A > DK-4500 Nykøbing Sj. > Danmark > mobil +45 30 34 03 44 > [1]http://home20.inet.tele.dk/vsevisit/ > > References > > 1. http://home20.inet.tele.dk/vsevisit/ > begin:vcard > fn:Villum Sejersen > n:Sejersen;Villum > adr;quoted-printable;quoted-printable:;;N=C3=B8rregade 1 A;Nyk=C3=B8bing > Sj.;;DK-4500;Danmark > email;internet:v...@privat.tdcadsl.dk > tel;work:+45 59 66 67 77 > tel;home:+45 59 91 31 57 > tel;cell:+45 30 34 03 44 > x-mozilla-html:TRUE > url:http://home20.inet.tele.dk/vsevisit > version:2.1 > end:vcard > > _______________________________________________ > bug-lilypond mailing list > bug-lilypond@gnu.org > http://lists.gnu.org/mailman/listinfo/bug-lilypond _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond