Hi,
On Thu, Dec 05, 2002, Ray Peck wrote:
Cool: I got working PDF output.
Now: I grepped /usr/doc/lilypond-1.6.5-1/ for sodipodi and
SVG and found nothing. How do I generate SVG output so
that I can try it in OO, and where is the code that generates
it, so I know what to go hack to fix
Hello,
I'm trying got install Lilypond from RPM on a Mandrake 8.1, but I can't get
out of the dependencies web. Could anyone give me a complete working
installation sequence for the various RPM that need to be installed on
Mandrake 8.1?
Thanks a lot
Silvio
Hello all.
I need an accidental macro which isn't in the standard ones but I'm not
able to hack one by myself (because I'm a lilypond newbie and a
non-programmer). Perhaps someone of you has made a suitable macro and
could send it to me.
What I need: There should be accidentials before every
When I state a key for a piece in Lilypond I expect it to follow
common rules for writing music, i.e. not to put natural signs on every
note which should be altered in that key (e.g., in D major, for f
and c) Infact, when writing music by hand, alterations are put on the
key to spare the work
Silvio a Beccara wrote:
Instead, Lilypond puts
natural signs on every note which is not explicitely written with an
accidental, which is quite disappointing, since it does know where
accidentals should NOT be put!
So I think there ought to be a way to change this unlogical, and
unmusical,
Matthias Geier wrote:
What I need: There should be accidentials before every note, even if
it's just a natural sign. On note repetitions there should be an
accidental only before the first note and nothing before the following.
It's the way Schoenberg used to typeset his works.
Uh, I am
s.abeccara wrote:
When I state a key for a piece in Lilypond I expect it to follow
common rules for writing music,
Lilypond DOES follow common notational behaviour.
You specify which notes the music should contain, and then lilypond
decides how to typeset the accidentals on basis of the
hi,
On Fri, 2002-12-06 at 14:56, s.abeccara wrote:
When I state a key for a piece in Lilypond I expect it to follow
common rules for writing music, i.e. not to put natural signs on every
---SNIP---
who know this (after all simple) solution.
this is a discussion that has been kicked around the
Thank you - it worked ! With the upgrade to 1.6.6, the \translator \StaffContext
minimumVerticalExtent is also working !!
With the \translator \ScoreContext TimeSignature \override, I do get some error
messages about spacing but the output is fine. Can I safely assume that all is well?
Hi,
this is just to post an example of automatic (lilypond) score
generation. Sorry for being a bit off-topic.
If you want to try it, build and do something like:
tritone -n7 -l out.ly
and then compile out.ly .
Ciao,
- Fabio
--
Fabio Barbon ___ [EMAIL PROTECTED]
REAL
From: Edward Lee [mailto:[EMAIL PROTECTED]]
http://www.pstoedit.net
Interesting program! Doesn't help today, but I'm pretty sure
that I'll be using it in the future. Thanks!
___
Lilypond-user mailing list
[EMAIL PROTECTED]
Ray Peck wrote:
How about using GIMP to capture the images and create any efficient
image file you want to insert into your OpenOffice document?
I'm using GIMP for some things, but I want to avoid using pixmaps
as much as possible, and I want to be able to edit the pasted-in
image
Paul Scott wrote:
Ray Peck wrote:
How about using GIMP to capture the images and create any efficient
image file you want to insert into your OpenOffice document?
Here is an OpenOffice Writer document doing what you described with a
JPEG which I believe is not proprietary. It was
That would be Insert/Graphic/From File but you knew that.
Yeah.
If insert/graphic/from file would accept SVG than I'd be
cruisin'.
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
(sorry sending reply to the wrong posting - for some reason I didn't
receive the posting from s.abeccara)
Simon Bailey wrote:
| if i'm reading a piece in g major, then i
| will read any note in the bottom space of the treble staff as an
| f-sharp, not as an f. so i write fis for this
After a small bugfix in the accidental engraver (1.7 cvs), this hack
does more or less what you request.
The last measure shows an example where it goes wrong. Problem is that
the music is parsed in input order - so the 2nd e gets an accidental
because the 1st was not entered yet, whereas the
16 matches
Mail list logo
