[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 1000 in lilypond: communicate with upstream texi2html project

From: lilypond
Subject: Re: Issue 1000 in lilypond: communicate with upstream texi2html project
Date: Sat, 15 Oct 2011 00:48:31 +0000

Comment #16 on issue 1000 by address@hidden: communicate with upstream texi2html project

First answer: I think it's just aesthetics. Most webpages use lower-case letters, so IIRC I asked that the people working on the init file produces lower-case html files. It's been a long time since this work was done so I'm not certain if I actually asked them or not, but it's the kind of thing that I would do. I would like to keep the lower-case html names, though. I know it's easy to do in code. :)

Second answer: I'm not certain about the translation issues, but I can clarify/emphasize that (in IIRC 10 out of our 11 manuals) we create html names based on numbered/unnumbered status. i.e.
  @node foo
  @subsubsection foo
gets a new html page, whereas
  @node bar
  @unnumberedsubsubsec bar
does *not* get a new html page. And yes, we regularly use @unnumberedsubsubsec; that's the default "level" in our notation reference. In most manual we keep unnumbered for the subsubsec level, but in 1 or 2 manuals we use unnumbered at the subsec level and have new pages on the @section level. The point of the "numbered/unnumbered" distinction is to avoid having to specify different --section= commands in the build system; instead, the splitting is done in the general numbered/unnumbered case. This produces a more complicated init file, of course. :)

I think this could be a useful feature for other projects, so I definitely hope it gets upstream.

Third answer: I'm not totally positive, but I believe that @translationof is only used in our internal "housekeeping" translation scripts -- they check that there's an appropriate @translationof for each @node in the main docs.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]