[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Lilypond-auto] Issue 2967 in lilypond: @unnumberedsubsubsec should alwa
From: |
lilypond |
Subject: |
[Lilypond-auto] Issue 2967 in lilypond: @unnumberedsubsubsec should always have an accompanying @node |
Date: |
Mon, 19 Nov 2012 08:16:35 +0000 |
Status: Accepted
Owner: ----
Labels: Type-Documentation
New issue 2967 by address@hidden: @unnumberedsubsubsec should always
have an accompanying @node
http://code.google.com/p/lilypond/issues/detail?id=2967
Sections in the documentation introduced with
@unnumberedsubsubsec should always have an
accompanying @node and feature in an earlier
@menu list. At least one does not, see
@unnumberedsubsubsec Instrument names in
NR 3.5.1. All the docs should be trawled to
check this to ensure the links in the html
left panel and index entries work correctly.
If the name is already used in a node in the
same manual it would need to be changed. This
is the case in the example quoted above, as
"Instrument names" is already a node in NR 3.5.1.
Trevor
- [Lilypond-auto] Issue 2967 in lilypond: @unnumberedsubsubsec should always have an accompanying @node,
lilypond <=
- Re: [Lilypond-auto] Issue 2967 in lilypond: @unnumberedsubsubsec should always have an accompanying @node, lilypond, 2012/11/19
- Re: [Lilypond-auto] Issue 2967 in lilypond: @unnumberedsubsubsec should always have an accompanying @node, lilypond, 2012/11/21
- Re: [Lilypond-auto] Issue 2967 in lilypond: @unnumberedsubsubsec should always have an accompanying @node, lilypond, 2012/11/22
- Re: [Lilypond-auto] Issue 2967 in lilypond: @unnumberedsubsubsec should always have an accompanying @node, lilypond, 2012/11/25
- Re: [Lilypond-auto] Issue 2967 in lilypond: @unnumberedsubsubsec should always have an accompanying @node, lilypond, 2012/11/25
- Re: [Lilypond-auto] Issue 2967 in lilypond: @unnumberedsubsubsec should always have an accompanying @node, lilypond, 2012/11/29
- Re: [Lilypond-auto] Issue 2967 in lilypond: @unnumberedsubsubsec should always have an accompanying @node, lilypond, 2012/11/30