On 2-Apr-06, at 7:25 AM, Dave K. wrote:
As far as I can tell there is no flush left/flush right
option in Lilypond,
Yes there is; see the documentation for Text marks and/or Rehearsal
marks. They're in chapter 8.
Yes, I know I can manually align every single
symbol I markup, but that
On 1-Apr-06, at 11:58 PM, Paul Scott wrote:
|direction| (direction):
|1|
Up or down, left or right?
The new reader wouldn't know that 1 was UP and -1 was DOWN and 0 was
in the middle. Also LEFT and RIGHT are the same as DOWN and UP,
respectively.
Ok, thanks. Fixed in CVS.
-
Hello
First of all , i wish to say thanx to everybody working on the dev of
lily.
the last version is great.
Ok, now for some remarks.
the nested tuplets feature which is really great has however one
inconvenient.
As we can see in the news doc, when these occur the brackets are too
tight
GP == Graham Percival [EMAIL PROTECTED] writes:
Put this at the top of your input file:
#(ly:set-option (quote no-point-and-click))
Should this be given more prominent play in the manual? I think we've
had several questions on it of late, and you kind of have to know
The bug report below surprisingly gives no warning. In real-life
situations I get
warning: junking event: `BeamEvent'
\acciaccatura { f16[ g
] }
Maybe there is a simple fix for it...
Werner
I am seeing a 5x to 10x increase in .pdf file size
when using 2.8.1. versus 2.6. For example a simple
4 page score goes from 380K to 2.1MB.
This is using Windows XP.
Thank you.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
I posted the following previously:
After upgrading to 2.8.1, I notice that the .pdf files produced are
considerable larger, on the order of about 5 to 10 times the size
formerly produced. This has a detrimental effect on my ability to
store and distribute, so much that I have to back level to
Just wondering if this is an actual issue or whether I'm misreading
things. Is the horizontal placement of these chords alright? I was
under the impression that there should be space on the left.
On 4/2/06, Dave K. [EMAIL PROTECTED] wrote:
v2.8.1
{
g' b' c'' e''1^\fermata
g' b' c''
On 4/5/06, karim haddad [EMAIL PROTECTED] wrote:
Hello
First of all , i wish to say thanx to everybody working on the dev of
lily.
the last version is great.
Ok, now for some remarks.
the nested tuplets feature which is really great has however one
inconvenient.
As we can see in the news
Dennis O\'Toole wrote:
I posted the following previously:
After upgrading to 2.8.1, I notice that the .pdf files produced are
considerable larger, on the order of about 5 to 10 times the size
formerly produced. This has a detrimental effect on my ability to
store and distribute, so much that
Assuming that there's no such file as asdfg.ly, typing:
lilypond asdfg.ly
gives as output:
warning: can't find file: `'
error: failed files: asdfg.ly
This makes it appear that the file exists (it failed, after all) but
has a bad \include in it somewhere--I just spent a good twenty minutes
The bug report below surprisingly gives no warning. In real-life
situations I get
warning: junking event: `BeamEvent'
\acciaccatura { f16[ g
] }
Maybe there is a simple fix for it...
I've fixed it by myself in the CVS :-) BTW, the above message is
caused
Dear Trevor
Great Thanx it works ! it was the bracket padding that i have missed.
I will let you know if i encounter some impossible notation. But for the
time being,
Lily is the best.
Thanx to all again .
Karim
On 4/5/06, karim haddad [EMAIL PROTECTED] wrote:
Hello
First of all , i wish
Hello !
I found your article
http://sca.uwaterloo.ca/lilypond/lilypond.org/doc/v2.7/Documentation/user/music-glossary/source/Documentation/user/music-glossary.html
very informative and amazingly complete.
But there is a major problem with the name of notes and rests.
In English (and maybe in
Werner LEMBERG wrote:
The bug report below surprisingly gives no warning. In real-life
situations I get
warning: junking event: `BeamEvent'
\acciaccatura { f16[ g
] }
Maybe there is a simple fix for it...
I've fixed it by myself in the CVS :-) BTW, the above
Hello list,
in comparing the PDF output of the lilypond combo
as distributed in the 2.8.1 tarballs (for Linux/X86)
with the results generated by my locally comiled LilyPond
I found some strange difference:
The noteheads in the results from local Lily look like
bad bitmaps while those from the
Dennis O'Toole wrote:
See attached. Interestingly, the.ps is correspondingly smaller as
it used to be in the 2 MB range.
There is something very strange going on with this file
muurbloem:/tmp/ms$ pdfinfo TULIPS_2006-04-03.pdf
Creator:LilyPond 2.8.0
Producer: GPL Ghostscript
If it's any help to the debuggers. I installed 2.8.0 on Win XP this week,
and my PDF files are pretty small, around 50k for a 1 page song sheet with
chords lyrics and 3 voice polyphony. Prior to installing, my machine had
pretty much nothing on it except Microsoft applications, so I assume it
I've fixed it by myself in the CVS :-)
cool! don't forget to backport.
How do I do this?
Werner
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
19 matches
Mail list logo
