On Fri, 2003-09-26 at 02:23, Olivier Cloirec wrote:
Is a simple .ly file works with a PostScript output?
NO, it doesn't. If I run
ly2dvi -P file.ly
and then view the file with
ghostview file.ps
it gives the same terrible result.
But... if I just run ly2dvi -p file.ly, a ps file is
On Wednesday 24 September 2003 08:30 pm, Graham Percival wrote:
On Thu, 25 Sep 2003 00:59:11 +0200
ario [EMAIL PROTECTED] wrote:
So I wanted to convert a file, which has the statement
\version 1.6.10 in it, using
-snip-
\version 1.7.28
How come???
There were no syntax changes
I'm not sure, but -p is used for generate PDF files (it uses Type1
fonts) whereas -P generates PostScript output with bitmap fonts.
Look at your /usr/(local/)share/lilypond/1.8.0/fonts if there are afm
and tfm fonts...
Olivier
arie-lily wrote:
On Fri, 2003-09-26 at 02:23, Olivier Cloirec
Hi,
[I got the strange wide spacing of multi-measure rests as well as Paul!
Until I upgrade, I will avoid using Multi-Measure rest markup]
I have noticed that on 1.8.2 a single bar rest with r1 (4/4 time) results in
the rest not being centred in the bar.
Is this by design or is it a bug?
It does
Ralph Little wrote:
Hi,
[I got the strange wide spacing of multi-measure rests as well as Paul!
Until I upgrade, I will avoid using Multi-Measure rest markup]
Now, you can use it, can't you?
I have noticed that on 1.8.2 a single bar rest with r1 (4/4 time) results in
the rest not being centred
Thanks for the note about R1/r1. You are quite right.
A quick replace s/r1/R1/g should fix that :D
Regarding the Multi-measure rest issue, I thought that a change was added to
CVS.
I've just upgraded from 1.6.4 to 1.8.2 and I'm just getting over the shock!
Maybe I'll have a go shortly, but it
Ralph Little wrote:
Thanks for the note about R1/r1. You are quite right.
A quick replace s/r1/R1/g should fix that :D
Regarding the Multi-measure rest issue, I thought that a change was added to
CVS.
I've just upgraded from 1.6.4 to 1.8.2 and I'm just getting over the shock!
Maybe I'll have a go
Hi,
Quite awhile back, Lilypond had issues with gcc 3.x, in which I could
never get it to compile.
I am installing a new machine, and debating on Slackware 8.1 (gcc 2.95)
or 9 (gcc 3.2.x). Which would be better, to limit the problems I might
have?
Thanks,
Bryan
LOG file is attached as requested.
I ran the regtool command you suggested. Now, if I tell windows open the
test.ly file with bash, it almost works. It invokes lily-wins, but
produces an error message when it tries to execute the following command:
cygpath -aw /cygdrive/c/Documents and
in the following:
\score {
\notes \relative c' {
f g c~f g c
}
\paper { raggedright = ##t}
}
it seems clear to me that the tie between g's should go up, to avoid
colliding with the tie between f's. unfortunately, that does not follow
the rule of curving away from staff center.
i have not been
Hi,
Why I get:
/tmp/repeat-volta.ly:14:39: warning: beam has less than two visible stems:
with the following code?
\score {
\notes \context Voice \relative c' {
\repeat tremolo 16 {e32\p ( c32)}
}
}
Pedro
___
Lilypond-user mailing list
How about having better support for chord tremolos when whole notes
are involved? In the example bellow, not only the beams in the first
measure should be placed bellow the noteheads, but they should be also
more inclined, like in the second measure. Any changes to see that in
2.1? :-)
\score {
I am unable to transpose chord names correctly.
If I enter chords as e1:m7 f1:maj7 etc then they print correctly on the
score but do not transpose with the rest of the score. My notes and key
signature do transpose correctly.
If I enter e-minor7 chord as e g b d then it transposes but
Hello!
I'm trying to compile lilypond-2.0.0 but unsuccessfully :(((.
I'm using gcc-3.3.1.
It doesn't compile (even with the patch) with flex-2.5.4a.
It compiles with flex-2.5.31 but seems buggy (it segfaults when parsing
starts :( ).
I hope it will compile with flex-2.5.27...
I don't know if it
On Friday 26 September 2003 04:57 pm, you wrote:
in the following:
\score {
\notes \relative c' {
f g c~f g c
}
\paper { raggedright = ##t}
}
it seems clear to me that the tie between g's should go up, to avoid
colliding with the tie between f's. unfortunately, that does not
follow
15 matches
Mail list logo
