Re: *-headword.ly files look weird

[Graham Percival]

On Mon, Apr 26, 2010 at 10:37:18PM -0700, Mark Polesky wrote:
> Why are so many of the Documentation/snippets/new/*-headword.ly
> files coded in absolute mode with one note per line?

I don't know; what does the git history say?

You do realize that the exact input for the headwords are almost
the least visible portion of the documentation, right?  The only
way to see the input code is by clicking on the image in html;
there's no way (at present) for info and html people to see it.

I really think it's more effective to work on other aspects of
this problem.  If you're more concerned about the input formatting
than the content of the docs or the bugs in the program, that's
perfectly valid -- but the best way to solve this is by
writing/finding/adapting a python script that automatically
indents lilypond code (some attempts exist already), and then
running that on our docs with lilypond-book.

For the first pass at this, we don't even need to agree on the
indentation -- just get the framework together.  Then all we
debate is how the indentation should look, adjust the script, and
*boof*, the computer automatically updates all 5000 (made-up
number) pieces of lilypond input in snippets, doc examples, etc
etc.

ETA: 3 hours if you know python and indentation (the only tricky
part is detecting scheme-code vs. lilypond-code).  5 hours if you
know python.  20 hours if you know neither, but trust me, the
python you'll learn on this project will be very useful for tons
of other lilypond projects.


Valentin, could you add this to the relevant tracker issue?

Cheers,
- Graham