Making the lilypond documentation ready for 2.12

[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 the NEWS are not translated. Many, however, are simply mismatching node 
names, where the nodes were renamed in English but not in another language, or 
missing translations...

If you fix any issues, the results will be updated the next morning (Central 
European Time).

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 
Overview]"). What do you thinkg about those things?

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 showstoppers and MUST be fixed for 
the release?



Cheers,
Reinhold
- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, Vienna University of Technology, Austria
email: address@hidden, http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/
 * K Desktop Environment, http://www.kde.org, KOrganizer maintainer
 * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFJQUaLTqjEwhXvPN0RAgtFAJ9Gga6gF4f5kgz8+IIw8XwXH/EnRwCfTqsJ
lMbvj6fW8RvOUqMmXLmYwwU=
=3PRe
-----END PGP SIGNATURE-----