[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bug] convert-ly \newpage
From: |
Graham Percival |
Subject: |
Re: [bug] convert-ly \newpage |
Date: |
Tue, 17 Aug 2004 17:26:25 -0700 |
Thanks for asking me to look at it -- convert-ly.py was a lot more
understandable than I thought it would be.
I still haven't figured out how to build lilypond on OSX, but I will
soon. In Sept I'm moving away to do a second bachelor (this time in
music), and I've decided not to get internet access in my apartment --
this should force me to work on university, composition, or other
important things (including lilypond) instead of reading slashdot and
wasting time. (I'll have 'net access at university, so I could
upload patches then)
Anyway, I haven't tested this, but I think it's the right format.
I don't want to add something to CVS without testing it first. :)
Produced via diff -u
Cheers,
- Graham
--- scripts/convert-ly.py Tue Aug 3 09:47:00 2004
+++ scripts/convert-ly.py.new Tue Aug 17 17:19:32 2004
@@ -2144,7 +2144,12 @@
conversions.append (((2, 3, 10), conv,
'''\\addlyrics -> \\oldaddlyrics, \\newlyrics ->
\\addlyrics'''))
+def conv (str):
+ str = re.sub (r'\\newpage'. r'\\pageBreak', str)
+ return str
+conversions.append (((2, 3, 12), conv,
+ '''\\newpage -> \pageBreak'''))
def conv_mode_experiment (str):
str = re.sub (r'\\chords\b', r'\\chordmode', str)