2013/4/14 Janek Warchoł <janek.lilyp...@gmail.com> > 2013/4/14 Federico Bruni <fedel...@gmail.com>: > > As you can see in this example: > > http://lilypond.org/ly-examples/tab-example.png > > > > the bottom part of the bracket has been cut off because of -dpreview. > > Can you change -dpreview so that brackets are taken into account? > > I think this isn't as simple as it looks, and it affects many other grobs. > As far as i know, the problem is that everything that sticks outside > grob's extent is ignored by LilyPond. For example, when you override > extent to be empty as in here > > { b4 b b } > \addlyrics { > \override LyricText #'X-extent = ##f > oeirg ergoi fooo > } > > lyrics collide - because Lily ignores everythign outside the (empty in > this case) extent when calculating collisions. > Unfortunately, this cannot be solved by simply including everything in > extents. As far as i can see, the solution is to define two kinds of > extents (see here > http://lists.gnu.org/archive/html/lilypond-devel/2012-06/msg00230.html). > http://code.google.com/p/lilypond/issues/detail?id=3239 is a step in > that direction, but it's progressing slowly; more people discussing > code are needed to really move this forward. > However, currently our efforts should concentrate on preparing a > stable, and after that we could return to this thing. > > best, > Janek >
thanks for your comment, Janek I've found a similar report and added a link to this thread: http://lists.gnu.org/archive/html/bug-lilypond/2013-04/msg00091.html _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
