On Sat, 2002-10-26 at 02:45, Paul Scott wrote:
Graham Percival wrote:
Actually your last two solutions sound like they have possibilities.
Possibly something from this could be added to the docs when you have
time. When I get clearer on this I'll post my solution. Of course this
also
How do I make ly2dvi NOT to print the Lily was here X.X.X mark?
\header{
tagline =
}
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
How do I make ly2dvi NOT to print the Lily was here X.X.X mark?
Thanks for your help,
Antonio
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
That has possibilities and might solve another problem. I'm going to
post a question or two about vertical spacing when I get a chance. My
tempo marking is too close to the notes right now.
The padding property is your friend, for example:
\property Voice.TextScript \override #'padding =
\context Staff = soprano
\global
\clef treble
\property Staff.instrument = Soprano
\property Staff.midiInstrument = flute
\sopranoNotes
\notes { R2.*7
\context Lyrics =
Mats,
Removing the feta* files in my local directory made the dvips and ly2dvi
generated files look the same. Unfortunately it didn't fix the squashed
font problem.
Sorry about the 16 versus 20 font size oversight. I'm usnig denemo to
enter the music which defaults to 16 so I have to change it
[EMAIL PROTECTED] writes:
I hope you saw the other postings on this problem which I think answer
your question.
Any ideas?
Still the only thing I can think of is some kind of resolution
mismatch. (are you sure you removed everything, i.e. what does locate
feta say?) Second, if you use ly2dvi
