[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: abc2ly produces bad output
From: |
rog peppe |
Subject: |
Re: abc2ly produces bad output |
Date: |
Thu, 18 Mar 2010 08:06:13 +0000 (UTC) |
User-agent: |
Loom/3.14 (http://gmane.org/) |
Reinhold Kainhofer <reinhold <at> kainhofer.com> writes:
> Just exchange the handling of slurs with closing tuplets in try_parse_note:
>
> if slur_begin:
> voices_append ('-(' * slur_begin )
> if slur_end:
> voices_append ('-)' *slur_end )
> if parser_state.parsing_tuplet:
> parser_state.parsing_tuplet = parser_state.parsing_tuplet - 1
> if not parser_state.parsing_tuplet:
> voices_append ("}")
yes. one remark though: this code is a little misleading
slur_begin is never actually used - state.next_articulation is used
for the opening bracket; slur_begin is set within
try_parse_articulation but it's only a local variable
there. it could be deleted without affecting the code.
i'm a total lilypond newbie - what do the leading
minus signs do for the slur? i couldn't find an entry
for "-" in the lilypond command index other than
as a note suffix, but the parser does seem to accept it.