Hello,
I'm working on gregorian chant reprensentation for a project student in
a graduate ingeneering school in France, and I have had a lot of
discussion with a monk on it. My aim is to improve gregorian chant
representation in free softwares for monk to use it.
I read the latest version of the
As far as I can tell, page and line penalties are used _only_ for forbidding
and forcing page breaks. Is there much chance they will ever be used for
anything else? If not, they could be replaced by booleans - this would make
the breaking algorithms a bit easier.
Also, there seems to be some
Alle 09:48, mercoledì 22 marzo 2006, Marco Gusy ha scritto:
(ignoring ties)
I meant ignoring slurs, ties are ok
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Hello!
you can help promote lilypond by spreading the release announcement.
* The HTML version is at
http://lilypond.org/web/announce-v2.8.html
* The text version is at
http://cvs.savannah.gnu.org/viewcvs/*checkout*/workbook/press.txt?root=lilypond
note that the text is UTF-8 ; take
I don't really understand what you mean. If you don't want
any connection between the lyrics and the notes, just skip
\lyricsto and specify the duration of each syllable. If you want
information from the lyrics to affect the notes, then you would still
have to specify the duration of each
Marco Gusy wrote:
I just want to obtain the correct beaming behaviour in vocal music (like in
the sample image i sent) without getting mad beaming and melismaing by
hand.
The rule should simply be Break beam on every new syllable.
Since lilypond implemented the auto-melisma using dashes in
Pedro Kröger wrote:
I get a 404 not found error when make download tries to fetch
http://lilypond.org/~hanwen/osx-lilypad-0.2.tar.gz. this happens with
darcs up to this patch:
Thu Mar 23 11:08:27 BRT 2006 [EMAIL PROTECTED]
* document why NSIS_CONFIG_LOG is switched off.
thanks. fixed.
Lilypond-book doesn't seem to understand the include structure very
well. That is, it's using the included files, but doesn't seem to
know that it needs to rebuild the snippets if you change an included
file. I'm working around this by removing all the snippets when I
change anything, but
Hi,
I've just upgraded to version 2.8.0-5 on Windows.
Firstly, it seems to be slower than the 2.7.x series, about the same speed
as the old 2.6.x series.
Secondly, could a compressed archive of the files installed by the installer
be added as a target of the GUB? Alternatively, an option
It looks like my email client messed up the lines on the patches I
sent in. I'm trying again with a different one. Hope this works. I
also attached the patches, just in case. Note: I'm pretty sure these
changes won't break CID fonts, but it'd be a good idea to double check
that.
David Feuer
Pedro Kröger wrote:
GUB asks for a darwin7-sdk-0.4.tar.gz file. where can I download it? I
google for it but I found nothing useful.
you should get it automatically if you do make download
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
--
Pedro Kröger wrote:
The command:
python gub-builder.py -p local build flex
fails because flex-2.5.4a.tar.gz unpacks to flex-2.5.4 (without the a)
and gub-builder is trying to do:
tar -C /home/kroger/devel/gub/target/local/src -zcf
/home/kroger/devel/gub/uploads/local/flex-2.5.4a-src.local.gub
From: Mats Bengtsson [EMAIL PROTECTED]
To: Graham Percival [EMAIL PROTECTED]
Cc: Stephen [EMAIL PROTECTED]; lily-devel
lilypond-devel@gnu.org
Sent: Monday, March 20, 2006 4:09 PM
Graham Percival wrote:
On 20-Mar-06, at 8:18 AM, Stephen wrote:
I don't think Rehearsal Marks are as
I am personally extremely grateful for all of the great changes in
LilyPond's tie formatting code during these last many months: both the
improvements in the default tie formatting and especially the new
ability to override the default formatting with manual adjustments.
I have thought of an
I would like to now if it is possible to type the change of fingers not only
using the two numbers(i.e 5-1) but also adding a little slur above the two
fingers. I found lots of score with the little slurs between fingers without
dash
Thanks
Gianni Bertoni
I made some changes to the Postscript backend, making the output more
readable (especially for text), around 10% shorter, and, at least in theory,
also faster to interpret. These changes are just a start, but I hope they
help. I'd like to know if it might be possible to make the backend work
On Tue, 21 Mar 2006, Elie Roux wrote:
Hello,
I'm working on gregorian chant reprensentation for a project student in
a graduate ingeneering school in France, and I have had a lot of
discussion with a monk on it. My aim is to improve gregorian chant
representation in free softwares for monk to
Yes, this looks better. Now, that we have barAlways = ##t, we can also
drop these dMinima etc. definitions. I also set the \version to 2.8.0
(just looks nicer in the source). Result is attached. I think it's still
not perfect, but much better than what is currently in the docu.
Graham,
Good news: As of yesterday, there is an ebuild for 2.8.0 in Gentoo
portage. Previously, the latest versions were 2.4.2 and 2.5.2. It's
good not to have to roll my own ebuilds anymore.
All Gentoo Lilypond users who update their systems regularly will see
this if they have the unstable flag
Hi,
You may want to apply the attached patch. It updates
linux_kernel_headers to 2.6.13+0rc3-2.1. I couldn't find
2.6.13+0rc3-2 from any mirror.
Pedro
New patches:
[updated version of Linux_kernel_headers
Pedro Kröger [EMAIL PROTECTED]**20060328000836] {
hunk ./lib/arm.py 18
-
It seems this issue doesn't bother anyone else? In any case, now
that 2.8 is out there, I thought I'd start pushing this point again.
I attach a patch that gives the behaviour that I think is correct.
I also attach 2 examples of the differences between the existing and
the proposed
On Tue, 28 Mar 2006 03:43, Werner LEMBERG wrote:
It seems this issue doesn't bother anyone else? In any case, now
that 2.8 is out there, I thought I'd start pushing this point again.
I attach a patch that gives the behaviour that I think is correct.
I also attach 2 examples of the
Shouldn't all tremolo lines be at the same angle (usually about 30
degrees)?
Sorry, I am new to the list, and am not sure where this thread
started. But in standard notation, this is not what usual tremolo
markings look like.
Josh
On Mar 28, 2006, at 9:48 AM, Joe Neeman wrote:
On Tue,
I've tweaked it by adding a little more to the minimum length of the
stem. The Franck output is unchanged, I've attached the new
Tchaikovsky output.
Very nice!
Oh, and I remembered a ChangeLog entry this time :)
Please add it just to the mail and don't include it into the diff
directly.
Shouldn't all tremolo lines be at the same angle (usually about 30
degrees)?
AFAIK, this isn't true in the presence of beams. Can you provide a
counterexample (this is, a small scanned image)? In that case we have
to make it configurable.
Werner
On Tue, 28 Mar 2006 07:01, Joshua Parmenter wrote:
Shouldn't all tremolo lines be at the same angle (usually about 30
degrees)?
Sorry, I am new to the list, and am not sure where this thread
started. But in standard notation, this is not what usual tremolo
markings look like.
I started the
26 matches
Mail list logo
