[EMAIL PROTECTED] writes:
> How is the documentation in the lilypond tarball supposed to be read?
> There are a bunch of texi files, but I haven't found any make targets
> that will transform them to anything more useful. A "make dvi"
> created a lot of strangely-named dvi file before failing with an
> error. I tried to manually run makeinfo to at least get an info file,
Can we have a bugreport?
> and at least it didn't fail, but the internal links were not in a very
> good state.
I know. Patch appreciated.
>
> And then there's mention of DOC++ in a README somewhere, but I haven't
> tried that yet.
>
> If someone can give me a hint on what the recommended way of
> processing the documentation is, I can at least try it and see if it
> works for me. And why isn't it done automatically by configure/make?
try
make htmldoc
or
make -C Documentation/user/ dvi
It's not done automatically because it requires a working LilyPond
executable.
--
Han-Wen Nienhuys, [EMAIL PROTECTED] ** GNU LilyPond - The Music Typesetter
http://www.cs.uu.nl/people/hanwen/lilypond/index.html
