Graham Percival escreveu:
>
> How picky do you want to be about this? Examples with very little below
> the staff will cut off the treble clef. See
>
> http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Falls-and-doits
>
> for example. (missing 2 or 3 pixels at the bottom of the clef)
Han-Wen Nienhuys wrote:
Werner LEMBERG escreveu:
In section 5.1, `Moving objects', there are two examples using
`extra-offset'. The second one has the `ritenuto' cropped partially.
I wonder whether it is a generic problem (this is, lilypond can't
compute the bounding box correctly if extra-off
Werner LEMBERG escreveu:
>
> In case nobody objects, I'll file a bug report.
>
See #11.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code for Music Notation
http://www.lilypond-design.com
_
Werner LEMBERG escreveu:
> In section 5.1, `Moving objects', there are two examples using
> `extra-offset'. The second one has the `ritenuto' cropped partially.
>
> I wonder whether it is a generic problem (this is, lilypond can't
> compute the bounding box correctly if extra-offset is used) or w
Werner LEMBERG wrote:
Due to the new collision avoidance algorithm, section 5.1, `Moving
objects', is out of date.
Similarly, in section 4.2, `Saving typing with identifiers and
functions', the music function `padText' should be replaced with
something more meaningful.
Yes and no -- some colli
Hi everyone!
In the following fragment of music, Lilypond prints a double hyphen on the last
note of the slur.
\version "2.10.0"
MusicaUno = \relative c'' {
e8. e16 e4 d8. d16 d8 d
d4( c) b b
}
Parole = \lyricmode {
Ky -- ri -- e, Ky -- ri -- e e --
lei -- son, e
}
Han-Wen Nienhuys wrote:
Maximilian Albert escreveu:
. So it seems that the use of "Accidental #'style" is deprecated and one
should set the alteration-alist directly. (But changing the style
property still works in v2.11.13, even if I don't know why, given that I
couldn't find the code handli
Han-Wen,
thank you for your very fast and helpful answers!
A few more comments/questions/suggestions.
>> \once \override NoteHead #'style = #'harmonic
>> \once \override NoteHead #'glyph-name = #'"2harmonic"
>
> if you set glyph-name, style is no longer necessary.
That's what I thought bef
Due to the new collision avoidance algorithm, section 5.1, `Moving
objects', is out of date.
Similarly, in section 4.2, `Saving typing with identifiers and
functions', the music function `padText' should be replaced with
something more meaningful.
Werner
__
In section 5.1, `Moving objects', there are two examples using
`extra-offset'. The second one has the `ritenuto' cropped partially.
I wonder whether it is a generic problem (this is, lilypond can't
compute the bounding box correctly if extra-offset is used) or whether
it is a bug. In the former
Have a look at section 2.2.6 in the tutorial, subsection `Tuplets'.
The third beat in the displayed bar is entered as
\times 2/3 { f,8 g16 a g a }
and displayed as
x x x x x
| | | | |
|-- -
---
3
I strongly disagree with th
Maximilian Albert escreveu:
> Orm Finnendahl schrieb:
>
>> thanks for pointing that out. That's exactly along the lines I was
>> thinking. Is anybody capable of doing the scheme/lilypond code? I
>> don't know Metafont yet but I think I could handle that part and throw
>> in the glyphs (they are c
12 matches
Mail list logo
