In the doc source, we add commands like
@cindex beaming
@funindex []
There is no automatic testing for this, but I'm certain that our
doc build correctly links the index entry to the place where the
command was placed in the doc source.
As far as I know, there is nobody currently working on
Graham,
My area of expertise is editing and one of the things that often make
or break a set of docs are the indexes for each manual. Do we have any
kind of regression scheme (sorry about the pun) to check for problems
peculiar to an index? For instance does each citation in the index
lead to a pa
No, that's fine -- we already have somebody to handle the
git+compile+doc policy stuff. So far I have no indication that
he's overwhelmed with work.
If you're up for writing a few lilypond examples (say, creating an
example of \bendAfter using a non-integer argument), *that* could
be useful... bu
On Mon, Mar 22, 2010 at 04:54:52PM -0400, Kieren MacMillan wrote:
> Hi Graham,
>
> > and think you might be able to help with category 3
>
> Check...
ok. Take a look at
http://code.google.com/p/lilypond/issues/detail?id=989
in particular, see if you can suggest an example for the NR to
take ca
2010/3/22 Graham Percival :
> If you belong to category 1, and think you might be able to help
> with category 3, please contact category 2 (CC'd on this email) or
> me.
Nobody is cc'd on this email AFAICT
I can apply patches and check compilation.
--
Francisco Vila. Badajoz (Spain)
www.paconet.
Hi Graham,
> 1. we have a number of users who know a lot about lilypond, but
> are not familiar with git + compiling + our doc policies.
Hey... that's me!!!
Well, I know some about it -- but it doesn't seem to work on my machine very
well, so what's the diff?? [pun intended ;)]
> 2. we have a
I should be able to handle some git committing / compile checking, and stuff
like that if others can do the worst of the typing.
Jon
On Mon, Mar 22, 2010 at 3:36 PM, Graham Percival
wrote:
> Here's the current situation with the documentation.
>
> 1. we have a number of users who know a lot abou
Here's the current situation with the documentation.
1. we have a number of users who know a lot about lilypond, but
are not familiar with git + compiling + our doc policies.
2. we have a doc editor on Windows who knows about
git+compiling+doc policies, but knows relatively little
about l
