Han-Wen Nienhuys wrote:
2008/4/7, Graham Percival <[EMAIL PROTECTED]>:
Could we get *all* the internals treated with lilypond-book ?
Currently the docs generated from define-markup-commands.scm are
processed with lilypond-book, but the docs generated from other
files (like define-grob-properties.scm) go directly to .texi.
It would be nice to add lilypond examples for properties, and we
seem to have sufficient interest to begin this task.
I am not sure what the right technology would be. The quoting would
get very hairy, because most of the internals are generated from .scm
or .cc files.
I think we should look into a way of having a directory
Documentation/internal/grob-properties/PROPERTY-NAME.tely
One problem that's not solved using this strategy is that property names
like "style" are
used for different purposes on different grobs.
/Mats
make it so that the internals documentation automatically uses that
snippet for documenting said property. That would also provide a way
to do documentations.
--
=============================================
Mats Bengtsson
Signal Processing
School of Electrical Engineering
Royal Institute of Technology (KTH)
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=============================================
_______________________________________________
lilypond-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
