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.
>
> J
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
>
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
>
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 .
Each B.6.x item in the navbar links only to the top of the
page, which is poin
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 .
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
I like the way the "Feta font" appendix page turned out, but
I just assumed each "@subsection foo" would get .
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 ther
