For the sake of completeness, I set the default version of ghostscript
to gs-gpl, ran the file through lilypond again, then viewed the file
with all of the pdf viewers that are on my system (which I believe to be
all of the pdf viewers available through the standard debian repositories).
Acrob
Graham Percival wrote:
On 16-Aug-05, at 8:03 PM, D Josiah Boothby wrote:
Using the 2.6.0 autopackage on Debian sarge/sid, Evince (v. 0.3.0)
doesn't display the 3's in the time signatures.
Please file a bug report with evince, then. (?)
Looking more carefully
I don't kn
Using the 2.6.0 autopackage on Debian sarge/sid, Evince (v. 0.3.0)
doesn't display the 3's in the time signatures.
An example .ly file:
\version "2.6.0"
\score {
\relative c' {
\time 3/4 d2.
\time 7/8 e2..
\time 2/4 f2
\time 3/8 es4.
\time 5/8 ges4 f4.
\time 4/8 e2
\time
oking for, is probably
\override Stem #'beamed-lengths = #'(20)
The value of beamed-length is a list, so you could also do something like
#'(5 6 7)
to get different stem lengths for different beam multiplicities.
Erik
On Wednesday 19 January 2005 07.22, D Josiah Boothby wrote:
Lilypond shall handle this automatically. Additionally, the clef
changes in a horn part are normally different from the clef changes in
the full score. See the attached image.
...
But in guitar scores you always use treble clef, right? Here another
example: Take the pocket score of `Ein deutsche
"Old notation" bass clef has a certain logical place in a context (such as Strauss's Don
Quixote) in which a low horn is traversing a range which makes the use of treble or bass clefs awkward.
Rather than learn three clefs (tenor clef would be a pretty close replacement for old notation bass clef
