Hi Pierre,
2014-02-18 21:03 GMT+01:00 Pierre Perol-Schneider
:
> I'd like to open a thread about starting a track to help an LSR revival.
> Should I open it on the bug or the user'rs list ?
-user, i think.
___
bug-lilypond mailing list
bug-lilypond@gnu
2014-02-18 19:16 GMT+01:00 Janek Warchoł :
> Hello,
>
>
Hi Janek
> oh my - this looks very complicated. I have to admit that i wouldn't
> have the patience to do this - kudos to you (and other volunteers!)
>
Yep, but I think it will cover a nice cleaning.
>
> I think that this may be an ind
Hello,
2014-02-18 0:45 GMT+01:00 Pierre Perol-Schneider
:
> Hi All,
>
> As promised here's the step-by-step procedure I'm following to manually
> upgrade the LSR.
> For sure this is not the most facinating literature but I deeply request
> you to read it carefully in order to comfortating all of u
Hi Pierre,
> > 5.2. change \version "2.14.2" for \version "2.18.0"
> [...]
> Perhaps, I am misunderstanding what you are doing. But wouldn’t it be
> better to use convert-ly here for upgrading from version 2.14.2 (or what
> ever the file is) to 2.18.0?
> That way you would
2014-02-18 9:33 GMT+01:00 Noeck :
> Hi Pierre,
>
Hi Noek,
> please find two comments inline:
>
[...]
> > 5.2. change \version "2.14.2" for \version "2.18.0"
> [...]
> Perhaps, I am misunderstanding what you are doing. But wouldn’t it be
> better to use convert-ly here for upgrading from versi
Hi Pierre,
please find two comments inline:
Am 18.02.2014 00:45, schrieb Pierre Perol-Schneider:
> Hi All,
>
> As promised here's the step-by-step procedure I'm following to manually
> upgrade the LSR.
> For sure this is not the most facinating literature but I deeply request
> you to read it ca
Hi All,
As promised here's the step-by-step procedure I'm following to manually
upgrade the LSR.
For sure this is not the most facinating literature but I deeply request
you to read it carefully in order to comfortating all of us that this work
is not a waste of time.
All comments and suggestion a