2008/10/8 Valentin Villenave [EMAIL PROTECTED]:
(sending again because the attachments were too heavy)
Hi Neil,
before pushing it, could you have a look at the attached patch that
replaces PianoStaff with GrandStaff? I doubt it would change anything
to your work on nested contexts, but
Good day, lilypond-devs!
My name is Nils and I'm the website-maintainer for Denemo.
Denemo is a music notation program for Linux and Windows (and possibly MacOS)
that lets you rapidly enter notation for typesetting via the LilyPond music
engraver.
It is an official GNU project and the website
Valentin Villenave [EMAIL PROTECTED] writes:
2008/10/8 Valentin Villenave [EMAIL PROTECTED]:
I won't push it myself because it's still a scary move (at least to me).
And by the way: I haven't added any NEWS item since I'm not sure this
will get merged, but it ever does, we /ABSOLUTELY/ need
On Wed, 8 Oct 2008 12:48:12 +0200
Valentin Villenave [EMAIL PROTECTED] wrote:
2008/10/8 Valentin Villenave [EMAIL PROTECTED]:
I won't push it myself because it's still a scary move (at least to
me).
And by the way: I haven't added any NEWS item since I'm not sure this
will get merged,
Valentin
This has quite a potential to muck things up in the docs, but if we want to
make the change this is what will need to be done.
The global change which you have done does not work if both PianoStaff and
GrandStaff appear in the same sentence or even paragraph. One example I
spotted
2008/10/8 Valentin Villenave [EMAIL PROTECTED]:
I won't push it myself because it's still a scary move (at least to me).
And by the way: I haven't added any NEWS item since I'm not sure this
will get merged, but it ever does, we /ABSOLUTELY/ need to post it on
the mailing list, on the website,
2008/10/8 Graham Percival [EMAIL PROTECTED]:
http://lilypond.org/doc/v2.11/Documentation/user/lilypond-program/Generating-LilyPond-files
Yes. Denemo is listed there but the link points to the old Sourceforge
page and not to denemo.org.
-Risto
___
it should also be mentioned on this page:
http://lilypond.org/web/about/faq
till
Original-Nachricht
Datum: Wed, 8 Oct 2008 16:35:57 +0300
Von: Risto Vääräniemi [EMAIL PROTECTED]
An: Graham Percival [EMAIL PROTECTED]
CC: Nils Gey [EMAIL PROTECTED], lilypond-devel@gnu.org
2008/10/8 Trevor Daniels [EMAIL PROTECTED]:
This has quite a potential to muck things up in the docs, but if we want to
make the change this is what will need to be done.
Well, I have done everything I could to fix things (even in the
translated docs).
The global change which you have done
http://lilypond.org/doc/v2.11/Documentation/user/lilypond-program/Generating-LilyPond-files
The link should be fixed to `www.denemo.org'.
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
2008/10/8 Nils Gey [EMAIL PROTECTED]:
It is an official GNU project and the website can be found here:
http://www.denemo.org
Well, it's nice to see you guys are alive! I only knew your old
website, and I've subscribed to your mailing lists for a few years but
from where I was standing the
On the Sponsoring - See what you can do page,
( http://lilypond.org/web/sponsor/options )
Clicking on the PayPal payments link sends the user to
a webpage with a form to fill out in Dutch. There's no
easy way to change the language. Maybe it's a small
thing, but I don't think so. I think
I should take down that page. I am gainfully employed, so I don't
need any donations.
On Wed, Oct 8, 2008 at 11:35 AM, Mark Polesky [EMAIL PROTECTED] wrote:
On the Sponsoring - See what you can do page,
( http://lilypond.org/web/sponsor/options )
Clicking on the PayPal payments link sends
Valentin, you wrote Wednesday, October 08, 2008 2:52 PM
2008/10/8 Trevor Daniels [EMAIL PROTECTED]:
This has quite a potential to muck things up in the docs, but if we want
to
make the change this is what will need to be done.
Well, I have done everything I could to fix things (even in the
2008/10/8 Graham Percival [EMAIL PROTECTED]:
Don't be silly. This is just one more syntax change -- it's even
covered by convert-ly!
You mean, this weird CLI-thingy 80% of our Windows users have never used? :-)
If anything, having such an obvious breakage for 2.12 is a *good*
thing, since
On Wed, 2008-10-08 at 00:21 -0700, Mark Polesky wrote:
Hey everyone,
I agree with Valentin. I think it makes sense to
just get rid of PianoStaff. Semantically, it's
redundant; and removing an entire context would
simplify the learning process for newbies, among
other things.
Is keeping
Greetings,
(some day I *may* figure out how to use the online patch reviewer
thingy; I can't understand why it keeps asking me for a SVN repository
when we're using an external git repo)
Here's a patch to music-functions.scm in order to add the
showFirstLength property that many LilyPonders
2008/10/6 Trevor Daniels [EMAIL PROTECTED]:
So I definitely prefer \larger.
Here is a patch that removes \bigger.
Okay to push? If it is, I'll add a NEWS item.
Cheers,
Valentin
0001-Removed-bigger-markup-command-use-larger-instead.patch
Description: Binary data
Hello, John and translators,
When running make translation-status I obtain 'bad object' warnings on
these files:
fr/user/macros.itexi
de/user/macros.itexi
fr/user/lilypond.tely
This makes the status page not properly updateable by me. As I usually
work only on the lilypond/translation branch, I
2008/10/8 Joe Neeman [EMAIL PROTECTED]:
Is keeping one extra context definition around such a learning barrier?
Certainly not; it's just a matter of consistency in LilyPond syntax.
PianoStaff could be useful in the future: if I ever get around to fixing
the vertical spacing (ok, let's be
Francisco Vila schrieb:
Hello, John and translators,
When running make translation-status I obtain 'bad object' warnings on
these files:
fr/user/macros.itexi
de/user/macros.itexi
fr/user/lilypond.tely
ok, so this is the thing that cases the bad objects? I will update my
macros since they
Hello,
I am interested in the understanding how \include ... is
implemented, since I want to figure out how to permit relative
includes and wildcards in pathnames.
My first attempts lead me to believe that this is implemented through
the lexer. Is this correct? Files such as lily/lexer.ll, and
2008/10/4, Han-Wen Nienhuys [EMAIL PROTECTED]:
10.3 PPC
As far as I can see, it doesn't work on 10.3.9 (neither GUI or CLI).
Cheers,
Valentin
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Dear LilyPond developers,
I hope it's not too late to suggest the patch attached to this
e-mail... If at all possible, I would like to see the following
added to the header block (ie, additional fields for titles):
number - The score number, if part of a book, to be printed
Dear LilyPond developers,
I don't know how much of a pain this would be to add (especially at
this stage of development), but would it be possible to include
ranges in tempo definitions? I've done a quick search of the
mailing list, but cannot see that anyone else has suggested this.
A lot of
Hi John,
On Wed, Oct 8, 2008 at 4:25 PM, John Zaitseff [EMAIL PROTECTED] wrote:
Dear LilyPond developers,
I don't know how much of a pain this would be to add (especially at
this stage of development), but would it be possible to include
ranges in tempo definitions? I've done a quick search
Dear Patrick,
John Zaitseff wrote:
[...] A lot of music I am transcribing has tempo annotations of
the form dotted quarter note = 92-96. I would like to enter
something like the following in LilyPond:
\tempo 4. = 92-96
With the latest development release (2.11.61), you can do
Hi John,
On Wed, Oct 8, 2008 at 4:52 PM, John Zaitseff [EMAIL PROTECTED] wrote:
Yes, I did read that in the NEWS file (that is, text annotations for
\tempo). Still, not as nice syntactically as my suggestion above!
Besides, I'd still like to do something like:
\tempo Медленно 4. = 92-96
Patrick McCarty wrote:
[...]
Also, since the tempo of MIDI output is set with this command, we
would need to decide which of the two indications to choose (or
take an average).
I've taken the average up until now in my own Scheme function: I
think that makes the most sense.
I'll look into
On Wed, Oct 8, 2008 at 6:14 PM, Patrick McCarty [EMAIL PROTECTED] wrote:
Hello,
I am interested in the understanding how \include ... is
implemented, since I want to figure out how to permit relative
includes and wildcards in pathnames.
My first attempts lead me to believe that this is
On Wed, Oct 8, 2008 at 8:52 PM, John Zaitseff [EMAIL PROTECTED] wrote:
Besides, I'd still like to do something like:
\tempo Медленно 4. = 92-96
Is there any interest in a patch that will allow me to do this? I
To do stuff like this, you need to hack special support in the parser,
which I
Han-Wen Nienhuys wrote:
John Zaitseff wrote:
Besides, I'd still like to do something like:
\tempo Медленно 4. = 92-96
Is there any interest in a patch that will allow me to do this?
To do stuff like this, you need to hack special support in the
parser, which I think is a bad idea.
I´m not saying it´s too difficult; I´m saying I won´t apply your patch :-)
Look for tempo_event in parser.yy
On Wed, Oct 8, 2008 at 11:07 PM, John Zaitseff [EMAIL PROTECTED] wrote:
Han-Wen Nienhuys wrote:
John Zaitseff wrote:
Besides, I'd still like to do something like:
\tempo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Donnerstag, 9. Oktober 2008 schrieb [EMAIL PROTECTED]:
Reinhold No, he suggests we ignore all lines starting with @c or
Reinhold @comment and don't process them at all in our buildscripts.
Watch out for lines beginning @code
Of course, we'd
Dear Han-Wen,
John Zaitseff wrote:
I´m not saying it´s too difficult; I´m saying I won´t apply
your patch :-)
Not trying to be difficult, but given that this idea (of tempo
ranges) seems to me to be a reasonable one, is there any reason
why not? I realise that it is a syntax
/[EMAIL PROTECTED]/
Watch out for lines beginning @code
Yes, this should have been
/[EMAIL PROTECTED] \t]/
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
36 matches
Mail list logo
