[EMAIL PROTECTED] writes:
> 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?
Normal sheet music is printed on something which is about 10% larger
than a4. I don't know what size precisely?
> 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.
fixed.
> > > It appears that 'make dvi' is aborting when bibtex gets errors, which
> > > it always does for the reference manual because there's no
> > > bibliography.
that would be weird, becuase of the || true command.
> > >
> > > 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?
maybe || true can be moved.
--
Han-Wen Nienhuys, [EMAIL PROTECTED] ** GNU LilyPond - The Music Typesetter
http://www.cs.uu.nl/people/hanwen/lilypond/index.html
