Re: minor convert-ly problem

[Carl Sorensen]

On 1/30/11 3:33 PM, "Keith OHara" <address@hidden> wrote:

> Carl,
>    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 see the concern here.  I have thought about ways to fix it.  I haven't
come up with anything great.

> 
>    It seems appropriate to re-write the 2.13.4 rule to refer to the newest
> commands so users can find them in the release-version manual. I could try to
> write a patch but don't yet know what commands correspond to what old
> commands. (And, in this case, maybe you want to say "look at the default
> output first, and if adjustments are still needed, update manually.")

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.

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.

I'm thinking that perhaps the sanest way to deal with this is with the
UPDATE_MANUALLY string.  Perhaps it could be changed to say something like

"This advice may have changed for later versions.  Please review the current
manuals for this topic, and manually update your file to the current
syntax."

Thanks,

Carl