[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
More bugs with convert-ly and postfix syntax
From: |
Larry Gilbert |
Subject: |
More bugs with convert-ly and postfix syntax |
Date: |
Thu, 9 Oct 2003 13:27:29 -0600 (MDT) |
I see that a bug I noticed in
convert-ly has been fixed in CVS. I have some more related bugs to
report. These are all examples from conversion of a 1.6.6 file.
First:
When there is a closing slur mark attached to a chord and a rest follows
the chord, conversion can incorrectly move the closing slur mark over to
the rest.
---[1.6.6 syntax sample]-----------------------------------------------
<)des4. f des'> r8 \bar ":|"
[ <des8 f aes> r <des ges bes> ] r |
---[Converted sample]--------------------------------------------------
<des f des'>4. r8) \bar ":|"
<des f aes>8[ r <des ges bes> ] r |
---[End samples]-------------------------------------------------------
Second:
Closing phrasing-slur marks ("\)") get broken up after conversion:
---[1.6.6 syntax sample]-----------------------------------------------
<des'4. des'> <beses8 beses'(> | <)aes4 aes'> aes' \( ( |
)aes16. ges32 f16. ees32 \) des8 r |
---[Converted sample]--------------------------------------------------
<des' des'>4. <beses beses'>8( | <aes aes'>4 aes') \( ( |
aes16.) ges32 f16. ees32 \ des8) r |
---[End samples]-------------------------------------------------------
Third:
Sometimes, when opening and closing slur marks are used in the middle of a
chord as the only delineation between two notes, the converter correctly
moves the slur mark but neglects to leave a space between the notes.
---[1.6.6 syntax sample]-----------------------------------------------
r8 <ges,,4 ges'> \clef "violin" <c'''8(ees> ~ |
[ <c16 ees> <des)f> ]
---[Converted sample]--------------------------------------------------
r8 <ges,, ges'>4 \clef "violin" <c'''ees>8( ~ |
<c ees>16[ <desf>) ]
---[End samples]-------------------------------------------------------
Fourth:
The converter does not account for string literals, and happily converts
anything that looks like note data in need of postfix conversion.
---[1.6.6 syntax sample]-----------------------------------------------
tagline =
"\\parbox{\\hsize}{\\thefooter\\quad\\small\\noindent\\hspace{\\stretch{1}}
This music is part of the Mutopia project: \\hspace{\\stretch{1}}
\\texttt{http://www.MutopiaProject.org/}\\\\ \\makebox[\\textwidth][c]{It
has been typeset and placed in the public domain by " + \maintainer + ".}
\\makebox[\\textwidth][c]{Unrestricted modification and redistribution is
permitted and encouraged---copy this music and share it!}}"
---[Converted sample]--------------------------------------------------
tagline =
"\\parbox{\\hsize}{\\thefooter\\quad\\small\\noindent\\hspace{\\stretch{1}}
This music is part of the Mutopia project: \\hspace{\\stretch{1}}
\\texttt{http://www.MutopiaProject.org/}\\\\ \\makebox[\\textwidth] c[]{It
has been typeset and placed in the public domain by " + \maintainer + ".}
\\makebox[\\textwidth] c[]{Unrestricted modification and redistribution is
permitted and encouraged---copy this music and share it!}}"
---[End samples]-------------------------------------------------------
I hope this information is helpful. Please let me know if I can be of
further help. I think LilyPond is great!
--
Larry Gilbert
Renton, WA, USA
address@hidden
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- More bugs with convert-ly and postfix syntax,
Larry Gilbert <=