Re: LSR updates: was: polychords: a working solution

[Carl Sorensen]

On 2/19/12 10:51 AM, "Thomas Morley" <address@hidden> wrote:

>Hi David,
>
>2012/2/19 David Nalesnik <address@hidden>:
>> Hi Harm,
>>
>> On Sun, Feb 19, 2012 at 8:32 AM, Phil Holmes <address@hidden>
>>wrote:
>>>
>>>
>>>  2) "correct" the syntax of the files you know have errors ready for
>>>that
>>> move.  Which you do is up to you -  bear in mind that if you go for
>>>2), then
>>> it's possible that the work will be wasted if we struggle to get the
>>>LSR
>>> updated.  However, you will at least be prepared.
>>>
>>
>> If you'd like to go the route of updating syntax in the problem files to
>> 2.14, then I'll be happy to take on part of the task.  Just let me know!
>>
>> -David
>
>I fixed already following files:
>
>Altering-the-number-of-stems-in-a-beam.ly
> I changed the old override-auto-beam-setting.
>
>automatic-beams-two-per-two-in-4-4-or-2-2-time-signature.ly
> I changed the old override-auto-beam-setting.
>
>coloring-individual-staff-lines.ly
> I added the definition for interval-translate from 2.12.3
> Better use an other fix?
>
>how-to-define-autobeamsettings-in-the‹layout-block.ly
> I changed the autoBeamSettings.
>
>Including-a-file-only-once.ly
> I reimplemented the relevant definitions from "2.12.3"
> Better use an other fix?
>
>Obtaining-a-tablature-for-open-tuning-and-or-normal-tuning.ly

This snippet may be no longer needed due to changes in tablature.

> I replaced the number-lists with pitches-lists.
> Better implementation with makeStringTuning?
> TODO handle the log-warning: warning: no such internal option:
>open-tuning
> TODO change the description
>
>overriding-automatic-beam-settings.ly
> I changed the old override-auto-beam-setting and a comment.

I think that this snippet is no longer needed because of the new autobeam
syntax which is in the docs.

>
>Positioning-tuplet-numbers-close-to-kneed-beams.ly
> I changed 'thickness to 'beam-thickness as the author suggested (line
>64).
>
>specifying-context-with-beatgrouping.ly
> I changed beatGrouping to beatStructure
> Suggestion: New Title: doctitle = "Specifying context with beatStructure"

I believe this is also covered adequately in the docs.
>
>template-for-multiple-instruments,-prints-a-score-and-parts.ly
> I changed the old override-auto-beam-setting.
>
>use-custom-fonts-flat-b-and-sharp-#-symbols-for-chords.ly
> I simply added added lowercase? To the definition of
>my-chord-name->pop-markup
> Of course lowercase? Is of no use here. A better fix would be more
>invasive.
>
>I didn't manage to fix:
>filtering-parts-from-the-command-line.ly
>mixed-meter---automatic-compound-time-signatures.ly
>
>
>May I ask you and any other interested user for review and perhaps
>ideas for the remaining files?
>

Thanks for your work on this.

Carl