Grand LilyPond Input Syntax Stabilization (GLISS) webpage

Grand LilyPond Input Syntax Stabilization (GLISS) It's up, such as it is: http://lilypond.org/~graham/gliss/ If you remember the email from a few months ago, nothing much has changed (I've rephrased a few things based on the comments). If you don't know what I'm talking about, take a quick s

Add basic scheme programmable engravers. (issue181109)

Neat! http://codereview.appspot.com/181109/diff/17/21 File lily/context-scheme.cc (right): http://codereview.appspot.com/181109/diff/17/21#newcode26 lily/context-scheme.cc:26: // TODO: naming - should use now? I think ly:context-current-moment is clearer (although of course it isn't consistent

Re: Autobeaming

Am Samstag, 2. Januar 2010 00:35:16 schrieb Carl Sorensen: > On 1/1/10 10:27 AM, "David Kastrup" wrote: > > Carl Sorensen writes: > >> OK, point taken. I'll come up with a different name for the music > >> function. Do you have any suggestions? > >> > >> How about \pushTimeSignatureSetting and

Re: Autobeaming

On 1/1/10 10:27 AM, "David Kastrup" wrote: > Carl Sorensen writes: > >> On 1/1/10 6:13 AM, "David Kastrup" wrote: >> >>> "Trevor Daniels" writes: >>> For varying time signatures changes could still be made via \overrideTimeSignatureSettings. >>> >>> I consider it a grave user

Re: G clef changes [was: Re: Alternative music font]

On Fri, Jan 1, 2010 at 9:18 PM, Carl Sorensen wrote: >> This doesn't make a lot of sense: you should print out the PDF on a >> 1200 dpi printer, and see how it looks on paper.  Screen appearances >> are misleading. > > OK, so if we print it out on a 1200 dpi printer, how do we get approval for >

Re: input/regression/tuplet-text-*.ly wrong version

On Fri, Jan 01, 2010 at 03:27:48PM +0100, James Bailey wrote: > The regression tests for input/regression/tuplet-text*.ly have a version > statement of 2.12.3, although they don't compile with 2.12.3, and these > tests were not included in 2.12.3. Good catch! Could you go to the web interface f

Re: G clef changes [was: Re: Alternative music font]

On 1/1/10 4:08 PM, "Han-Wen Nienhuys" wrote: > On Fri, Jan 1, 2010 at 2:21 PM, Marc Hohl wrote: > >>> >>> IIUC, you should do the following: >>> >>> 1) Make a sample at 1200 dpi and post it somewhere so that we can be >>> satisfied that it looks right at 1200 dpi. >>> >> >> Ok, I used th

Re: Autobeaming

On Fri, Jan 01, 2010 at 02:13:51PM +0100, David Kastrup wrote: > "Trevor Daniels" writes: > > > For varying time signatures changes could still > > be made via \overrideTimeSignatureSettings. > > I consider it a grave user interface mistake to have some things work > only with \overrideTimeSigna

Re: Make doc broken by french translation

Le mardi 29 décembre 2009 à 20:37 -0700, Carl Sorensen a écrit : > The documentation is broken right now due to the french translation of the > Notation reference. > > A bad index entry is found in Documentation/fr/out-www/notation.cp > > Line 2 in this file is: > > \entry{\par }{1}{\code {\par

Re: G clef changes [was: Re: Alternative music font]

On Fri, Jan 1, 2010 at 2:21 PM, Marc Hohl wrote: >> >> IIUC, you should do the following: >> >> 1) Make a sample at 1200 dpi and post it somewhere so that we can be >> satisfied that it looks right at 1200 dpi. >> > > Ok, I used the same example and created a sample page. > It is available as a 1

Re: please do a "make doc-clean; make clean"

On 1/1/10 2:51 PM, "John Mandereau" wrote: > Le mercredi 30 décembre 2009 à 16:06 -0700, Carl Sorensen a écrit : >> I did decide to try the out-of-tree build, which required me to do a new >> configure. I thought I could do a configure in the out-of-tree build >> directrory, but the error mes

Re: please do a "make doc-clean; make clean"

Le mercredi 30 décembre 2009 à 16:06 -0700, Carl Sorensen a écrit : > I did decide to try the out-of-tree build, which required me to do a new > configure. I thought I could do a configure in the out-of-tree build > directrory, but the error messages said I had to do a make distclean first. > Afte

[PATCH]: New G clef

Marc Hohl has worked on a new G clef that is rotated about 1.5 degrees clockwise to improve its balance, as suggested by Jan (see ) A 1200-dpi png is available at http://www.hohlart.de/marc/gcleftest.png A patch is availa

Re: G clef changes

Marc Hohl writes: > Carl Sorensen schrieb: > > Ok, I used the same example and created a sample page. > It is available as a 1200 dpi png picture at: > > http://www.hohlart.de/marc/gcleftest.png Ouch, ouch, ouch. Don't load this as a picture into firefox on X11. It is something like 1x1000

Re: Autobeaming

Carl Sorensen writes: > On 1/1/10 6:13 AM, "David Kastrup" wrote: > >> "Trevor Daniels" writes: >> >>> For varying time signatures changes could still >>> be made via \overrideTimeSignatureSettings. >> >> I consider it a grave user interface mistake to have some things work >> only with \over

Re: G clef changes [was: Re: Alternative music font]

Carl Sorensen schrieb: On 1/1/10 2:52 AM, "Marc Hohl" wrote: Carl Sorensen schrieb: [...] Ok, so I'll go for this. It isn't as easy as I thought, because I cannot just rotate the whole picture, because the path is too complex for metafont. So I'll have to transform every poin

Re: G clef changes [was: Re: Alternative music font]

On 1/1/10 2:52 AM, "Marc Hohl" wrote: > Carl Sorensen schrieb: >> [...] >>> Ok, so I'll go for this. It isn't as easy as I thought, because I cannot >>> just rotate the whole picture, because the path is too complex for metafont. >>> So I'll have to transform every point and draw thereafter. I

Re: Autobeaming

On 1/1/10 6:13 AM, "David Kastrup" wrote: > "Trevor Daniels" writes: > >> For varying time signatures changes could still >> be made via \overrideTimeSignatureSettings. > > I consider it a grave user interface mistake to have some things work > only with \overrideTimeSignatureSettings, but

Re: Autobeaming

On 1/1/10 5:40 AM, "Trevor Daniels" wrote: > > > Carl Sorensen wrote Tuesday, December 29, 2009 6:27 PM > >> On 12/29/09 8:41 AM, "Carl Sorensen" wrote: >> >> I think I've got a consistent idea now. I think I can add a >> property >> (probably 'details to avoid namespace pollution, but m

New articulation character for half-open hi-hats?

In most of the books and literature about drumming I have, the half-open hi-hat is typeset as in the attached PNG file with an articulation that looks somewhat like the empty set in the Symbol font or the character Ø. Unfortunately, LilyPond does not seem to have an articulation character that cou

input/regression/tuplet-text-*.ly wrong version

The regression tests for input/regression/tuplet-text*.ly have a version statement of 2.12.3, although they don't compile with 2.12.3, and these tests were not included in 2.12.3. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.

Re: 2.13.10 pre-release testing

On Jan 1, 2010, at 5:02 AM, James Bailey wrote: Yet more architectural changes to GUB, so I thought it'd be worth hearing if it works. lilypad should be included automatically now. http://lilypond.org/~graham/ Cheers, - Graham Expected output is generated using OSX-ppc 10.5.8 also. Happy

Re: Autobeaming

"Trevor Daniels" writes: > For varying time signatures changes could still > be made via \overrideTimeSignatureSettings. I consider it a grave user interface mistake to have some things work only with \overrideTimeSignatureSettings, but not with \override timeSignatureSettings. It is already b

Re: Autobeaming

Carl Sorensen wrote Tuesday, December 29, 2009 6:27 PM On 12/29/09 8:41 AM, "Carl Sorensen" wrote: I think I've got a consistent idea now. I think I can add a property (probably 'details to avoid namespace pollution, but maybe timeSignatureDefaults) to the TimeSignature grob. Then I can u

Re: 2.13.10 pre-release testing

Graham Percival wrote Friday, January 01, 2010 2:18 AM The recent problem with end-of-line in mingw is (believed to be) fixed; It is. Thanks Patrick! In testing I noticed another niggle. Clicking on the url which now appears in the pdf causes Adobe Reader to fire up a browser, as it shoul

Re: 2.13.10 pre-release testing

looks alright here on osx 10.4, intel On 31.12.2009, at 09:15, Graham Percival wrote: Yet more architectural changes to GUB, so I thought it'd be worth hearing if it works. lilypad should be included automatically now. http://lilypond.org/~graham/ Cheers, - Graham __

Re: G clef changes [was: Re: Alternative music font]

Carl Sorensen schrieb: [...] Ok, so I'll go for this. It isn't as easy as I thought, because I cannot just rotate the whole picture, because the path is too complex for metafont. So I'll have to transform every point and draw thereafter. It seems to work, but I have to change some explicit draw