[EMAIL PROTECTED] writes:
> I've managed to get the MetronomeMark to separate the stem from the
> notehead:
> |
> |
> |
>
> O
>
> In addition, there's a huge space underneath the first staff line. Is
> the MetronomeMark #'padding property being applied underneath
> the staff line? (instea
[EMAIL PROTECTED] writes:
>
> Hi,
>
> I'm wandering if I can change the definition of "program_name" in the
> files in scripts/*.py from for instance:
>
> program_name = 'midi2ly'
>
> to
>
> program_name = sys.argv[0]
>
> It will not change the behavior of the programs whatsoever, but it'll
>
[EMAIL PROTECTED] writes:
> This example fails to build, but AFAIK the actual pipeSymbol
> stuff is fine. If I delete everything before the pipeSymbol (including
> the { ), it works. But if I leave anything in front of it like #(set!
> or
> \paper {}, it fails. I can't figure out how to fix thi
[EMAIL PROTECTED] writes:
>
> On 3-Sep-04, at 12:12 PM, Han-Wen Nienhuys wrote:
>
> > [EMAIL PROTECTED] writes:
> >> Judging from scm/script/scm, LilyPond appears to try to place the
> >> accent underneath the slur. My recollection is that the accent (the
> >> ->
> >> kind) goes above the slur.
[EMAIL PROTECTED] writes:
> @end lilypond
>
> That's correct according to the style guidelines at the beginning of
> Documentation/user/lilypond.tely, but I think it would look better with
> a period after "notes". Can I change the manual style to fit that?
We changed the manual from having pu
[EMAIL PROTECTED] writes:
> Some notation elements have a little "bugs" section, like this one for
> micro tones:
> ---
> There are no generally accepted standards for denoting three quarter
> flats, so LilyPond's symbol does not conform to any standard.
> ---
>
> IMO this isn't really a bug. A
[EMAIL PROTECTED] writes:
> > ...
> > [EMAIL PROTECTED] FIXME: Unknown clef type `neomensural_c2'
> > +
> > ...
>
> Arrrgh! This should probably be "neo_mensural_c2" according to
> scm/clef.scm:
>
> ("neo_mensural_c2" . ("clefs-neo_mensural_c" -2 0))
>
> Or, rather, scm/clef.scm should sa
[EMAIL PROTECTED] writes:
> The Oxford English Grammar (1996) by Sidney Greenbaum suggests to use generic
> singulars they, them, their:
I second this.
> you would write
>
> "If you want to do foo, you should write bar in your LilyPond score".
>
IMO, it makes the text awkward, since almost eve
[EMAIL PROTECTED] writes:
> Hi guys, the examples in Documentation/user/notation.itely in the
> "Ancient notation" section need a lot of work. Ancient notation is
> another weakness of mine; I have no idea what's changed between when
> these examples were written and current LilyPond. Could so
On Wednesday 08 September 2004 14.05, Nicolas Sceaux wrote:
> Erik Sandberg <[EMAIL PROTECTED]> writes:
>
> hm.
> Here is a first trial.
> After the music has been parsed, there is no distinction between *2/3
> and *4/6, so
>
> 3 6
> --- is ok whereas === is n
This example fails to build, but AFAIK the actual pipeSymbol
stuff is fine. If I delete everything before the pipeSymbol (including
the { ), it works. But if I leave anything in front of it like #(set!
or
\paper {}, it fails. I can't figure out how to fix this -- or rather,
I can
figure out ho
On 3-Sep-04, at 12:12 PM, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
Judging from scm/script/scm, LilyPond appears to try to place the
accent underneath the slur. My recollection is that the accent (the
->
kind) goes above the slur. Comments?
Yes: please check in multiple reputable scores
% time signatures don't do numbers for 4/4 and 2/2
\version "2.3.14"
{
\time 4/4 c'1
\time 2/2 c'1
\override TimeSignature #'style = #'()
\time 4/4 c'1
\time 2/2 c'1
\override TimeSignature #'style = #'numbered
\time 4/4 c'1
\time 2/2 c'1
}
___
lilypond-
Hi, Graham!
> ...
> programming error: Grob `NoteHead' has no interface for property
> `delta-pitch'
> Continuing; crossing fingers
> ...
These errors are annoying, but harmless. Ancient notation uses a couple
of internal variables that need to survive different stages of compiling.
It curr
On Wed, 8 Sep 2004, Graham Percival wrote:
> ...
> [EMAIL PROTECTED] FIXME: Unknown clef type `neomensural_c2'
> +
> ...
Arrrgh! This should probably be "neo_mensural_c2" according to
scm/clef.scm:
("neo_mensural_c2" . ("clefs-neo_mensural_c" -2 0))
Or, rather, scm/clef.scm should say:
Hi guys, the examples in Documentation/user/notation.itely in the
"Ancient notation" section need a lot of work. Ancient notation is
another weakness of mine; I have no idea what's changed between when
these examples were written and current LilyPond. Could somebody with
a clue have a look at
Hi,
On Wed, 8 Sep 2004, Heikki Johannes Junes wrote:
> But, why not write directly to the LilyPond user ("you") and not to the
> person who reads about a composer/user who uses LilyPond:
>
> [...]
I would prefer this, because then even us hermaphrodites are not offended,
and even if some aliens
Hi,
Yeh, I object, but only 'cause I'm a bloke! ;)
More seriously, I've not seen many pronoun references, and I think that
it is generally better to avoid them altogether if at all possible with
direct command-like phrases.
I must admit to some surprise that there is such a standard that
determine
On Tue, 07 Sep 2004 18:34:51 -0400 Carl Sorensen <[EMAIL PROTECTED]> wrote:
> On Mon, 2004-09-06 at 20:21, Graham Percival wrote:
>
> > - Current English academic[1] writing style is to use the feminine
> > pronoun as a gender-neutral pronoun. "A composer might want to do
> foo,
> > so she sho
Erik Sandberg <[EMAIL PROTECTED]> writes:
> On Friday 03 September 2004 23.41, Nicolas Sceaux wrote:
>> what I've started to look at is something like that:
>>
>> \tupletify { c8 c8*2/3 c c c8 c8*4/5 c16*4/5 c c4*2/6}
>> ==>
>> { c8 \tuplet 2/3 { c8 c c } c8 \tuplet 4/5 { c8 c16 c } \tuplet 2/6
> - I've arbitrarily picked the number 3 for spaces when indenting.
I prefer two spaces for indentation, at least for examples in the
documentation. Expect that lilypond.info is displayed on terminal
windows which have a width of 80 characters only; the less indentation
the better are the chances
21 matches
Mail list logo
