Re: Making the lilypond documentation ready for 2.12

2008-12-11 Thread Patrick McCarty
On Thu, Dec 11, 2008 at 8:57 AM, Reinhold Kainhofer wrote: > > 2) About the current CSS design: Patrick sent a patch a while ago, which was > never applied. Plus, there are the suggestions to rename the "<<< Back to > Documentation index" to something more meaningfull (e.g. "[To Documentation > Ov

Re: Making the lilypond documentation ready for 2.12

2008-12-11 Thread Laura Conrad
> "Graham" == Graham Percival <[EMAIL PROTECTED]> writes: Graham> 2.11.65 is so much better than 2.10.33 that it's ridiculous. For Graham> the past year we've been telling everybody to use/read 2.11.x Graham> instead of 2.10, but that only reaches people on -user. It's past

Re: Making the lilypond documentation ready for 2.12

2008-12-11 Thread Graham Percival
On Thu, Dec 11, 2008 at 05:57:46PM +0100, Reinhold Kainhofer wrote: > 3) How about other issues with the new docs? In particular, my list of issues > has not been updated for quite a while: > http://wiki.kainhofer.com/lilypond/texi2html_issues > Are these problems still there, which are showstoppe

Making the lilypond documentation ready for 2.12

2008-12-11 Thread Reinhold Kainhofer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 1) Each morning I build the current docs from git master on my server and also run a linkchecker (linklint) on the result: http://kainhofer.com/~lilypond/linkdoc/ As you can see, there are lots of broken links, some due to the fact that the IR or th