Re: LSR update?

[Thomas Morley]

Am Mi., 28. Dez. 2022 um 07:17 Uhr schrieb Werner LEMBERG <wl@gnu.org>:
>
>
> > Lateron, when LSR runs 2.24.0, we need to insert all snippets from
> > /Documentation/snippets/new.  This is tedious, any help would be
> > great.
>
> Sebastiano, if we send you an archive with all updated snippets: Do
> you have a possibility to mass-import them into the database?
> Submitting them one by one via the LSR web interface is not feasible.
>
> Ideally, there would be a git repository to which we can actually push
> the new files (to retain the editing history), and a script that
> regenerates the database automatically – and vice versa.

Werner, actually it's less work than expected.
Currently /Documentations/snippets/new contains 53 ly-files and 1
README as of 2023/1/1

9 files are really new ones:

  adjusting-figured-bass-alteration-glyphs.ly
  aligning-the-ends-of-hairpins-to-notecolumn-directions.ly
  customizing-the-chord-grid-style.ly
  customizing-the-no-chord-symbol.ly
  direction-of-merged-fa-shape-note-heads.ly
  measure-centered-bar-numbers.ly
  overriding-articulations-by-type.ly
  positioning-opposing-fermatas-on-a-bar-line.ly
  printing-tuplet-brackets-on-the-note-head-side.ly

I've already put them into LSR (unapproved and the code is commented).

##

Locally I updated the following 43 lsr-files by replacing the code by
the code from the relevant /new-snippets

  accordion-register-symbols.ly
  adding-an-ottava-marking-to-a-single-voice.ly
  adding-parentheses-around-an-expressive-mark-or-chordal-note.ly
  ancient-fonts.ly
  ancient-headword.ly
  ancient-notation-template----modern-transcription-of-gregorian-music.ly
  
automatically-changing-the-stem-direction-of-the-middle-note-based-on-the-melody.ly
  book-parts.ly
  centered-measure-numbers.ly
  changing-the-positions-of-figured-bass-alterations.ly
  changing-time-signatures-inside-a-polymetric-section-using--scaledurations.ly
  chant-or-psalms-notation.ly
  chord-names-alternative.ly
  controlling-tuplet-bracket-visibility.ly
  creating-a-delayed-turn.ly
  cross-staff-stems.ly
  customized-drum-notation-in-printed-and-midi-output.ly
  customizing-the-position-and-number-of-dots-in-repeat-sign-bar-lines.ly
  flute-slap-notation.ly
  generating-custom-flags.ly
  heavily-customized-polymetric-time-signatures.ly
  hymn-template.ly
  mensurstriche-layout-bar-lines-between-the-staves.ly
  modifying-default-values-for-articulation-shorthand-notation.ly
  modifying-the-ottava-spanner-slope.ly
  of-the-ubiquity-of-markup-objects.ly
  page-label.ly
  percussion-example.ly
  positioning-segno-and-coda-with-line-break.ly
  preventing-final-mark-from-removing-final-tuplet.ly
  printing-bar-numbers-at-regular-intervals.ly
  printing-bar-numbers-using-modulo-bar-number-visible.ly
  printing-marks-on-every-staff.ly
  printing-music-with-different-time-signatures.ly
  printing-the-bar-number-for-the-first-measure.ly
  repeats-headword.ly
  rhythmic-slashes.ly
  setting-the-minimum-length-of-hairpins.ly
  showing-the-same-articulation-above-and-below-a-note-or-chord.ly
  tam-tam-example.ly
  unfretted-headword.ly
  using-tags-to-produce-mensural-and-modern-music-from-the-same-source.ly
  vertical-aligned-staffgroups-without-connecting-systemstartbar.ly

These will be included in a tarball, which Sebastiano will need.

##

As soon as the LSR runs 2.24.0 and all above mentioned snippets are
in, for 9 of them the outdated description needs to be adjusted:

  adding-an-ottava-marking-to-a-single-voice.ly
  adding-parentheses-around-an-expressive-mark-or-chordal-note.ly
  
automatically-changing-the-stem-direction-of-the-middle-note-based-on-the-melody.ly
  centered-measure-numbers.ly
  changing-the-positions-of-figured-bass-alterations.ly
  controlling-tuplet-bracket-visibility.ly
  modifying-default-values-for-articulation-shorthand-notation.ly
  of-the-ubiquity-of-markup-objects.ly
  printing-the-bar-number-for-the-first-measure.ly

Afaict, this can't be done together with the code-upgrade.

> > As final step we need to delete the ones from
> > /Documentation/snippets/new and commit the new state, I would be
> > very thankful if someone else could do so.

In /Documentations/snippets/new only 1 snippet should stay

>
> I can help with that.

Many thanks!!
>
>
>     Werner

Cheers,
  Harm