Hi James, Hi Harm, Hi David, On 2014-02-13 22:47 GMT+01:00 James wrote: *Isn't there a standard practice for making a snippet shown as deprecated?*
Never heard of. On 2014-02-14 0:10 GMT+01:00 Harm wrote: *Did you succed contacting Seba already? * No I don't. No answer up to now. On 2014-02-14 0:10 GMT+01:00 Harm wrote: *Do you have a list of snippets making troubles?* Yes I do. On 2014-02-14 0:10 GMT+01:00 Harm wrote: *If so, please post it and call for help, it's way too much work for a single person!* Already done and I will, thanks (see my "step-by-step procedure" at the end of my respond for details). On 2014-02-14 0:10 GMT+01:00 Harm wrote: *If you have editing privileges [...]* I don't. Now for those remarks and questions : On 2014-02-14 0:10 GMT+01:00 Harm wrote: *Any objections?* On 2014-02-14 0:10 GMT+01:00 Harm wrote: *I seem to remember that I noticed several snippets, where the scheme-functions would not work with newer versions. Others are using some (very) complicated stuff to do things, that nowadays can be reached ways easier. Worth recoding. Though, I'd not do it _during_ the upgrade, _if_ they compile.* On 2014-02-14 7:42 GMT+01:00 David wrote : *Uh, the snippets tagged "docs" are all imported in LilyPond anyway, so one should just take them from Documentation/snippets/new (if they required changes more than running convert-ly).* On 2014-02-14 9:27 GMT+01:00 David wrote : *Well, one problem we definitely have is that a) Documentation/snippets is at version 2.19.2 b) the versions have been upgraded at least to 2.16.0[...]I have the suspicion that it will be tedious anyway.* +1 :) On 2014-02-14 9:27 GMT+01:00 David wrote : *[...] unless that snippet just continued to compile but stopped doing what it should, and nobody noticed so far in our documentation).* On 2014-02-14 10:05 GMT+01:00 David wrote : *[...] If it isn't at all in Documentation/snippets/new, then it should convert cleanly with convert-ly (unless that snippet just continued to compile but stopped doing what it should, and nobody noticed so far in our documentation).* Here's what I'll do : 1) Within few days, probably this week-end, I'll send you a "step-by-step procedure" of what and how I'm doing. What I can tell you now is that I finally choose to update each snippet manually. Reason is that the number of problematic snippets is not that high and I definitly think that it would be more accurate. 2) because of this manual choice, I'll send you questions from time to time. 3) In any case, at the end of my work, I'll send you 3 lists : - List of snippets that should be deleted - List of snippet that have major modification - List of snippet that should be upgraded Now for the other remarks, at this point, I'm not sure to know what to anwer... Thank you all, Pierre _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
