Issue 788 in lilypond: simpler convert-ly rules

[codesite-noreply]

Status: Accepted
Owner: gpermus
Labels: Type-Enhancement Priority-Postponed Maintainability

New issue 788 by gpermus: simpler convert-ly rules
http://code.google.com/p/lilypond/issues/detail?id=788

This looks sub-optimal:
------
def conv (str):
    str = re.sub (r"\\octave(?![a-zA-Z])", r"\\octaveCheck", str)
    str = re.sub (r"arpeggioUp", r"arpeggioArrowUp", str)
    str = re.sub (r"arpeggioDown", r"arpeggioArrowDown", str)
...
------

arpeggio* should have \\ as well.  Also, they should also be
matched with full words.  In fact, "lots" of the convert-ly rules
need to match a complete word.

1)  Could somebody verify this (look in the python docs, run a few
tests, whatever... not that I doubt Daniel; just that we should
make sure).

2)  Could somebody consider writing a nicely-named-function such
that the convert-ly rules look like this?

def conv (str):
    str = f("\\oldCommand", "\\newCommand", str)
?

It's silly for people to manually add \b everywhere, and it's
equally silly for contributors to say "oh, I can't touch
convert-ly, since I don't know python".  Let's make it easy to
write/modify those rules.



--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings