Werner LEMBERG wrote:
> > It's only for some exotic tweaks that you might want to change
> > the fraction to something else than the default 15/16...
>
> Hmm. Section 1.2.6 in notation.pdf says that 3/4 is the default
> value for \afterGrace. A documentation bug?
Nope. Honest mistake.
- Mark
[You should use bug-lilyp...@gnu.org -- lilypond-...@gnu.org doesn't
work IIRC!]
> A clue for our brave developers: The attached image made from
>
> \stemDown c4 c\longa
>
> shows that the skyline mechanism does not consider the longa' stem
> worth to be skylined.
This is not a clue, this i
> It's only for some exotic tweaks that you might want to change the
> fraction to something else than the default 15/16...
Hmm. Section 1.2.6 in notation.pdf says that 3/4 is the default value
for \afterGrace. A documentation bug?
Werner
___
On Fri, Aug 07, 2009 at 12:26:42AM +0200, Francisco Vila wrote:
> >
> 2009/8/6 Laura Conrad :
> > It's scary if you play the wrong note even when you took all that care
> > to enter the right note.
>
> A clue for our brave developers: The attached image made from
>
> \stemDown c4 c\longa
>
> s
On Thu, Aug 06, 2009 at 03:29:11PM +0200, John Mandereau wrote:
> Le jeudi 06 août 2009 à 13:51 +0200, Reinhold Kainhofer a écrit :
> > No, big pages should link to the other big pages. That's how the current
> > .init
> > file is supposed to work. If it doesn' t, then that' s a bug in the script
On Thu, Aug 06, 2009 at 06:46:35PM +0200, John Mandereau wrote:
> Le jeudi 06 août 2009 à 00:08 -0700, Graham Percival a écrit :
> > As for category #2, we already have a great location for pieces of
> > input: the snippets. If there's anything of educational value in
> > input/, let's put it into
On Thu, 2009-08-06 at 07:11 -0700, Mark Polesky wrote:
> Joe Neeman wrote:
>
> > There doesn't seem to be. As a workaround, you could add a context
> > property called, say, "spanArpeggioInThisContext" and document somewhere
> > that the \connectArpeggiosOn command works in the lowermost context
>
On Thu, Aug 06, 2009 at 06:42:49PM +0200, Francisco Vila wrote:
> 2009/8/6 Patrick McCarty :
> > IIRC, Graham can't build GUB from scratch at the moment, so this is
> > the only hold-up.
Yes; I haven't had time to investigate this further within my 3-4
hours of lilypond each day. Given that all t
Hi Trevor,
I'm not sure I understand the need for this.
I would not normally use a lyric extender
unless the syllable had an extended duration
over several notes or was sung to a long note.
This occurs far less frequently than a 2-note melisma.
Do you attach lyric extenders unconditionally
to e
>
2009/8/6 Laura Conrad :
> It's scary if you play the wrong note even when you took all that care
> to enter the right note.
A clue for our brave developers: The attached image made from
\stemDown c4 c\longa
shows that the skyline mechanism does not consider the longa' stem
worth to be skylin
Kieren
I'm not sure I understand the need for this.
Maybe I'm missing something (it wouldn't be
unusual :)
I would not normally use a lyric extender
unless the syllable had an extended duration
over several notes or was sung to a long note.
This occurs far less frequently than a 2-note
melisma.
2009/8/6 Trevor Daniels :
> It works fine, Neil. At least it compiled several .itely files
> with no errors, so I'm back in business. Many thanks!!
Excellent. Thanks for testing it.
Regards,
Neil
___
lilypond-devel mailing list
lilypond-devel@gnu.
Neil Puttock wrote Thursday, August 06, 2009 9:58 PM
2009/8/6 Trevor Daniels :
I'm stuck too. Neil updated the LSR today,
so now lots of snippets require 2.13.4 and
I can no longer compile the docs easily, so
can't check any edits I make.
I'm sorry as always when this happens, Trevor, th
2009/8/6 Graham Percival :
> As for category #2, we already have a great location for pieces of
> input: the snippets. If there's anything of educational value in
> input/, let's put it into LSR. We don't currently have a
> "complete pieces" or "long examples" or whatever tag, but I'm sure
> Vale
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Donnerstag, 6. August 2009 19:39:22 schrieb John Mandereau:
> Le jeudi 06 août 2009 à 09:55 -0700, Mark Polesky a écrit :
> > \afterGrace
> > \afterGraceCustom
> >
> > Though I admit, I'm not particularly fond of this solution.
>
> Neither
2009/8/6 Trevor Daniels :
> I'm stuck too. Neil updated the LSR today,
> so now lots of snippets require 2.13.4 and
> I can no longer compile the docs easily, so
> can't check any edits I make.
I'm sorry as always when this happens, Trevor, though in my defence,
there were already some updated s
2009/8/6 John Mandereau :
>> \afterGrace {d1 {c16[ d] }} % works as now - except extra braces
>> \afterGrace {d1 {c16[ d] } 15 16} % extra two optional parameter does
>> the biz currently done by
>
> Music functions are defined in a simpler way: they take a fixed number
> of arguments, and by conv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Donnerstag, 6. August 2009 20:00:16 schrieb John Mandereau:
> Le jeudi 06 août 2009 à 19:52 +0200, Reinhold Kainhofer a écrit :
> > Hmm, the tag is still there in the html file (both before
> > postprocess_html.py and after). From a quick look at t
Le jeudi 06 août 2009 à 19:52 +0200, Reinhold Kainhofer a écrit :
> Hmm, the tag is still there in the html file (both before
> postprocess_html.py and after). From a quick look at the postprocess_html.py
> script it seems that all you do is replace that tag, so I suppose the
> texi2html part i
> "Francisco" == Francisco Vila writes:
>> Actually, what I did was print the part in a different clef. It's
>> really inauthentic to have music of that era (it was a transcription
>> from the Odhecaton) with ledger lines anyway. The new clef is a
>> better option.
Fran
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Donnerstag, 6. August 2009 19:33:06 schrieb John Mandereau:
> Le jeudi 06 août 2009 à 18:55 +0200, Reinhold Kainhofer a écrit :
> > On kainhofer.com I'm using the latest CVS version (updated yesterday),
> > and the language links are missing there:
On Thu, Aug 06, 2009 at 06:22:05PM +0200, John Mandereau wrote:
> Le mercredi 05 août 2009 à 21:03 -0700, Patrick McCarty a écrit :
> > I need this patch to run ./autogen.sh with the latest Autoconf version
> > (2.64). The only earlier version I am able to test is 2.63, which
> > works fine with t
2009/8/6 John Mandereau :
> Le jeudi 06 août 2009 à 18:55 +0200, Reinhold Kainhofer a écrit :
>> On kainhofer.com I'm using the latest CVS version (updated yesterday), and
>> the
>> language links are missing there:
>> http://kainhofer.com/~lilypond/Documentation/notation/Vocal-music.html
>
> Afte
Le jeudi 06 août 2009 à 09:55 -0700, Mark Polesky a écrit :
> \afterGrace
> \afterGraceCustom
>
> Though I admit, I'm not particularly fond of this solution.
Neither am I. Why not just junk the form?
> This would require modifying the define-music-function defmacro
> (on line 764 of
Le jeudi 06 août 2009 à 18:55 +0200, Reinhold Kainhofer a écrit :
> On kainhofer.com I'm using the latest CVS version (updated yesterday), and
> the
> language links are missing there:
> http://kainhofer.com/~lilypond/Documentation/notation/Vocal-music.html
After having read replies from you and
Le 06/08/2009 18:48, John Mandereau disait :
Le jeudi 06 août 2009 à 18:42 +0200, Francisco Vila a écrit :
Before releasing, please check that all HTML doc pages have links to
other languages at bottom.
Just checking any page not being the first, will serve. Some of us
have built the docs and
2009/8/6 Laura Conrad :
> Actually, what I did was print the part in a different clef. It's
> really inauthentic to have music of that era (it was a transcription
> from the Odhecaton) with ledger lines anyway. The new clef is a
> better option.
What a coincidence! I am very busy these days tryi
2009/8/6 John Mandereau :
> Le jeudi 06 août 2009 à 18:42 +0200, Francisco Vila a écrit :
>> Before releasing, please check that all HTML doc pages have links to
>> other languages at bottom.
>>
>> Just checking any page not being the first, will serve. Some of us
>> have built the docs and have o
> "Francisco" == Francisco Vila writes:
Francisco> it's a Longa with the cropped stem that makes it to
Francisco> appear as a breve. Change g,\longa to
Francisco>\longa
Francisco> and the stem appears (the lower g still is cropped)
Actually, what I did was print the par
2009/8/6 Reinhold Kainhofer :
> Works correctly in lilypond 2.13.4.
It works for lilypond alone on very latest 2.13.4, but not for
lilypond-book. The eps shows the stem cropping.
> Is the snippet (the eps file) cut too tight on your computer and the stem is
> included, but cut off by the bounding
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Donnerstag, 6. August 2009 18:48:12 schrieb John Mandereau:
> Le jeudi 06 août 2009 à 18:42 +0200, Francisco Vila a écrit :
> > Before releasing, please check that all HTML doc pages have links to
> > other languages at bottom.
> >
> > Just checking
Ian Hulin wrote:
> Is there a way of do this sort of thing sometime in the future?
>
> \afterGrace {d1 {c16[ d] }} % works as now - except extra braces
> \afterGrace {d1 {c16[ d] } 15 16} % extra optional parameters
Well, now I think we're pretty much back at Han-Wen's original
suggestion, which
2009/8/6 Laura Conrad :
>
> The attached lilypond file displays the G below the staff correctly as
> a longa (square note with a tail) if you say "lilypond
> tenor-simple.ly".
>
> However, if you include it in the attached .lytex file, and "make
> tenorbook.pdf" with the attached makefile, the othe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Donnerstag, 6. August 2009 18:09:07 schrieb Laura Conrad:
> The attached lilypond file displays the G below the staff correctly as
> a longa (square note with a tail) if you say "lilypond
> tenor-simple.ly".
>
> However, if you include it in the att
Le jeudi 06 août 2009 à 18:42 +0200, Francisco Vila a écrit :
> Before releasing, please check that all HTML doc pages have links to
> other languages at bottom.
>
> Just checking any page not being the first, will serve. Some of us
> have built the docs and have observed this problem; John is on
Le jeudi 06 août 2009 à 00:08 -0700, Graham Percival a écrit :
> IMO, there are two kinds of examples here.
> 1) advertizing examples: "we can do tabs, complex rhythms, lots
> of accidentals, gregorian chant, etc etc". We expect people to
> glance at the image and then move on.
> 2) educational
2009/8/6 Patrick McCarty :
> On Thu, Aug 06, 2009 at 03:54:33PM +0100, Trevor Daniels wrote:
>>
>> Mark Polesky wrote Thursday, August 06, 2009 3:26 PM
>> >
>> >Anything holding up 2.13.4? By now there are so
>> >many new things that I'd like to try, but I'm a
>> >non-compiler, so...
>>
>> I'm stuc
The attached lilypond file displays the G below the staff correctly as
a longa (square note with a tail) if you say "lilypond
tenor-simple.ly".
However, if you include it in the attached .lytex file, and "make
tenorbook.pdf" with the attached makefile, the other \longas are still
displayed correc
Le mercredi 05 août 2009 à 21:03 -0700, Patrick McCarty a écrit :
> I need this patch to run ./autogen.sh with the latest Autoconf version
> (2.64). The only earlier version I am able to test is 2.63, which
> works fine with the patch.
>
> The warnings I am seeing and workarounds are here:
>
> h
On Thu, Aug 06, 2009 at 11:44:17AM +0200, Valentin Villenave wrote:
> 2009/8/6 Patrick McCarty :
> > Any comments or suggestions are welcome. This patch is one of the
> > final steps towards producing SVG output that is both valid and
> > compatible across all user agents I have tested (Inkscape,
On Wed, Aug 05, 2009 at 09:03:10PM -0700, Patrick McCarty wrote:
> Hello,
>
> I need this patch to run ./autogen.sh with the latest Autoconf version
> (2.64). The only earlier version I am able to test is 2.63, which
> works fine with the patch.
>
> The warnings I am seeing and workarounds are h
On Thu, Aug 06, 2009 at 03:54:33PM +0100, Trevor Daniels wrote:
>
> Mark Polesky wrote Thursday, August 06, 2009 3:26 PM
> >
> >Anything holding up 2.13.4? By now there are so
> >many new things that I'd like to try, but I'm a
> >non-compiler, so...
>
> I'm stuck too. Neil updated the LSR today,
Le jeudi 06 août 2009 à 16:14 +0100, Ian Hulin a écrit :
> At the moment it looks like we're setting the equivalent of a global
> static variable to do this - bad news for such a specific function.
Indeed.
> Is there a way of do this sort of thing sometime in the future?
>
> \afterGrace {d1 {
Le jeudi 06 août 2009 à 00:29 -0700, Graham Percival a écrit :
> 1) news items: would it be possible to keep the news-front vs.
> news-old? I'd like to maintain human control over what's on the
> front page.
This is achieved easily by marking news entries with ad-hoc tags, e.g. a
dummy Texinfo ma
Han-Wen Nienhuys wrote:
On Thu, Aug 6, 2009 at 11:19 AM, Mark Polesky wrote:
Han-Wen Nienhuys wrote:
I think in general the manual should not encourage users to define or
set variables using Scheme, exactly because the scoping semantics are
confusing.
I just had an idea. Why no
Mark Polesky wrote Thursday, August 06, 2009 3:26 PM
Anything holding up 2.13.4? By now there are so
many new things that I'd like to try, but I'm a
non-compiler, so...
I'm stuck too. Neil updated the LSR today,
so now lots of snippets require 2.13.4 and
I can no longer compile the docs easi
On Thu, Aug 6, 2009 at 11:19 AM, Mark Polesky wrote:
>
> Han-Wen Nienhuys wrote:
>
>> I think in general the manual should not encourage users to define or
>> set variables using Scheme, exactly because the scoping semantics are
>> confusing.
>
> I just had an idea. Why not make afterGraceFraction
Anything holding up 2.13.4? By now there are so
many new things that I'd like to try, but I'm a
non-compiler, so...
- Mark
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
John, you wrote Thursday, August 06, 2009 3:01 PM
No; I'm on Windows Vista, so building isn't an option, is it?
No, but you can still run check-xrefs and fix-xrefs, but it will
complain about missing files markup*.tely, internals.tely and so
on.
Good. In that case I'll leave them for som
Han-Wen Nienhuys wrote:
> I think in general the manual should not encourage users to define or
> set variables using Scheme, exactly because the scoping semantics are
> confusing.
I just had an idea. Why not make afterGraceFraction a context property
for Score? Wouldn't that solve all of these
Joe Neeman wrote:
> There doesn't seem to be. As a workaround, you could add a context
> property called, say, "spanArpeggioInThisContext" and document somewhere
> that the \connectArpeggiosOn command works in the lowermost context
> where spanArpeggioInThisContext is true. This preserves the abi
Andrew Hawryluk wrote:
> I think even this simple case might fail if the dots were placed in
> the Voice context:
> << c''4. \\ b'4. >>
Yes, but I would consider this a "mesh". If there is a way to test
for that, this situation would not qualify for moving the engraver
to the Voice context.
- M
Le jeudi 06 août 2009 à 04:18 -0700, Graham Percival a écrit :
> > make check-xrefs
> I need to spend 1-2 more days on the AU, but then I'll finally
> start my CG review. I'll definitely add this at that point.
Documentation]$ grep check-xrefs contributor/*
contributor/doc-work.itexi:for check-x
Trevor Daniels wrote:
> BTW, I'd be grateful if you and other developers could keep an
> eye on the text as I add it, and fix or comment on any inaccuracies,
> as I'm a little out of my depth with some of the terms.
No need to worry. Any inaccuracies will be cleared up eventually.
I, for one, wo
Le jeudi 06 août 2009 à 14:48 +0100, Trevor Daniels a écrit :
> No; I'm on Windows Vista, so building isn't an option, is it?
No, but you can still run check-xrefs and fix-xrefs, but it will
complain about missing files markup*.tely, internals.tely and so on.
> Good. In that case I'll leave the
John Mandereau wrote Thursday, August 06, 2009 12:06 PM
Le jeudi 06 ao=C3=BBt 2009 =C3=A0 11:35 +0100, Trevor Daniels a
=C3=A9crit =
:
Have you tried building docs inside the source tree?
No; I'm on Windows Vista, so building isn't an option, is it?
I generated my own scripts so I can have
Le jeudi 06 août 2009 à 13:51 +0200, Reinhold Kainhofer a écrit :
> No, big pages should link to the other big pages. That's how the current
> .init
> file is supposed to work. If it doesn' t, then that' s a bug in the script
> and
> needs to be fixed.
But does the web site in one large page m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Donnerstag, 6. August 2009 13:46:33 schrieb Francisco Vila:
> 2009/8/6 Graham Percival :
> > As for the "one big HTML" docs, I'd suggest that it @ref to the
> > splitted general html.
No, big pages should link to the other big pages. That's how th
On Thu, Aug 06, 2009 at 01:46:33PM +0200, Francisco Vila wrote:
> 2009/8/6 Graham Percival :
> > As for the "one big HTML" docs, I'd suggest that it @ref to the
> > splitted general html. That said, I've never been a fan of the
> > "one big html" stuff, so if anybody who uses that wants to argue
>
On Tue, 2009-08-04 at 21:23 -0700, Mark Polesky wrote:
> Neil Puttock wrote:
> > (let* ((Arpeggio
> > arpeggio (or something else without the capital letter)
>
> What's bad about the capital letter? I capitalized it because it's
> a grob-name and grob-names are capitalized. Does the same problem
>
2009/8/6 Graham Percival :
> As for the "one big HTML" docs, I'd suggest that it @ref to the
> splitted general html. That said, I've never been a fan of the
> "one big html" stuff, so if anybody who uses that wants to argue
> that we *should* create one big general.html... and if that person
> wa
Andrew Hawryluk writes:
> 2009/8/5 John Mandereau :
>> dots.ly before
>> dots.ly after
>>
>> collision-mesh.ly before
>> collision-mesh.ly after
>
> I think even this simple case might fail if the dots were placed in
> the Voice context:
> << c''4. \\ b'4. >>
>
> In the example that Mark found, t
Graham Percival wrote:
On Thu, Aug 06, 2009 at 12:12:59AM +0100, Ian Hulin wrote:
This is AU section 3.2.1
--
If ‘filename.ly’ contains more than one \score block, then the rest of the
scores will be output in numbered files, starting with ‘filename-1.pdf’.
--
This is a regression:
On Thu, Aug 06, 2009 at 01:06:20PM +0200, John Mandereau wrote:
> Le jeudi 06 août 2009 à 11:35 +0100, Trevor Daniels a écrit :
> > > Not until we have @rweb or @rgeneral or whatever it gets called.
> > > At least, that's what the @ref{Setup for MacOS X} are waiting for.
>
> Adding cross-reference
Le jeudi 06 août 2009 à 11:35 +0100, Trevor Daniels a écrit :
> > Not until we have @rweb or @rgeneral or whatever it gets called.
> > At least, that's what the @ref{Setup for MacOS X} are waiting for.
> > I admit that I could fix the @rprogram{LilyPond-book} link right
> > now if it was a priority
Le mercredi 05 août 2009 à 23:40 -0700, Graham Percival a écrit :
> Is it ok if Patrick Schmidt and I do a few more days' work on that
> branch? The changes would be almost all[1] in his css/alt2.css
> file.
The changes can be wherever you like, the guy that will import these
changes just has to
Graham Percival wrote Thursday, August 06, 2009 10:06 AM
On Thu, Aug 06, 2009 at 09:50:56AM +0100, Trevor Daniels wrote:
I've just pushed another fix for broken refs resulting from your
doc
reorganisation.
Oops, I forgot that I need to "touch foo.tely" before testing.
That said, it would o
On Thu, Aug 06, 2009 at 11:44:17AM +0200, Valentin Villenave wrote:
> 2009/8/6 Patrick McCarty :
> > Any comments or suggestions are welcome. This patch is one of the
> > final steps towards producing SVG output that is both valid and
> > compatible across all user agents I have tested (Inkscape,
2009/8/6 Patrick McCarty :
> Any comments or suggestions are welcome. This patch is one of the
> final steps towards producing SVG output that is both valid and
> compatible across all user agents I have tested (Inkscape, Firefox,
> etc.)
Though single-page SVG output is a sensible default, perha
On Thu, Aug 06, 2009 at 09:50:56AM +0100, Trevor Daniels wrote:
> I've just pushed another fix for broken refs resulting from your doc
> reorganisation.
Oops, I forgot that I need to "touch foo.tely" before testing.
That said, it would only find the broken @ref, not the broken
@rprogram stuff.
John Mandereau wrote Wednesday, August 05, 2009 8:47 PM
At least one of the terms listed by Mark is introduced in the
Learning
Manual: "grob" in 4.1.2 Objects and interfaces. I see this
glossary
could be a quick reference that briefly defines each term and
gives
cross-references to document
Graham
I've just pushed another fix for broken refs resulting from your doc
reorganisation. As there seems to be no replacement nodes all I can
do is comment them out with a FIXME. Any chance you could add
replacement nodes as you go so we can fix the links properly rather
than scattering F
On Thu, Aug 06, 2009 at 12:32:20AM -0700, Graham Percival wrote:
> On Thu, Aug 06, 2009 at 12:29:58AM -0700, Patrick McCarty wrote:
> > The details are listed on the Rietveld page, but I'll illustrate the
> > naming convention here.
> >
> > 1) One book, four pages (test.ly):
> >
> > test.svg
>
On Thu, Aug 06, 2009 at 12:29:58AM -0700, Patrick McCarty wrote:
> The details are listed on the Rietveld page, but I'll illustrate the
> naming convention here.
>
> 1) One book, four pages (test.ly):
>
> test.svg
> test-page2.svg
> test-page3.svg
> test-page4.svg
Speaking as a user, cou
On Wed, Aug 05, 2009 at 08:06:43PM +0200, John Mandereau wrote:
> The web site in Texinfo is on master now, except the examples (see my
> other email). All of what I could think of the technical status and
> to-do is in the commmit message.
A few comments about some of those FIXMEs/TODOs:
1) new
Graham Percival wrote Thursday, August 06, 2009 7:51 AM
On Thu, Aug 06, 2009 at 12:12:59AM +0100, Ian Hulin wrote:
This is AU section 3.2.1
--
If ‘filename.ly’ contains more than one \score block, then the
rest of the
scores will be output in numbered files, starting with
‘filename-1.p
Hello,
I have uploaded a patch to Rietveld:
http://codereview.appspot.com/105045/show
***
The details are listed on the Rietveld page, but I'll illustrate the
naming convention here.
1) One book, four pages (test.ly):
test.svg
test-page2.svg
test-page3.svg
test-page4.svg
2) Two books
On Wed, Aug 05, 2009 at 07:57:52PM +0200, John Mandereau wrote:
> The new directory Documentation/examples that was proposed to host
> examples for the web site plays a duplicate role of input/ and
> input/mutopia. What about cleaning up these two directories (that is,
> deleting unused input file
78 matches
Mail list logo
