On Tue, 1 Apr 2008 02:33:49 +0200 Reinhold Kainhofer <[EMAIL PROTECTED]> wrote:
> Actually, I'm already working in the dev/texi2html branch in git... > Currently, I've put the lilypond.css file into Documentation and > the .init file into the top dir (should probably go into buildscripts) > > All the docs are automatically built with texi2html instead of > makeinfo in that branch, and so far I haven't run into any further > problems... > > The English docs in Documentation/user build just fine, the language > docs also build to a large extent, but there I'm running into some > small issues (mainly that I need to change the way the file names are > generates -- especially for nodes with special characters in them -- > to be consistent with makeinfo). And some post-processing scripts > probably need to be adjusted (because texi2html does some things > differently from makeinfo). > > E.g. makeinfo produces <body>, while texi2html produces <body > lang=".." COLOR=... ...>. Unfortunately, one build script explicitly > extracts the contents as everything between <body> and </body>, which > no longer works. I'm expecting some furhter similar problems... > > Also, ./buildscripts/www_post.py fails, but I haven't yet looked into > that. Sounds good. I'm pretty certain that John was the last person to work on www_post.py, and he's much more familiar with the doc build system than I am, so I'll let you work it out with him. :) Cheers, - Graham _______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
