Graham has clearly pointed out a bug. It's easier to see in the
following example:
\documentclass[letterpaper]{article}
\usepackage{graphics}
\begin{document}
\begin{lilypond}
\score { \new StaffGroup \new Staff \relative c' {
\repeat unfold 8 {c4 c c c } \break
\repeat unfold 8 {d4 d d d } \break
\repeat unfold 8 {e4 e e e } \break
\repeat unfold 8 {f4 f f f } \break
\repeat unfold 8 {g4 g g g } \break
}}
\end{lilypond}
\end{document}
What seems to happen is that when the bar numbers get two digits,
then they start sticking out to the left of the staff so the left
edge of the bounding box of the .eps files changes.
The same problem appears much more pronounced if you set
\set Staff.instrument = "..."
which gives a first line that is totally misplaced with respect
to the others.
So, the current solution in lilypond-book for LaTeX with separate .eps
files for each score line definitely needs some polishing before it
gets useful.
/Mats
Graham Percival wrote:
On 7-Jul-05, at 3:48 AM, Mats Bengtsson wrote:
It's certainly possible to let lilypond-book automatically detect the
text height of the LaTeX document and set the vsize correspondingly.
However, it's not so much use since
1. It's only relevant when you explicitly have a \book{..} in
your .ly code (which it turn is mainly useful to be able to use
\pagebreak in the .ly code)
It also avoids some other problems -- the first few lines are shifted
to the left (relative to the other lines):
\documentclass[letterpaper]{article}
\usepackage{graphics}
\begin{document}
\begin{lilypond}
\score { \relative c' {
\repeat unfold 8 {c4 c c c } \break
\repeat unfold 8 {d4 d d d } \break
\repeat unfold 8 {e4 e e e } \break
\repeat unfold 8 {f4 f f f } \break
\repeat unfold 8 {g4 g g g } \break
}}
\end{lilypond}
\end{document}
Basically, lilypond-book without \book is only usable for single-line
examples.
That's ok; it's still useful for musicological documents. But as a
mechanism
for publishing music, you need to use \book{}.
2. If you already have some commands in your .ly code that affects the
page size, then they will override the setting done by lilypond-book,
since lilybook inserts the commands at the top of the code.
The only reason to have such commands is as a workaround for these
bugs. :)
Cheers,
- Graham
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
--
=============================================
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=============================================
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
