lilyPondTool doesn't do this yet, but it's goal is definitely enabling that.
--- Original Message ---
From: Graham Percival [EMAIL PROTECTED]
To: fsarud [EMAIL PROTECTED]
Sent: 08/06/28/, 6:20:32
Subject: Re: Towards something like a helper to write in Lilypond
does) which at
2008/6/28 Bertalan Fodor [EMAIL PROTECTED]:
lilyPondTool doesn't do this yet, but it's goal is definitely enabling that.
Wilbert's LilyKDE also has a similar goal IIUC (not to mention my own
EasyLilyPond project, that aims to integrate these different modules
within a single platform). To me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Freitag, 20. Juni 2008 schrieb luis jure:
another question: i find your flags a bit small (and too slanted)
In your original images, the slant is somewhere betwen 40 and 45 degrees...
But I agree, that large slant does not look good. I prefer
Op zaterdag 28 juni 2008, schreef fsarud:
Some improvements I foresee are:
- some capability to clicking somewhere on the image and the cursor going
to the selected place (some like the PDF referenced files that Lilypond
already does)
With LilyKDE[1] (a Kate plugin for authoring LilyPond
Is there any way to specify the fontsize for a markup in absolute size? In
particular, the markup (title page for A4, defined in an in external include
file) should always use the same font size, irrespective of the global staff
size.
This way, I can define one nice title page and use that for
Hi Paul,
In fact I don't normally use a \global key change just \global
timing and dynamics.
Hmmm... unfortunately, that makes for (slightly) more work and
(slightly) less-maintainable code. However, it does give me an idea:
perhaps one could use \tag in the \global section to control
Am 27.06.2008 um 22:55 schrieb Kieren MacMillan:
Hi James,
The output has the cross staff beams horribly, horribly wrong.
I'm not sure exactly what you're looking for, but maybe the
following modified code will get you going in the right direction:
Well, I had a guess, and it came up
Le 28 juin 08 à 17:18, Reinhold Kainhofer a écrit :
Is there any way to specify the fontsize for a markup in absolute
size? In
particular, the markup (title page for A4, defined in an in external
include
file) should always use the same font size, irrespective of the
global staff
size.
Mats Bengtsson wrote:
In my
experience, it's fairly uncommon in printed music to have this kind of
different durations in the two alternatives, so I don't think that it's
common enough to deserve a specific example in the manual. You may want
to submit it to the LSR, though.
It's not
On Sat, Jun 28, 2008 at 9:50 AM, James E. Bailey [EMAIL PROTECTED] wrote:
Am 27.06.2008 um 22:55 schrieb Kieren MacMillan:
Hi James,
The output has the cross staff beams horribly, horribly wrong.
I'm not sure exactly what you're looking for, but maybe the following
modified code will get
Le 28 juin 08 à 18:11, Nicolas Sceaux a écrit :
Le 28 juin 08 à 17:18, Reinhold Kainhofer a écrit :
Is there any way to specify the fontsize for a markup in absolute
size? In
particular, the markup (title page for A4, defined in an in
external include
file) should always use the same font
Nicolas Sceaux wrote:
oops, baseline-skip and word-space should also be fixed absolutely, and
not based on the ones from props.
Do you mean like:
#(define-markup-command (abs-fontsize layout props size arg)
(number? markup?)
(let* ((ref-size (ly:output-def-lookup layout 'text-font-size 12))
In the new documentation, after looking carefully, i was not able to find the
section related to the symbol
||O||
a whole note, with two short vertical lines on both sides.
In section 1.2.1.1 there is the whole note with one short vertical lines on
both sides, but not 2.
Thanks.
--
View this
Am Samstag, 28. Juni 2008 schrieb Patrick Horgan:
Mats Bengtsson wrote:
In my experience, it's fairly uncommon in printed music to have this kind
of different durations in the two alternatives, so I don't think that it's
common enough to deserve a specific example in the manual. You may want
On Sat, 28 Jun 2008 11:26:46 -0400
Kieren MacMillan [EMAIL PROTECTED] wrote:
In any case, we should really -- as a community -- come up with a
set of best practices (or at least guidelines), since this is a
situation that is both common and somewhat complicated to handle in
Lilypond.
We
Is this a notehead for ancient music? You'll find it in NR
2.8.1.1 or NR appendix B.5.
Cheers,
- Graham
On Sat, 28 Jun 2008 14:43:32 -0700 (PDT)
sdfgsdhdshd [EMAIL PROTECTED] wrote:
In the new documentation, after looking carefully, i was not able to
find the section related to the symbol
Graham,
We *have* a set of best practices.
They're LM 5 Working on LilyPond projects.
Unless I'm missing something, there is no best practice on how to
(e.g.) efficiently handle instrument switching. There are, of course,
several references to the concept widely scattered throughout the
On Fri, Jun 27, 2008 at 3:19 PM, Kieren MacMillan
[EMAIL PROTECTED] wrote:
Hey all,
After thinking about it a bit, it seems to me that the current (*wicked
awesome*, BTW) skyline coding could come to the rescue here... =)
IMO, the ultimate algorithm for a piano-with-centered-dynamics
2008/6/29 Kieren MacMillan [EMAIL PROTECTED]:
We *have* a set of best practices.
They're LM 5 Working on LilyPond projects.
I wrote them two years ago, and AFAIK nobody has ever read them.
Not only have I read them too, but I think I translated them (or
contributed to the translation). A very
Hi,
I think this question is extreme a big challenge to you all, but is very
urgent for me.
I can't go to New England Conservatory, because I was forced by the two
unabled deans to learn the piano when entering my local conservatory. This
stopped me from learning composition, so I have no
This edition uses a very distinctive chord naming
system--functional chord name system. For example, the tonic major
triad is written as T, subtonic triad is S, and dominant is
D. Chords share two notes of both T and S or D and T are prefixed
by two function letters and then the
Hi Valentin,
Not only have I read them too
There you go, Graham: at least two people have read your best
practices docs! ;-)
I don't think the docs are incomplete, I think *we* are, as
LilyPond coders.
I'm afraid all of us are actually making history right here, right
now.
I think that I've sent a copy of my .ly file to everyone that requested
one. If I missed you let me know.
It's de Victoria's O Magnum Mysterium. The file generates choir,
individual parts, choir with piano reduction, and midi files for choir
and for each part.
Patrick
Is this a notehead for ancient music?
Not really.
You'll find it in NR 2.8.1.1 or NR appendix B.5.
He won't find it since we don't have a glyph for it. It's probably
best to submit a bug report, together with a high-resolution scan of
such a note head.
Werner
24 matches
Mail list logo
