On Mon, 12 May 2008 18:10:48 -0600 "Carl D. Sorensen" <[EMAIL PROTECTED]> wrote:
> Graham, > > I'm sorry to be obtuse on this, but I want to do the job right. So I > figure if I spend a bit of your time in the beginning, I'll save some > at the end... You're quite right to do so! Of course, no matter how long you spend studying policy.txt, you'll probably miss one or two items when you start sending me updates. That's expected and quite acceptable... I don't expect helpers to be sending perfect doc submissions until at least half a dozen .itely files have been exchanged. How much time you spend reading policy.txt, and how much time we spend discussing specific doc submissions, is a tradeoff that's hard to evaluate. :) > policy.txt has the following: > > ---- END COPIED TEXT ---- > > I have a couple of questions here: > > 1) You show @snippets as coming between @predefined and @seealso. > You also show @rlsr as a subitem under @seealso. What is the > difference between @snippets and @rlsr? @snippets is a "section heading" (except I try to avoid "section" since that has a technical definition in the docs). @rlsr creates a link. The best explanation I can give here is to look at Key Signatures in the newly-uploaded pitches.itely. It shows all these things in action. > 2) Am I correct that we should put @predefined, @seealso, and > @knownissues at the end of each subsubsection? Yes. > 3) Am I correct that the current preferred usage is to replace > subsubsection with unnumberedsubsubsec so that a subsection will be a > complete HTML page, rather than a subsubsection? Yes, although that's a small detail that I can easily do later on in the process. It also won't have any effect on the current GDP output; it only affects the texi2html output, which is still under development. Cheers, - Graham _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
