On Tue, Aug 11, 2009 at 12:51:18AM -0300, Han-Wen Nienhuys wrote:
> On Mon, Aug 10, 2009 at 10:19 PM, Graham
> Percival wrote:
> > Are these for the Open Source Metadata Framework?
> > http://www.ibiblio.org/osrt/omf/
>
> Yes.
>
> > Are they actually being used? If not, can I remove them?
>
> I
2009/8/11 Johannes Schindelin :
> Okay, I could not resist, so here is something more capable.
Thanks for not being more resistable. :-) (And for giving a nice
illustration how easy it actually is to write a quick hacked-up GUI -
I guess that'll be useful to me on many occasions in the future).
> Pushed to git.
Thanks a lot!
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On Mon, Aug 10, 2009 at 05:35:15PM -0700, Graham Percival wrote:
> On Mon, Aug 10, 2009 at 05:27:15PM -0700, Patrick McCarty wrote:
> > On Mon, Aug 10, 2009 at 05:08:51PM -0700, Graham Percival wrote:
> > > Tail of target/linux-x86/log/build.log
> > > Tail of target/linux-x86/log/
On Mon, Aug 10, 2009 at 10:19 PM, Graham
Percival wrote:
> The main doc pages all contain stuff like:
>
> @c don't remove this comment.
> @ignore
> @omfcreator Han-Wen Nienhuys, Jan Nieuwenhuizen and Graham Percival
> @omfdescription Learning Manual of the LilyPond music engraving system
> @omftype
Neil Puttock writes:
> Very shapely parentheses. :)
Thank you, and thanks for the comments! Here are two addenda
to the original patch that make the improvements you suggested:
commit 79259e82dea04bec0090152268ac8ec3ad12ff1f
Author: Thomas Morgan
Date: Mon Jul 27 20:22:03 2009 -0400
Ma
The main doc pages all contain stuff like:
@c don't remove this comment.
@ignore
@omfcreator Han-Wen Nienhuys, Jan Nieuwenhuizen and Graham Percival
@omfdescription Learning Manual of the LilyPond music engraving system
@omftype program usage
@omfcategory Applications|Publishing
@omflanguage Engli
On Tue, 2009-08-11 at 02:17 +0200, Francisco Vila wrote:
> 2009/8/11 Joe Neeman :
> > Is the footer too close to the lyrics? The default value (in the paper
> > block) for bottom-system-spacing is
> > bottom-system-spacing = #'((space . 1) (padding . 1) (min-distance . 0)
> > (stretchability . 5))
On Tue, 2009-08-11 at 02:19 +0200, Reinhold Kainhofer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Am Dienstag, 11. August 2009 02:04:28 schrieb Joe Neeman:
> > With the uninitialized variables fix, the remaining issues might just be
> > due to bad default settings (see below). I w
On Mon, Aug 10, 2009 at 05:27:15PM -0700, Patrick McCarty wrote:
> On Mon, Aug 10, 2009 at 05:08:51PM -0700, Graham Percival wrote:
> > Tail of target/linux-x86/log/build.log
> > Tail of target/linux-x86/log/build.log
>
> rm -rf target/freebsd-x86/packages/guile*
I tried that,
On Mon, Aug 10, 2009 at 05:08:51PM -0700, Graham Percival wrote:
> GUB "make lilypond" fails with:
>
> building package: freebsd-x86::guile
> *** Stage: download (guile, freebsd-x86)
> *** Stage: untar (guile, freebsd-x86)
> *** Stage: patch (guile, freebsd-x86)
> *** Stage: autoupdate (guile,
2009/8/11 Joe Neeman :
>> - -) The staves are really crammed together.
>
> This is controlled by the between-system-spacing \paper-block variable
> (try increasing 'space).
Let's be careful about not mixing staves and systems in our wording.
I appreciate that staves nearly collide with the lyrics
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Dienstag, 11. August 2009 02:04:28 schrieb Joe Neeman:
> On Tue, 2009-08-11 at 01:46 +0200, Reinhold Kainhofer wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > Am Dienstag, 11. August 2009 00:24:25 schrieb Joe Neeman:
> > > On Mo
2009/8/11 Joe Neeman :
> Is the footer too close to the lyrics? The default value (in the paper
> block) for bottom-system-spacing is
> bottom-system-spacing = #'((space . 1) (padding . 1) (min-distance . 0)
> (stretchability . 5))
>
> Could you try an increased padding value (maybe 2 or 3)?
3 is
GUB "make lilypond" fails with:
building package: freebsd-x86::guile
*** Stage: download (guile, freebsd-x86)
*** Stage: untar (guile, freebsd-x86)
*** Stage: patch (guile, freebsd-x86)
*** Stage: autoupdate (guile, freebsd-x86)
*** Stage: configure (guile, freebsd-x86)
*** Stage: compile (g
On Tue, 2009-08-11 at 01:54 +0200, Reinhold Kainhofer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Am Dienstag, 11. August 2009 01:10:33 schrieb Francisco Vila:
> > It looks much better now, except for the footer, when stretched.
>
> Yes, I also noticed this with my scores: It app
On Tue, 2009-08-11 at 01:46 +0200, Reinhold Kainhofer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Am Dienstag, 11. August 2009 00:24:25 schrieb Joe Neeman:
> > On Mon, 2009-08-10 at 13:03 +0200, Francisco Vila wrote:
> > > Hello. The example below shows that the new vertical engin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Dienstag, 11. August 2009 01:10:33 schrieb Francisco Vila:
> It looks much better now, except for the footer, when stretched.
Yes, I also noticed this with my scores: It appears that the space between the
last staff and the footer is fixed and wil
On Tue, 2009-08-11 at 01:10 +0200, Francisco Vila wrote:
> 2009/8/11 Joe Neeman :
> > On Mon, 2009-08-10 at 13:03 +0200, Francisco Vila wrote:
> >> Hello. The example below shows that the new vertical engine makes dead
> >> lyrics contexts to occup space. This did not happen before, IMO the
> >> ne
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Dienstag, 11. August 2009 00:24:25 schrieb Joe Neeman:
> On Mon, 2009-08-10 at 13:03 +0200, Francisco Vila wrote:
> > Hello. The example below shows that the new vertical engine makes dead
> > lyrics contexts to occup space. This did not happen befo
On 8/10/09 4:23 PM, "Trevor Daniels" wrote:
>
>
> Carl, you wrote Monday, August 10, 2009 10:58 PM
>> Can you express in words a rule that describes why
>>
>> a8 a a16[ a a8] a a a[ a16 a16]
>>
>> is better than
>>
>> a8[ a a16 a a8] a8[ a a a16 a]
>>
>
> I can do no better than quote R
On 8/10/09 5:25 PM, "Mark Polesky" wrote:
>
>
> I'm git-weary but still alive. Johannes spent *hours* debugging
> my problem, and eventually traced it to an undiscovered bug
> in gitk that only affects Microsoft Windows... So I think I'm
> back:
>
> $ git push --dry-run
> Everything up-to-d
Pushed to git.
Also, during this work I was able to improve the backslash handling; I think
all of the backslashes are now handled correctly.
Thanks,
Carl
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/l
I'm git-weary but still alive. Johannes spent *hours* debugging
my problem, and eventually traced it to an undiscovered bug
in gitk that only affects Microsoft Windows... So I think I'm
back:
$ git push --dry-run
Everything up-to-date
Now I need a break. But man, what a sport that guy is.
Hope
2009/8/11 Joe Neeman :
> On Mon, 2009-08-10 at 13:03 +0200, Francisco Vila wrote:
>> Hello. The example below shows that the new vertical engine makes dead
>> lyrics contexts to occup space. This did not happen before, IMO the
>> new lyrics should (IF it has enough room) to align with the previous
2009/8/10 Neil Puttock :
> Heheh, I'm hoping it won't come to that if I can get the existing test
> to work properly (I'm hopeful making the name longer will work).
Well this is rather puzzling: if I fix the bug, `make check' shows the
correction with a distance of 1.00 (even without changing
OK, I've found a setting that works *pretty well*, with one bad case:
\relative c'' {
\overrideBeamSettings #'Score #'(4 . 4) #'end
#'((* . (1 1 1 1))
((1 . 8) . (4 4)))
a8 a a a a a a a | % OK
\break
a16 a a8 a a
a a16 a a8 a | % OK now, was wrong, should be ...
a16[ a a8] a a
a[
On Mon, 2009-08-10 at 13:03 +0200, Francisco Vila wrote:
> Hello. The example below shows that the new vertical engine makes dead
> lyrics contexts to occup space. This did not happen before, IMO the
> new lyrics should (IF it has enough room) to align with the previous
> one.
Did this work before
Carl, you wrote Monday, August 10, 2009 10:58 PM
On 8/10/09 9:14 AM, "Trevor Daniels"
wrote:
With all Carl's mods applied just the expected two
inconsistencies
remain:
\relative c'' {
a8 a a16 a a8 a a a a16 a | % wrong, should be ...
a8 a a16[ a a8] a a a[ a16 a] |
a32 a a16 a a
On 8/10/09 9:14 AM, "Trevor Daniels" wrote:
>
>
> Trevor Daniels wrote Monday, August 10, 2009 8:49 AM
>>
>> Neil Puttock wrote Monday, August 10, 2009 12:31 AM
>>
>> 2009/8/10 Patrick McCarty :
>>
>>> I wonder why we are seeing different beaming patterns? I think
>>> all of
>>> your manu
2009/8/10 Francisco Vila :
> Hello. The example below shows that the new vertical engine makes dead
> lyrics contexts to occup space. This did not happen before, IMO the
> new lyrics should (IF it has enough room) to align with the previous
> one.
I've found that ragged-last-bottom could trigger t
On Mon, 2009-08-10 at 14:23 -0700, Patrick McCarty wrote:
> On Mon, Aug 10, 2009 at 8:11 AM, Joe Neeman wrote:
> > On Thu, 2009-08-06 at 10:53 -0700, Patrick McCarty wrote:
> >> On Thu, Aug 06, 2009 at 06:22:05PM +0200, John Mandereau wrote:
> >> > Le mercredi 05 août 2009 à 21:03 -0700, Patrick Mc
2009/8/10 Reinhold Kainhofer :
> ... and added a new regression test for this bug, right? ;-)
Heheh, I'm hoping it won't come to that if I can get the existing test
to work properly (I'm hopeful making the name longer will work).
Regards,
Neil
___
li
On Mon, Aug 10, 2009 at 8:11 AM, Joe Neeman wrote:
> On Thu, 2009-08-06 at 10:53 -0700, Patrick McCarty wrote:
>> 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
On Mon, Aug 10, 2009 at 5:57 PM, Mark Polesky wrote:
>> > I've always wished those were in English.
>>
>> Well, it isn't. I think this is a good thing. Not everything in the
>> world should be US-centric.
>
> I wasn't meaning to sound US-centric; I'm more concerned with
> wasting developers' time
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Montag, 10. August 2009 22:56:09 schrieb Neil Puttock:
> 2009/8/10 Reinhold Kainhofer :
> > Since the patch b8a1b9b174a3b68f05bb3e08fb5f754649b92574, short
> > instrument names for harakiried staves are still printed (above each
> > other, at the to
Werner LEMBERG wrote:
> > I've always wished those were in English.
>
> Well, it isn't. I think this is a good thing. Not everything in the
> world should be US-centric.
I wasn't meaning to sound US-centric; I'm more concerned with
wasting developers' time with hard-to-read code.
- Mark
2009/8/10 Reinhold Kainhofer :
> Since the patch b8a1b9b174a3b68f05bb3e08fb5f754649b92574, short instrument
> names for harakiried staves are still printed (above each other, at the top of
> the system).
Oh dear, that's not good. :)
It looks like I should have paid more attention to
`instrument-n
>
>> feta-eindelijk
>> feta-toevallig
>> feta-arrow
>> feta-puntje
>> feta-bolletjes
>> feta-schrift
>> feta-banier
>> feta-klef
>> feta-timesig
>> feta-pendaal
>> feta-haak
>> feta-accordion
>
> I've always wished those were in English.
Since the patch b8a1b9b174a3b68f05bb3e08fb5f754649b92574, short instrument
names for harakiried staves are still printed (above each other, at the top of
the system).
Example attached.
Cheers,
Reinhold
--
--
Reinhold Kainhofer, re
Werner LEMBERG wrote:
> feta-eindelijk
> feta-toevallig
> feta-arrow
> feta-puntje
> feta-bolletjes
> feta-schrift
> feta-banier
> feta-klef
> feta-timesig
> feta-pendaal
> feta-haak
> feta-accordion
I've always wished those were in Eng
Hi,
On Mon, 10 Aug 2009, Johannes Schindelin wrote:
> On Mon, 10 Aug 2009, Graham Percival wrote:
>
> > On Mon, Aug 10, 2009 at 10:34:11AM +0200, Johannes Schindelin wrote:
> > > On Mon, 10 Aug 2009, Graham Percival wrote:
> > >
> > > > We've lost 50% of potential contributors to the website be
Trevor Daniels wrote Monday, August 10, 2009 8:49 AM
Neil Puttock wrote Monday, August 10, 2009 12:31 AM
2009/8/10 Patrick McCarty :
I wonder why we are seeing different beaming patterns? I think
all of
your manually-beamed patterns are correct though.
Trevor's using the MinGW build I pos
On Thu, 2009-08-06 at 10:53 -0700, Patrick McCarty wrote:
> 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 earl
(sorry for the duplicate message, the first one bounced)
My 2 cents...
1) The 1891 Breitkopf & Härtel edition of Brahms' Piano Trio
Op.8 (1889 version) has the smaller staves exactly 2/3
the height of the larger staves. Click "Complete score":
http://imslp.org/wiki/Piano_Trio_No.1,_Op
Op donderdag 30-07-2009 om 20:23 uur [tijdzone -0700], schreef Graham
Percival:
Hi Graham,
> Whenever you get a chance, could you take a look at this? I
> cleaned out the GUB dir (rm -rf *; git reset --hard origin) and
> now it can't download guile.
>
> This is the console message; I could send
> if you can explain me what should I do, I would try to make it.
OK. However, it seems to be more complicated than thougth at a first
glance. Anyway, here a rough outline how it could be done.
1. Metafont is called for those fonts:
feta11.mf, feta13.mf, ...,
feta-braces-a.mf, feta-
On Mon, 2009-08-10 at 12:27 +0200, Werner LEMBERG wrote:
> > The overlap between "Ecce panis" and "Allegro" is due to a bug (that
> > you and Werner have already found) regarding rehearsal marks not
> > being counted in the spacing problem.
>
> You haven't fixed this, right?
I have now :)
___
On 10/08/2009 10:52, John Mandereau wrote:
Le lundi 10 août 2009 à 00:36 +0100, Ian Hulin a écrit :
So providing we could stitch this into the lilypond parsing, you could get
\afterGrace #(5.16) {c'1} {d16[ e16]) ;or
\afterGrace {c1} {d16[ e16]} ; or even
\afterGrace #:fraction #(5.16} #ma
Hi,
On Mon, 10 Aug 2009, Graham Percival wrote:
> On Mon, Aug 10, 2009 at 10:34:11AM +0200, Johannes Schindelin wrote:
> > On Mon, 10 Aug 2009, Graham Percival wrote:
> >
> > > We've lost 50% of potential contributors to the website because of
> > > git.
> >
> > Fair enough. Maybe it is time to
2009/8/10 Graham Percival :
> On Mon, Aug 10, 2009 at 10:50:09AM +0200, John Mandereau wrote:
>> Le lundi 10 août 2009 à 01:18 -0700, Graham Percival a écrit :
>> > We've lost 50% of potential contributors to the website because of
>> > git.
>>
>> And we've lost the same percentage of potential Fre
Hello. The example below shows that the new vertical engine makes dead
lyrics contexts to occup space. This did not happen before, IMO the
new lyrics should (IF it has enough room) to align with the previous
one.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org
www.csmbadajoz.com
dead-lyrics-
Hi Werner,
if you can explain me what should I do, I would try to make it.
--
Marek Klein
http://gregoriana.sk
2009/8/10 Werner LEMBERG
>
> > I'll add a bug tracker item which suggests to split the Metafont
> > output into even smaller units, say, 16 glyphs per subfont, to
> > circumvent the p
> The overlap between "Ecce panis" and "Allegro" is due to a bug (that
> you and Werner have already found) regarding rehearsal marks not
> being counted in the spacing problem.
You haven't fixed this, right?
Werner
___
lilypond-devel mailing lis
Le lundi 10 août 2009 à 00:36 +0100, Ian Hulin a écrit :
> So providing we could stitch this into the lilypond parsing, you could get
> \afterGrace #(5.16) {c'1} {d16[ e16]) ;or
> \afterGrace {c1} {d16[ e16]} ; or even
>
> \afterGrace #:fraction #(5.16} #main: {c1} #grace {d16[ e 16]} ; and
> \af
On Mon, 2009-08-10 at 11:00 +0200, Reinhold Kainhofer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Yet another small issue with the vertical layout: It seems that where one
> piece ends and another one begins, the piece title is completely ignored for
> spacing. Even worse, Somet
On 10/08/2009 09:03, John Mandereau wrote:
Le dimanche 09 août 2009 à 16:43 -0600, Carl Sorensen a écrit :
How about \afterGraceSpacing?
That's OK for me; unless there is any objection on the command name,
I'll add the function with this name.
Best,
John
I still think it's
> I'll add a bug tracker item which suggests to split the Metafont
> output into even smaller units, say, 16 glyphs per subfont, to
> circumvent the problem. It's basically a logistic change which can
> be done even with minimal knowledge of the Metafont language --
> perhaps this is something fo
On Mon, Aug 10, 2009 at 10:50:09AM +0200, John Mandereau wrote:
> Le lundi 10 août 2009 à 01:18 -0700, Graham Percival a écrit :
> > We've lost 50% of potential contributors to the website because of
> > git.
>
> And we've lost the same percentage of potential French translators; I'm
> sorry to re
Graham Percival wrote Monday, August 10, 2009 9:18 AM
On Mon, Aug 10, 2009 at 08:45:22AM +0100, Trevor Daniels wrote:
Graham Percival wrote Monday, August 10, 2009 12:48 AM
I maoing hate git.
Git is fine; the complexity comes from the
baroque structures in LilyPond. Let's be
thankful Git
Le lundi 10 août 2009 à 01:18 -0700, Graham Percival a écrit :
> We've lost 50% of potential contributors to the website because of
> git.
And we've lost the same percentage of potential French translators; I'm
sorry to remark that most of them who didn't spend the effort to master
Git and stopped
On Mon, Aug 10, 2009 at 10:34:11AM +0200, Johannes Schindelin wrote:
> On Mon, 10 Aug 2009, Graham Percival wrote:
>
> > We've lost 50% of potential contributors to the website because of
> > git.
>
> Fair enough. Maybe it is time to suggest an easy interface to Git? You
> could even write a ve
Hi,
On Mon, 10 Aug 2009, Graham Percival wrote:
> On Mon, Aug 10, 2009 at 08:45:22AM +0100, Trevor Daniels wrote:
> >
> > Graham Percival wrote Monday, August 10, 2009 12:48 AM
> >> I maoing hate git.
> >
> > Git is fine; the complexity comes from the
> > baroque structures in LilyPond. Let's be
Is there any possibility to retrieve informations about slurs being
adjacent from a callback?
For example
\displayMusic { c4 ( c ) ( c ) c }
shows
[...]
(make-music
'EventChord
'elements
(list (make-music
'NoteEvent
'duration
>> configure.in has been modified! Please rerun `autogen.sh',
>> then `make all' again.
>
> Done.
Thanks.
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
> One has to keep in mind that Metafont does not permit more than 16
> different heights per font (something like that, I don't remember
> the exact details).
Yes, this problem already bites us. I'll add a bug tracker item which
suggests to split the Metafont output into even smaller units, say,
Le lundi 10 août 2009 à 06:40 +0200, Werner LEMBERG a écrit :
> It would be sufficient for me if `make all' simply aborts with a
> message
>
> configure.in has been modified! Please rerun `autogen.sh',
> then `make all' again.
>
> or something like that.
Done. INSTALL.txt and the Contribut
On Mon, Aug 10, 2009 at 08:45:22AM +0100, Trevor Daniels wrote:
>
> Graham Percival wrote Monday, August 10, 2009 12:48 AM
>> I maoing hate git.
>
> Git is fine; the complexity comes from the
> baroque structures in LilyPond. Let's be
> thankful Git has tools to cope :)
Oh? Didn't you comment th
Le dimanche 09 août 2009 à 16:43 -0600, Carl Sorensen a écrit :
> How about \afterGraceSpacing ?
That's OK for me; unless there is any objection on the command name,
I'll add the function with this name.
Best,
John
signature.asc
Description: Ceci est une partie de message numériquement signée
Le lundi 10 août 2009 à 00:56 -0700, Graham Percival a écrit :
> After spending a while reading and re-reading your addition to the
> CG git stuff, it sounds like this only applies to translated docs
> -- i.e. as long as I don't mess with anything in de/ es/ fr/ etc/,
> it's safe to "git pull -r".
Le dimanche 09 août 2009 à 16:48 -0700, Graham Percival a écrit :
> Mao. So that means that we don't want to add
> git config --global branch.autosetuprebase always
> to the git setup, and we still have to tell people to do
> git pull -r
> instead of
> git pull
> ?
You didn't read the end o
On Sun, Aug 09, 2009 at 04:48:45PM -0700, Graham Percival wrote:
> On Sun, Aug 09, 2009 at 11:45:05PM +0200, John Mandereau wrote:
> > Le samedi 08 août 2009 à 13:55 -0600, Carl Sorensen a écrit :
> > > As a practical matter, -r first applies the changes that were made on
> > > origin
> > > (sinc
Neil Puttock wrote Monday, August 10, 2009 12:31 AM
2009/8/10 Patrick McCarty :
I wonder why we are seeing different beaming patterns? I think all
of
your manually-beamed patterns are correct though.
Trevor's using the MinGW build I posted a few days ago, so it's
missing Carl's last change
Graham Percival wrote Monday, August 10, 2009 12:48 AM
On Sun, Aug 09, 2009 at 11:45:05PM +0200, John Mandereau wrote:
Le samedi 08 août 2009 à 13:55 -0600, Carl Sorensen a écrit :
> As a practical matter, -r first applies the changes that were
> made on origin
> (since your branch was check
Werner LEMBERG writes:
>> Are there any guidelines LilyPond adheres to for creating bounding
>> boxes?
>
> No.
>
>> For example, when I adjusted the bbox for the \eyeglasses markup
>> command, I _underestimated_ the bbox. Should I have slightly
>> _overestimated_ instead? Attached is a PNG disp
75 matches
Mail list logo
