[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: convert-ly bug
From: |
David Bobroff |
Subject: |
Re: convert-ly bug |
Date: |
11 Oct 2004 22:53:36 +0000 |
On Mon, 2004-10-11 at 22:48, Jan Nieuwenhuizen wrote:
> David Bobroff writes:
>
> > A few hours ago I built LilyPond from CVS sources. That was at ChangeLog
> > 1.2711. I ran convert-ly on a file and Lily choked on it. I had to change
> > an instance of \bookpaper to \paper. Shouldn't convert-ly have taken care
> > of that for me?
>
> Yes it should. Did your input file have a \version statement,
Yes, it did. It had \version "2.3.18" and still does.
> and did
> you rebuild convert-ly?
I did a make-clean; make all. Would that rebuilt convert-ly?
>
> > I just update my LilyPond sources from CVS again and did
> > not see any changes to convert-ly.
>
> Changes were made yesterday. What does
>
> grep -3 bookpaper scripts/convert-ly.py
>
> say?
address@hidden lilypond]# grep -3 bookpaper scripts/convert-ly.py
def conv (str):
str = re.sub (r'\\paper', r'\\layout', str)
str = re.sub (r'\\bookpaper', r'\\paper', str)
str = re.sub (r'paper-set-staff-size', r'layout-set-staff-size',
str)
return str
conversions.append (((2, 3, 22),
conv,
'''paper -> layout
bookpaper -> paper''' ))
################################
# END OF CONVERSIONS
address@hidden lilypond]#
-David