Hi Phil, 2012/2/19 Phil Holmes <m...@philholmes.net>:
> It looks like what you've done is exactly right for preparing for updating > the LSR. I think you have 2 options: 1) wait until we know that the LSR > will be moved to 2.14 before doing anything else; or 2) "correct" the syntax > of the files you know have errors ready for that move. Which you do is up > to you - bear in mind that if you go for 2), then it's possible that the > work will be wasted if we struggle to get the LSR updated. However, you > will at least be prepared. I started with 2) > > A few other comments to let you understand the LSR as well as I do - which > isn't huge. > > It's used for 2 things, really - the online searchable index, and also to > create snippets that can be put in the documents. These are tagged with > "docs" in the LSR and are then included in the documentation package by > copying them over and running makeLSR on them. That's where the snippets in > the URL you showed from Savannah come from - they're a subset of the full > LSR. When one of the "docs" snippets is known not to work on the latest > development version, a working version is created in snippets/new, and this > is used in the build system in preference to the original. This is > therefore a further indication of which snippets won't work, although only > of the ones tagged 'docs' Thanks for clarification. More questions. :) In the LSR-download I found several sub-directories like: "all" "ancient-notation" "automatic-notation" etc I only worked on the files from "all". Correct? Or should I have a look in the other directories? Once the files are fixed completely, what to do with them? Cheers, Harm _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
