Jay Anderson wrote:
Ok, here's what I've come up with to show the bug a little better:
I think this one is a bit more condensed, and avoids the
\layout{line-width} compression. I've added it to the bug report.
\version "2.9.21"
\score
{
<<
\new Staff
{
\relative c'
{
Ok, here's what I've come up with to show the bug a little better:
-
\version "2.9.21"
\score
{
<<
\new Staff
{
\relative c'
{
c4 c c c |
c4 c8 c c4 c8 c |
c8 c4 c8 c c4 c8 |
c8 c c c c c c c |
\times 2/3 {c4 c c} c4 c |
c4 \times 2/
> By 'better' I meant that it shows the problem more clearly. I haven't
> tweaked much at all yet. This is default Lilypond and it doesn't
> complain one bit about it getting too dense:
The new image definitely classifies the collision as a bug. It would
be great if you could extract a minimal e
By 'better' I meant that it shows the problem more clearly. I haven't
tweaked much at all yet. This is default Lilypond and it doesn't
complain one bit about it getting too dense:
-
Processing `E:/cygwin/home/Jay/open-scores/DukasVillanelle/trunk/Piano.ly'
Parsing...
Interpreting music... [8]
> Yeah, I agree that there wasn't a total collision in the examples I
> provided. Perhaps the attached is a bit better.
It's not really better. The music is typeset far too densely. I'm
quite sure that lilypond complains about it. What about removing,
say, the first bar so that the system is d
Yeah, I agree that there wasn't a total collision in the examples I
provided. Perhaps the attached is a bit better. This is what is
created when I generate the whole file and not just a little snippet.
I tried to boil the example down as much as possible. There is
definitely a problem. I can point
Werner LEMBERG wrote:
The bass clef in the following example collides with the rest in
the following example. It looks worse in context than it does
here, but normally lilypond does a good job of spacing the clef
changes. Is there any tweak I can do to fix this or are there
deeper problems? Than
> > The bass clef in the following example collides with the rest in
> > the following example. It looks worse in context than it does
> > here, but normally lilypond does a good job of spacing the clef
> > changes. Is there any tweak I can do to fix this or are there
> > deeper problems? Thanks
Jay Anderson wrote:
The bass clef in the following example collides with the rest in the
following example. It looks worse in context than it does here, but
normally lilypond does a good job of spacing the clef changes. Is
there any tweak I can do to fix this or are there deeper problems?
Thanks
The bass clef in the following example collides with the rest in the
following example. It looks worse in context than it does here, but
normally lilypond does a good job of spacing the clef changes. Is
there any tweak I can do to fix this or are there deeper problems?
Thanks for the help.
-
10 matches
Mail list logo
