[EMAIL PROTECTED] writes:
etc". The second thing is the expansion of the unified index. The index is a great way of finding what section something is is, but it's not big enough. For example, the "<<" operator isn't there and neither is "#". It does have a link to the Scheme tutorial, but that's only useful if I know that "#" is related to Scheme. Some other things that are missing: "(", "\(", "-x", "^x", "_x", "\markup", "\new", "\context" - (this is present, but it has a link to Piano Staves, for some reason).
This is a task that doesn't require all that much knowledge of how Lilypond works. Someone just needs to plow through Documentation/user/*.itely (in the source archive) and add lots of relevant
@cindex
entries.
Would you be willing to take up that task?
Aren't there tools for auto-indexing directory trees for search engines?
-- Jim Sabatke Hire Me!! - See my resume at http://my.execpc.com/~jsabatke
Do not meddle in the affairs of Dragons, for you are crunchy and good with ketchup.
_______________________________________________ lilypond-user mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-user
