Nick Payne <[email protected]> writes: > On 31/12/13 11:13, David Kastrup wrote: >> Noeck <[email protected]> writes: >> >>> Am 31.12.2013 00:35, schrieb Eluze: >>>> Tom Cloyd-2 wrote >>>>> Running convert-ly (from Frescobaldi) on a score, I get this at the top >>>>> of the code: >>>>> >>>>> \version "2.17.97" >>> I can confirm this using version 2.18.0 (both within Frescobaldi and on >>> the commandline). I also would have expected 2.18.0 after the conversion. >> It's due to a miscommunication between myself and Phil. This is >> harmless though a bit of a nuisance. Most of the time, you'll want to >> use the -d option anyway to avoid declaring a larger version than >> necessary: in that case this oversight will not have an effect. >> >> If you want to really have the version display converted to 2.18.0, you >> can use -t 2.18.0 I think. > > No, with 2.18.0 convert-ly, using the -t 2.18.0 option still leaves > the version number in the file at 2.17.97 (Linux amd64).
Shucks. Well, as I said it's harmless, and it's fixed in master and stable branches already. Once you use the convert-ly from either 2.19.0 or 2.18.1, things will look prettier. -- David Kastrup _______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
