lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Broken refs


From: Trevor Daniels
Subject: Re: Broken refs
Date: Thu, 6 Aug 2009 14:48:10 +0100


John Mandereau wrote Thursday, August 06, 2009 12:06 PM

Le jeudi 06 ao=C3=BBt 2009 =C3=A0 11:35 +0100, Trevor Daniels a =C3=A9crit =
:

Have you tried building docs inside the source tree?

No; I'm on Windows Vista, so building isn't an option, is it?

I generated my own scripts so I can have my texinfo syntax
and crossref links machine-checked.  Then I feel happy
about editing docs and pushing doc commits.

It also means I can check individual .itely files rather than
building the whole of the documentation.  This takes only
1-2 minutes, which is very efficient when honing doc edits.

Checking cross-references...

./notation/notation-appendices.itely: 939: `Fonts': external ruser x-ref
should be internal

./notation/notation-appendices.itely: 940: `Text encoding': external
ruser x-ref should be internal

./notation/notation-appendices.itely: 981: `Layout interfaces': external
ruser x-ref should be internal
Done: 7137 x-refs found, 3 bad x-refs found, fixed 0.

Aah; my checker doesn't check that.  Good catch.  I'll add that
refinement, I think it should be easy (if that term can apply to
anything to do with LilyPond :)

These 3 nits should be fixed automatically by fix-xrefs BTW.

Good.  In that case I'll leave them for someone else.  I'll test out
my change before I pull again to be sure it picks these up.

Best,
John

Trevor







reply via email to

[Prev in Thread] Current Thread [Next in Thread]