[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: minor convert-ly problem
From: |
Keith OHara |
Subject: |
Re: minor convert-ly problem |
Date: |
Sun, 30 Jan 2011 22:20:52 -0800 |
User-agent: |
Opera Mail/11.01 (Win32) |
On Sun, 30 Jan 2011 16:13:10 -0800, Carl Sorensen <address@hidden> wrote:
On 1/30/11 3:33 PM, "Keith OHara" <address@hidden> wrote:
The commands to adjust automatic beaming changed at 2.13.4 and again at
2.13.29, with NOT_SMART conversion rules. Only the first rule is triggered on
scores for the last stable version, and it refers to commands in the 2.13.4
manual that users will not have.
[...]
I've put together a possible patch for it, but I don't really like it. I
think the rule should always be that convert-ly rules get written and never
changed.
Yes in general, but your patch probably changes only the transient output of
the conversion script. You could think of it as a translation to a new
language, post-2.13.29-lilypond-English. An alternative would be a new rule at
the 2.13.48 stage of conversion, to catch any leftover *-auto-beam-setting.
I think that if you took the time to draft a patch, it is probably worthwhile
to push.
There are other, older NOT_SMART rules that apply to autobeaming. I don't
think we should go back and rewrite them. But there are still old files out
there, even on Mutopia, the last time I checked. They would trigger the
first autobeaming rule, and we'd have the same problem as the 2.13.4 rule.
Well, the old NOT_SMARTs (usually) didn't indicate the new command names at
all. Then users have to search the manual for the topic instead of the new
command name, but that is probably the best thing to have happen.
-Keith