Fix issue 1011.

Fix issue 1011.

Make lilypond-book handle spaces before the closing '>'
bracket as allowed by the HTML standard.

Add regression tests for issue 1011.

Checks if lilypond-book works with spaces and newlines in front of
the closing '>' bracket.

Add regression tests for lilypond-book.

Test the operation of lilypond-book with HTML files.

[Graham Percival (old account), 2010-02-13 20:40:22]

If John or anybody else wants to set in with comments about the build system,
that would be nice.  I'm really uncertain about having an html-specific regtest
dir; I'd much rather seen a lilypond-book dir that tested all output formats.

http://codereview.appspot.com/206092/diff/1/3
File input/regression/GNUmakefile (right):

http://codereview.appspot.com/206092/diff/1/3#newcode9
input/regression/GNUmakefile:9: SUBDIRS=musicxml abc2ly lilypondbook_html
I guess this is as good a place as any: why is this dir only checking
lilypondbook_html ?  If we're going to have any regtests specifically for
lilypond-book, surely it would be better to test all output formats?

http://codereview.appspot.com/206092/diff/1/4
File input/regression/lilypondbook_html/GNUmakefile (right):

http://codereview.appspot.com/206092/diff/1/4#newcode9
input/regression/lilypondbook_html/GNUmakefile:9: 
I don't understand this part -- why not always set LILYBOOK_HTML_FILES = ""   ?

http://codereview.appspot.com/206092/diff/1/4#newcode12
input/regression/lilypondbook_html/GNUmakefile:12: 
I'd rather not have a TMP variable; could you give it a better name?

http://codereview.appspot.com/206092/diff/1/16
File scripts/lilypond-book.py (right):

http://codereview.appspot.com/206092/diff/1/16#newcode396
scripts/lilypond-book.py:396: 
The changes to this file have been accepted and pushed, thanks!