On Wed, 14 May 2008 08:50:12 +0100
"Trevor Daniels" <[EMAIL PROTECTED]> wrote:
> Graham Percival wrote Wednesday, May 14, 2008 6:40 AM
>
> > Another solution is just to include @w{} in the list of commands
> > for doc helpers, and encourage people to write @[EMAIL PROTECTED]
> > lilypond command with arguments}}.
>
> I'd go for this solution. We have to use @w{} occasionally in
ok, done.
> other circumstances anyway. Not sure it's worth doing this every
> time though - it's bad enough in some text to have to place @code{}
> everywhere.
Well, if you write your text properly, that isn't an issue. :P
(yeah, the LM is different...)
> Might be better to do this only if the command
> would otherwise split -
Of course.
> ie leave it for one of the last tiding up actions
GDP: the lunar documantation cleanup!
> after all the text is in place (if we ever reach that point :)
Hey, we reached that point for Pitches months ago. Anyway, this
is trivial to fix; I've updated my sections: introduction.itely,
tutorial.itely, pitches.itely, and editorial.itely. Since
everything else is still under active GDP work, I haven't bothered
with them.
Cheers,
- Graham
_______________________________________________
lilypond-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
