Re: [LSR v2.18] A step by step manual procedure
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 carefully in order to comfortating all of us that this work is not a waste of time. All comments and suggestion are, of course, warmly welcome. Since english is not my native langage please feel free to ask for precision if any doubt. FIRST ROUND : 1. open all file in an alphabetical order; 2. open the first non-upgraded snippet with your favorite editor (Frescobaldi/Windows is really helpful since it compiles with any version you want); ;; Note: non-uppgraded snippets have no attached pdf 3. copy the doctitle; ;; e.g. doctitle = Overriding articulations of destinct type 4. googlize the doctitle; ;; e.g. site:lilypond.org/doc/v2.18 site:lilypond.org/doc/v2.18 Overriding articulations of destinct type 5. IF it matches : copy/paste the v2.18 doc code THEN 5.1. ELSE 6.; 5.1. find the snippet in the LSR by using search; ;; e.g. Overriding articulations 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 automatically update the syntax, the snippets will be more future-proof and you have less trouble with syntax changes. In short: isn’t that what convert-ly is made for? 5.3. delete LSR \header 5.4. compile (no particular reason here that warnings will occur but check the terminal anyway); 5.5. compare the output with the LSR output; 5.6. change some settings if needed in oder to reach the same output look (alignments have changed since v2.14); 5.7. delete version-statements; Why? Wouldn’t it be good to know that for the future? 5.8. add the LSR link on the top as an incommented line; ;; e.g. %% http://lsr.dsi.unimi.it/LSR/Item?id=774 ;; Note: this could be pretty helpfull and will save time for future upgrades/updates. 5.9. optional : if possible, add any relevant links as incommented lines; ;; e.g. %% see also http://lilypond.org/doc/v2.18/Documentation/notation/modifying-single-staves#ossia-staves ;; e.g. %% upgraded by ... see http:/... 5.10. save the snippet 5.11. IF all daily work snippets have been upgraded THEN 9. ELSE 2.; 6. find the snippet in the LSR by using search; ;; e.g. Ossia staves 6.1. delete LSR \header and update the snippet to v2.18; 6.2. compile the snippet and check for warnings; 6.3. IF it compiles without any or abnormal warning THEN 6.4. ELSE 7. 6.4. IF the code looks like a v2.18 one or can easily be upgraded AND IF the ouput, the title and the description don't seem obsolete THEN 5.5. ELSE 8. 7. googlize the title, part of the title, part of the code into the usual LilyPond sites, boards or lists to chek for higher/better code that would do the job. 7.1. IF it matches copy/paste the link(s) as an incommented line (add any comments if needed), copy/paste the new code THEN 5.5. ELSE 8.; ;; 7. 7.1 are fairly important and save a bunch of times since it avoids sending silly questions to the BugSquad as I did at the very beginning... 8. IF it does not match OR IF it's possibly obsolete OR IF no simple correction (see P.S.) can be applied, send a message to the BugSquad with explanation, with or without ideas, codes or any remark that could be helpful; 8.1. delete the attached pdf and/or other outputs; 8.2. add a number at the snippet file name (#00 for waiting room, #0 for deleted, #1 for modificated and #2 for upgraded) in order to gathered them on the top of the list. 8.3. wait for a new code to be send by the Squad and GOTO 5.4.; 9. Save All file on an external memory (could also prevent from some suicidal thoughts). ;; The weakest point of this manual update is that it multiplies the error risk by 700 (roughly the number of snippets). ;; Therefor i'll go for a second round. ;; Since I'm not at that stage, the hereunder lines are expected but will surely be extended or modified in a near future. SECOND ROUND: 1. copy/paste all file and rename it all OLD; 2. in the external memory rename the saved all file as all OLD 3. open all and delete files other than *.ly files; 4. check in the LSR the #0*.ly snippets that have already been deleted; 5. delete the relevant #0*.ly snippets in all; 6. rename the other #00*.ly #0*.ly #1*.ly and #2*.ly snippets as they originaly were; 7. open and check *.ly files one after the other : 7.1 check that there's no version-statements; 7.2 check that there's no LSR header; 7.3 check that, at least, the first line starts with the incommented snippet link; 7.4 compile and check terminal for any other warning than the no \version statement found one; 8. Save All file on an external memory; 9. create
Re: [LSR v2.18] A step by step manual procedure
2014-02-18 9:33 GMT+01:00 Noeck noeck.marb...@gmx.de: 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 version 2.14.2 (or what ever the file is) to 2.18.0? That way you would automatically update the syntax, the snippets will be more future-proof and you have less trouble with syntax changes. In short: isn’t that what convert-ly is made for? At that stage I copy/paste a v2.18 code since it's taken from the v.218 doc. There is no reason for the syntax to be false here. Plus, the v2.18 doc codes are sometimes enhanced, things that convert-ly cannot do. A good example here : - the v2.14 snippet : http://lsr.dsi.unimi.it/LSR/Item?id=501 - the v2.18 output : http://lilypond.org/doc/v2.18/Documentation/ly-examples/bach-schenker.png [...] 5.7. delete version-statements; Why? Wouldn’t it be good to know that for the future? Because it has to be so (see #7 : http://lilypond.org/doc/v2.17/Documentation/contributor/updating-the-lsr-to-a-new-version ) Anyway LSR will be v2.18... Cheers, Pierre ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Midi early start (2.19.2)
On Tue, Feb 11, 2014 at 8:40 PM, Jay Anderson horndud...@gmail.com wrote: Removing the Dynamic_performer causes rests at the start of a piece to be skipped causing misalignment with other voices. I've only tested this with 2.19.2 and 2.18.0. It works correctly in 2.18.0. Thanks, Jay Anderson - This has been submitted as Issue 3871 : https://code.google.com/p/lilypond/issues/detail?id=3871 Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [LSR v2.18] A step by step manual procedure
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 automatically update the syntax, the snippets will be more future-proof and you have less trouble with syntax changes. In short: isn’t that what convert-ly is made for? At that stage I copy/paste a v2.18 code since it's taken from the v.218 doc. There is no reason for the syntax to be false here. Ok, so a perfect example of “I am misunderstanding what you are doing.” Sorry for the noise. Cheers, Joram ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [LSR v2.18] A step by step manual procedure
Hello, 2014-02-18 0:45 GMT+01:00 Pierre Perol-Schneider pierre.schneider.pa...@gmail.com: 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 are, of course, warmly welcome. Since english is not my native langage please feel free to ask for precision if any doubt. [very long instructions] 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!) I think that this may be an indicator that there's something wrong with how LSR is working. I find it hard to believe that things have to be that complicated :/ best, Janek ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [LSR v2.18] A step by step manual procedure
2014-02-18 19:16 GMT+01:00 Janek Warchoł janek.lilyp...@gmail.com: 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 indicator that there's something wrong with how LSR is working. I find it hard to believe that things have to be that complicated :/ 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 ? Cheers, Pierre ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [LSR v2.18] A step by step manual procedure
Hi Pierre, 2014-02-18 21:03 GMT+01:00 Pierre Perol-Schneider pierre.schneider.pa...@gmail.com: 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.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
[LSR v2.18] Page spacing obsolete
Hi BugSquad, Could you check if this snippet : http://lsr.dsi.unimi.it/LSR/Item?id=227 should be deleted Cheers, Pierre ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
[LSR v2.18] Parenthesize note heads using a Scheme function interest ?
Hi Squad, In this snippet : http://lsr.dsi.unimi.it/LSR/Item?id=186 code could still be interesting but snippet's obsolete. What do you think ? Cheers, Pierre ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
[LSR v2.18] Positioning fingering indications precisely fingernings crashes in the doc.
Hi Squad,
See the doc :
http://www.lilypond.org/doc/v2.18/Documentation/snippets/editorial-annotations#editorial-annotations-positioning-fingering-indications-precisely
fingerings are crashing on many chords.
Please find hereunder the settings to reach a similar output to :
http://lsr.di.unimi.it/LSR/Item?id=551
\relative c' {
\set fingeringOrientations = #'(left)
c-1 d-2 a'-54
c-1 d-\tweak extra-offset #'(0 . 0.2)-2 a'-54
\set fingeringOrientations = #'(down)
c-1 d-2 a'-54
c-\tweak extra-offset #'(0 . -1.1)-1 d-\tweak extra-offset #'(-1.2 .
-1.8)-2 a'-54
\set fingeringOrientations = #'(down right up)
c-1 d-\tweak extra-offset #'(-0.3 . 0)-2 a'-54
c-1 d-\tweak extra-offset #'(-1 . 1.2)-2 a'-54
\set fingeringOrientations = #'(up)
c-1 d-\tweak extra-offset #'(0 . 1.1)-2 a'-\tweak extra-offset #'(0 .
1)-54
c-1 d-\tweak extra-offset #'(-1.2 . 1.5)-2 a'-\tweak extra-offset #'(0 .
1.4)-54
}
%
Cheers,
Pierre
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
