Re: Why is the installer file so big?

2006-06-24 Thread Quentin Spencer
Matthias Kilian wrote: On Sat, Jun 24, 2006 at 08:26:06PM +, Davide Castellone wrote: Why doesn't the Lilypond installer seem to be compressed? With my very slow 56k Internet connection I find the source-tarball (about 2.5 MB) more easy to download than the installer for GNU/Linux (>11 M

Re: AllAbout Examples

2006-06-24 Thread Graham Percival
On Sat, 24 Jun 2006 11:37:08 -0500 "Fairchild" <[EMAIL PROTECTED]> wrote: > The LSR entries seem to be short things They're mostly short, but it can have long things as well. > that haven't made the cut for > Tips and Tricks or Regression Tests. Actually, currently LSR is a mish-mash of lots of

Re: AllAbout Examples

2006-06-24 Thread Graham Percival
On Sat, 24 Jun 2006 17:38:43 -0500 "Fairchild" <[EMAIL PROTECTED]> wrote: > Seems that LSR won't accept 2.4.6. I've made enquiries about LSR (I think it's still on 2.6), but we cannot accept anything into the docs if it requires 2.4. I remember that you had some problems with 2.6; do they still

RE: AllAbout Examples

2006-06-24 Thread Fairchild
Trevor - I commented the point-and-click and resubmitted; failed again. Don't know what to do about the def-music-function. Seems that LSR won't accept 2.4.6. Just wending through the LSR screens to submit is painful, then failing without reason is discouraging. More reasons for a mainstream r

Re: proportional grace notes

2006-06-24 Thread V!ictor [EMAIL PROTECTED]
Hi Eduardo, I think you're right. This may by the way to change the spacing, but I'm not sure how to use this. I'll experiment with it a bit. If i find something I'll let you know. Thanks, victor. On Fri, Jun 23, 2006 at 08:56:56PM -0300, Eduardo Vieira wrote: Content-Description: Mail messag

Re: Why is the installer file so big?

2006-06-24 Thread Matthias Kilian
On Sat, Jun 24, 2006 at 08:26:06PM +, Davide Castellone wrote: > Why doesn't the Lilypond installer seem to be compressed? With > my very slow 56k Internet connection I find the source-tarball > (about 2.5 MB) more easy to download than the installer for > GNU/Linux (>11 MB), but the sources mu

Why is the installer file so big?

2006-06-24 Thread Davide Castellone
Why doesn't the Lilypond installer seem to be compressed? With my very slow 56k Internet connection I find the source-tarball (about 2.5 MB) more easy to download than the installer for GNU/Linux (>11 MB), but the sources must be compiled (all troubles included...). Isn't it possible to download

Re: proportional grace notes

2006-06-24 Thread Trevor Bača
On 6/23/06, V!ictor [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: On Fri, Jun 23, 2006 at 02:16:40PM -0500, Trevor Ba?a wrote: > On 6/23/06, V!ictor [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > >On Thu, Jun 22, 2006 at 10:47:02PM -0500, Trevor Ba?a wrote: > >> On 6/22/06, V!ctor [EMAIL PROTECTED

Re: AllAbout Examples

2006-06-24 Thread Trevor Bača
On 6/24/06, Fairchild <[EMAIL PROTECTED]> wrote: Graham - AllAbout examples usually will be much larger than the LSR entries and too big for the manual. Think about an AllAbout that displays all font sets, one to demonstrate vertical layout options for a multipage score, one showing lots of way

RE: AllAbout Examples

2006-06-24 Thread Fairchild
I tried. After stumbling for a while, got to a little [JavaScript Application] window: "Error running Lilypond:" No hint as to what to do about it. - Bruce -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fairchild Sent: Saturday, Jun

RE: AllAbout Examples

2006-06-24 Thread Fairchild
Graham - AllAbout examples usually will be much larger than the LSR entries and too big for the manual. Think about an AllAbout that displays all font sets, one to demonstrate vertical layout options for a multipage score, one showing lots of ways to use \markup, or the many ways to enter and dis

Re: programming error : no heads for arpeggio found ?

2006-06-24 Thread Roland Goretzki
Hello list, hello David, You wrote: > I get this error also. It comes when I use the \arpeggio without > specifically assigning a chord with it. In other words: \arpeggio = > no error while something like > << e\arpeggio \\ c\arpeggio >> will generate the error. The output looks > correct wi