On Wed, 10 Sep 2003 12:50:37 +0200
Mats Bengtsson <[EMAIL PROTECTED]> wrote:
> Aaron wrote:
> > I have a template which I created in 1.6.0 and I am using 1.8.0.
> > I changed the version field in the template to 1.7.28 which is what the
> > convert-ly -e does on an already created file.
>
> The pri
What is the problem? If you upgrade your LilyPond installation, you
have to learn the syntax of the new version. There are no huge
differences but several smaller ones. One good way of learning the
differences is to run an old example through convert-ly and see what
it changes.
/Mats
Aaron wrot
Hm I cc to the group...
>
> I don't really understand what you mean, do you have both 1.6 and 1.8
> installed at the same time? Since convert-ly never will be able to
> update exactly all incompatibilities between versions, I definitely
> recommend to write all new files for the LilyPond version y
The principle is very simple:
- You specify the version number of the LilyPond version where you
know that the file works.
- When you have upgraded LilyPond, just run convert-ly -e fily.ly,
which will update the file to work with your new LilyPond version
(among others, it will update the ver
Hi again,
I have a template which I created in 1.6.0 and I am using 1.8.0.
I changed the version field in the template to 1.7.28 which is what the
convert-ly -e does on an already created file.
I can't however parse the file and now convert-ly -e doesn't work
either.
I am confused about what ver
