Re: @subsection foo should get name=foo
Graham Percival wrote:
Yes. You can add a menu to the Feta font
section and introduce each subsection with
@node
@subsection ...
As we're in an appendix maybe this should be
@node ...
@appendixsubsec ... ?
I believe it should be
@node
@unnumberedsubsec
You can use them inside an @appendicsec, and since the html pages
are split based on numbers, we want an @unnumbered... there.
Just want to make sure I have this right. Is this outline correct?
Thanks.
- Mark
@node The Feta font
@appendixsec The Feta font
@cindex Feta font
@cindex Font, Feta
The following symbols are available in the Emmentaler font and may be
accessed directly using text markup such as @code{g^\markup @{
\musicglyph #scripts.segno @}}, see @ref{Formatting text}.
@menu
* Clefs::
* Time Signatures::
etc...
@end menu
@node Clefs
@unnumberedsubsec Clefs
@lilypond[quote]
\include font-table.ly
\markuplines \override-lines #'(word-space . 4)
\doc-chars #clefs
@end lilypond
@node Time Signatures
@unnumberedsubsec Time Signatures
@lilypond[quote]
\include font-table.ly
\markuplines \override-lines #'(word-space . 4)
\doc-chars #timesig
@end lilypond
etc...
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: @subsection foo should get name=foo
On Wed, Jul 15, 2009 at 01:44:03PM -0700, Mark Polesky wrote: Graham Percival wrote: I believe it should be @node @unnumberedsubsec You can use them inside an @appendicsec, and since the html pages are split based on numbers, we want an @unnumbered... there. Just want to make sure I have this right. Is this outline correct? Yep, looks good. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: @subsection foo should get name=foo
Mark Polesky wrote Tuesday, July 14, 2009 6:54 AM I like the way the Feta font appendix page turned out, but I just assumed each @subsection foo would get name=foo. Each B.6.x item in the navbar links only to the top of the page, which is pointless IMO: B.6 The Feta font * B.6.1 Clefs * B.6.2 Time Signatures * B.6.3 Numbers Is there an easy way to improve that? Yes. You can add a menu to the Feta font section and introduce each subsection with @node @subsection ... But it's easy to make mistakes in doing this. Are you able to check texinfo syntax and refs? If not, send any patch to me (or someone who can compile the docs for checking) before pushing. A broken doc breaks all LP compiles! Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: @subsection foo should get name=foo
Trevor Daniels wrote Tuesday, July 14, 2009 8:57 AM Mark Polesky wrote Tuesday, July 14, 2009 6:54 AM I like the way the Feta font appendix page turned out, but I just assumed each @subsection foo would get name=foo. Each B.6.x item in the navbar links only to the top of the page, which is pointless IMO: B.6 The Feta font * B.6.1 Clefs * B.6.2 Time Signatures * B.6.3 Numbers Is there an easy way to improve that? Yes. You can add a menu to the Feta font section and introduce each subsection with @node @subsection ... As we're in an appendix maybe this should be @node ... @appendixsubsec ... ? Graham ? But it's easy to make mistakes in doing this. Are you able to check texinfo syntax and refs? If not, send any patch to me (or someone who can compile the docs for checking) before pushing. A broken doc breaks all LP compiles! Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: @subsection foo should get name=foo
On Tue, Jul 14, 2009 at 10:46:58AM +0100, Trevor Daniels wrote: Trevor Daniels wrote Tuesday, July 14, 2009 8:57 AM Yes. You can add a menu to the Feta font section and introduce each subsection with @node @subsection ... As we're in an appendix maybe this should be @node ... @appendixsubsec ... ? I believe it should be @node @unnumberedsubsec You can use them inside an @appendicsec, and since the html pages are split based on numbers, we want an @unnumbered... there. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
