We currently use `makeinfo --html' to build the online documentation.
Makeinfo is the normal way to create texinfo docs, but it lacks many
useful features. Most importantly, it can't create HTML pages split
into subsections; it only creates split output based on nodes.
texi2html has many more ab
Trevor Daniels wrote:
This is rather short at
present, and I would like to extend it. The question is, by
how much. I'd welcome your views on the suggestions below.
In particular, is this too long? Does this cover too
many/too few topics?
I've been thinking about the Tutorial vs. the rest of
(Michael: this discussion doesn't greatly influence your own formatting
work on Pitches -- whatever we decide here, those changes still need to
be made. Other than moving the sections.)
Ok, let's start the other half of real GDP work (two halves: formatting
and rewriting) by examining Pitches.
Anybody object to this change? I'm looking at Micro tones right now:
Bugs
There are no generally accepted standards for denoting three-quarter
flats, so LilyPond's symbol does not conform to any standard.
IMO this isn't really a _bug_, so I propose using the more general term
"kno
John, sorry to add another thing to your plate, but could you
investigate this?
When I do "make web" in Documentation/user/ the manual is great. Images
for all examples, everything working in Documentation/user/out-www/
When I then do "make web" in the topdir, the Learning Manual is missing
Mats Bengtsson wrote:
Related to what I just wrote in my email on "GDP - Learning Manuall
Songs section", I hereby volunteer to write an introduction to the
art of setting properties in LilyPond. The intention is just to provide
a first overview of the different options available.
Would this b
2007/9/26, Juergen Reuter <[EMAIL PROTECTED]>:
> I am just curious: Why not introducing a new class "Octaveless_pitch"
> or "Octave_Pitch" (i.e. pitch within an octave) that contains all of
> "Pitch" except for the octaves, and then making "Pitch" a subclass of
> "Octaveless_pitch" that just adds
I've updated GDP stuff at:
http://opihi.cs.uvic.ca/~gperciva/
There you can find rewritten/expanded instructions for GDP Formatters
and Rewriters (formally known as "trivial/easy/" and "medium" -- I
always felt bad about typing "trivial") and the most recent version of
the docs.
Helpers: p
Graham,
Related to what I just wrote in my email on "GDP - Learning Manuall
Songs section", I hereby volunteer to write an introduction to the
art of setting properties in LilyPond. The intention is just to provide
a first overview of the different options available.
You probably want to put i
Quoting Trevor Daniels <[EMAIL PROTECTED]>:
Most of the _concepts_ associated with lyrics need to be
introduced in the Learning Manual, as they are pretty well
all needed whenever lyrics need to be set. But only the
minimum number of technicalities should be covered; all
alternative methods and
On 9/26/07, Juergen Reuter <[EMAIL PROTECTED]> wrote:
> On Tue, 25 Sep 2007, Han-Wen Nienhuys wrote:
>
> > 2007/9/25, Rune Zedeler <[EMAIL PROTECTED]>:
> + int octave_;
> + int notename_;
> + Rational alteration_;
> >>>
> >>> Why don't you use a Pitch object for this combination?
As one of the GDP helpers I'm having a first look at the
Songs section which is to go into the new Learning Manual.
It will be based on the Tutorial Songs section (section 2.4)
in the present User Manual. This is rather short at
present, and I would like to extend it. The question is, by
how mu
On Tue, 25 Sep 2007, Han-Wen Nienhuys wrote:
2007/9/25, Rune Zedeler <[EMAIL PROTECTED]>:
+ int octave_;
+ int notename_;
+ Rational alteration_;
Why don't you use a Pitch object for this combination? You would get
Scale* for free.
Primarily because the two values octave_ and has_octave_
Quoting Michael Rasmussen <[EMAIL PROTECTED]>:
On page:
http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Dynamics#Dynamics
It gives a warning and example:
Because these marks are bound to notes, you must use spacer notes if multiple
marks are needed during one note
c\< c\! d
14 matches
Mail list logo
