> > it should do because of the behavior of the other sizes. Why is it
> > that if I make the size smaller, the line width shrinks too? Is there
> > some good reason for this behavior? (I would expect changing the font
> > size to be independent from changing the margin size.)
>
> The linesize shouldn't be more than the paperwidth. Scaling the
> linesize sems like a good solution.
Well, not really. The normal way to choose the linesize is to pick it
depending on the paper width. The font size doesn't usually enter
into this at all. For example, if I use LaTeX and select a different
font size, the margins don't change.
The first computation for linewidth20 is the paper width minus a
multiple of the staff height. Maybe that is reasonable. But then it
gets scaled by staffheight/20 which means that the right margin for
11pt music is half the page.
> > Also, the default margins for 20pt look like they must be very tiny
> > for A4 paper. (They look pretty good on USA letter size which is 7mm
> > wider.)
>
> Yup. This is to reflect normal shete music (which is larger than A4)
Hmmm. It might then be desirable not to lie and have "a4.ly" loaded.
Is normal sheet music printed on a standard size of paper? Or is a
size used that predates the A, B, and C sizes?
> > What controls the text height? I can't figure this one out. The
> > "textheight" variable that is being set in the init files is never
> > used. (Grepping for it in the source turns up nothing.)
>
> Its controlled by the choice of TeX fonts.
How does the choice of TeX fonts affect the text height? I did
discover that ly2dvi looks at the textheight variable. I also noticed
that only ly2dvi32 seems able to print titles and authors on music
(and not ly2dvi). And even it can't print the title or author if it's
the first thing in the \header block. (This didn't used to be the
case.)
This header
\header{
foo = "nothing";
title = "The Gale";
composer = "Susan Conger";
}
becomes this TeX:
% Creator: GNU LilyPond 1.0.15.
% Automatically generated, at Tue Oct 13 08:26:46 1998
%
\def\LilyIdString{Lily was here, 1.0.15.}\def\mudelafoo{nothing}%
\def\mudelatitle{The Gale}%
\def\mudelacomposer{Susan Conger}%
I suspect the missing newline is responsible for ly2dvi32's inability
to find the first header item.
> > It appears that 'make dvi' is aborting when bibtex gets errors, which
> > it always does for the reference manual because there's no
> > bibliography.
> >
> > I guess bibtex returns false and so the rest of the && chain short
> > circuits. This means references don't get fixed and the table of
> > contents is screwed up. I'm not quite sure what is intended here, so
> > I didn't try to produce a fix. (Why the long chain with && instead of
> > just a list of commands?)
> because of the cd $(outdir)
>
>
> > $(outdir)/%.dvi: $(outdir)/%.latex
> > (cd $(outdir)&& \
> > latex \\nonstopmode \\input $(<F)&&\
> > (bibtex $(basename $(<F))&&\
> > latex \\nonstopmode \\input $(<F)&&\
> > latex \\nonstopmode \\input $(<F) ) || true)
> >
So would it be ok to use semicolons instead of &&'s?
