Re: LSR -> lilypond docs

[Mats Bengtsson]

As I have said earlier, I think it would be a big loss if the
web site could not provide the full documentation for
multiple old version, including a "complete" set of example files
with the correct syntax for the corresponding version.

We cannot expect all users to always stay upgraded with the
absolutely latest LilyPond version (for example if they use
a LilyPond packaged together with some Linux distribution
or find an older version good enough for their purposes and
don't want to go through the hazzle of upgrading all existing
.ly files).
I regularly use the currently available Tips and Tricks and
Regression test documents for old LilyPond versions when
answering questions on the mailing list. I would also expect
the number of such questions to increase if all of a sudden
the set of examples was not available for older versions.

I'm fully aware of all the advantages of LSR and exploiting
this examples in the official docs, but I don't want to lose
the support for multiple versions.

  /Mats

Graham Percival wrote:

> Valentin Villenave wrote:
>
> > 2007/11/10, Graham Percival <address@hidden>:
> >
> > > LSR finally has tags, so it's time to describe how LSR and the lilypond
> > > docs are linked.
> >
> > > you'll probably be mad at me for cutting hair again, but I couldn't
> > help notice on the page
>
>
> This isn't cutting hair in the least.  Granted, I remember discussing
> this a few months ago.  But if there's anything like this that you're
> not clear about, please ask.
>
> > Here, it appears to be 2.11.32 (though the LSR is, IIRC, still running
> > 2.10.something).
> >
> > Does it mean that integrated LSR snippets will automatically be
> > upgraded to the last LilyPond version (which the GDP is supposed to
> > document)?
>
>
> Yes.  Well, run through convert-ly.  This may or may not automatically
> perform all the updates; it depends on convert-ly.
>
> > Isnt'it a bit ackward if LSR snippets and GDP snippets have a slightly
> > different syntax?
>
>
> Yes, but this is unavoidable.  Lilypond GIT needs to compile with the
> specific version of lilypond.  The best we can do is run the snippets
> through convert-ly.
>
> If you're going to ask about upgrading LSR, bear in mind that this
> involves an unknown amount of work from Sebastiano, and that 2.11.34
> contains known serious bugs.  Based on the reaction to .35, I might
> propose .36 as a candidate for LSR-upgrading.
>
> The tentative plan is to upgrade LSR to a 2.12 beta release, then
> upgrade it again to 2.12.2 or .3 -- ie a stable 2.12.
>
> Cheers,
> - Graham
>
>
>
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/lilypond-user



--
=============================================
        Mats Bengtsson
        Signal Processing
        Signals, Sensors and Systems
        Royal Institute of Technology
        SE-100 44  STOCKHOLM
        Sweden
        Phone: (+46) 8 790 8463                         
       Fax:   (+46) 8 790 7260
        Email: address@hidden
        WWW: http://www.s3.kth.se/~mabe
=============================================