On Thu, Apr 21, 2011 at 3:49 PM, Trevor Daniels wrote:
>
>
> One or two quibbles with the language on this page:
>>
>
> I'll fix the typos.
>
>
Thanks, Trevor! Someone must have clumsy typing ... oops!
___
bug-lilypond mailing list
bug-lilypond@gnu.org
This looks like a bug to me. My minimal example:
\version "2.13.16"
{
\set Staff.pedalSustainStyle = #'text
c''1\sustainOn
}
If the pedalSustainStyle is set to #'mixed or #'bracket then the
bracket indicates the sustain up at the end of the piece. With #'text
style there is no sustain up mark
On Mon, Dec 21, 2009 at 12:45 PM, Neil Puttock wrote:
> 2009/12/21 Sandy Nicholson :
>
>> In case it’s relevant, I’m running Mac OS X 10.6.2 (but I started trying
>> LilyPond when I was still on 10.5, I think). It seems to make no difference
>> what PDF viewer I use, so it’s unlikely that it’s a b
On Fri, Nov 27, 2009 at 2:29 PM, Graham Percival
wrote:
> After a bit of experimenting, I think this is the best way to view issues:
>
> http://code.google.com/p/lilypond/issues/list?mode=grid&y=Priority&x=Type&cells=ids
>
> Neat, huh? I'll add it to the CG.
Yes! That is very cool. Somehow t
On Mon, Oct 12, 2009 at 1:59 PM, Carl Sorensen wrote:
>
>
>
> On 10/12/09 1:41 PM, "Andrew Hawryluk" wrote:
>
>> Attached is the output of LilyPond 2.7, which was benchmarked as a
>> near match against Baerenreiter BA320. The current beam positions do
>&g
Attached is the output of LilyPond 2.7, which was benchmarked as a
near match against Baerenreiter BA320. The current beam positions do
not match: the stems are now shorter, on average. (The third measure
also has a beaming error of another kind: the first two beats should
be grouped separately fro
On Mon, Apr 27, 2009 at 1:51 PM, Marc Hohl wrote:
> Pekka Siponen schrieb:
>>
>> For chords I don't think there is a standard approach. Chords haven't been
>> around long enough. I was hoping to collect opinions here. :) Maybe the best
>> source would be in some typography book? I checked mine and
ically fixed.
>
>
> You only need to modify text in the body of the documentation, including any
> examples that are inline in the docs.
>
> Carl
>
>
Here's the new version with the documentation change.
Andrew
From 404d16892a75df797f0f5c4f893ccbf3fd5b08ec Mon Sep 1
Attached is my fix for bug #729 and a convert-ly rule.
http://code.google.com/p/lilypond/issues/detail?id=729
If I can keep finding bugs that simple, I'll be sending patches weekly!
Andrew
From 2311c16f64a21247017cd0dafca5a177f676e506 Mon Sep 17 00:00:00 2001
From: Andrew Hawryluk
Date: Fr
The r16 in this example should appear in the lower staff ("PrimoLH"),
but the cross-staff beaming forces it to float above the system.
Andrew
\version "2.12.1"
Iup = \change Staff = "PrimoRH"
Idown = \change Staff = "PrimoLH"
\relative c'' <<
\new PianoStaff <<
\new Staff = "PrimoRH" {
This may be another manifestation of bug #570:
http://code.google.com/p/lilypond/issues/detail?id=570
On Mon, Nov 10, 2008 at 7:25 AM, Bailey James E.
<[EMAIL PROTECTED]> wrote:
> I don't know how fermatas are placed by default, but it would be nice if
> ties and fermatas didn't collide by default
¿Podrías decribir el problems un poco más específicamente?
Tambien existe un grupo de usuarios de LilyPond en español:
http://es.groups.yahoo.com/group/lilypond-es/
Andrew
On Thu, Oct 23, 2008 at 1:26 PM, Gracia <[EMAIL PROTECTED]> wrote:
> No me funciona el lilypond en linux, que hago?
>
>
>
>
ck <[EMAIL PROTECTED]> wrote:
> Hi Andrew,
>
> 2008/10/20 Andrew Hawryluk <[EMAIL PROTECTED]>:
>> I'm not upgrading my copy of Finale this year, so I'd like to
>> contribute some cash to fixing bugs 379 and 427:
>> http://code.google.com/p/lilypond/issue
I'm not upgrading my copy of Finale this year, so I'd like to
contribute some cash to fixing bugs 379 and 427:
http://code.google.com/p/lilypond/issues/detail?id=379
http://code.google.com/p/lilypond/issues/detail?id=427
All it will take is getting slurs that cross a line break to begin
after the
On Tue, Aug 19, 2008 at 4:03 AM, Valentin Villenave
<[EMAIL PROTECTED]> wrote:
> 2008/8/12 Martin Klejch <[EMAIL PROTECTED]>:
>
>> %% the "Lyrics independent of notes" example (chapter 7.3.7.5 of the manual)
>> %% gives errors: warning: Lyric syllable does not have note. Use \lyricsto
>> %% or asso
On Wed, Jul 2, 2008 at 11:04 PM, George_ <[EMAIL PROTECTED]> wrote:
>
> Basically, my problem is this - I want to typeset this chord:
> 4.
>
> And this is what I get:
> http://www.nabble.com/file/p18251902/1.jpg
>
> Because the notes of the chord are so close together and there are so many
> of the
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
>> modifi
Example is attached. Should I add this to the bug tracker, or is that
Valentin's territory?
Andrew
On Mon, May 19, 2008 at 9:58 AM, <[EMAIL PROTECTED]> wrote:
> Issue 427: ugly collision slur and phrasing slur
> http://code.google.com/p/lilypond/issues/detail?id=427
>
> Comment #3 by hanwenn:
>
When a slur crosses a line break, the slur after the break begins
before the key signature. Phrasing slurs, on the other hand, begin
after the key signature. (This is not clear in any of the regression
tests because the slur examples are all in C major.) I know that this
sort of question has come u
Why is only the first mark shifted upward? Is it a bug in the program
or the user? :)
Andrew
\version "2.11.42"
\paper {ragged-right = ##t}
\relative c' {
c c c c
\once \override Score.RehearsalMark #'padding = #5
\mark \markup Markup
c c c c
\once \overrid
I wrote out an organ accompaniment in LilyPond (to get it onto 4 pages
instead of 13), and it illustrates this situation very well. In eight
separate places there was a major or minor second between a dotted and
undotted note, with the dotted note on a staff space - exactly the
condition that produ
Given the right note spacing and tie directions, ties can collide with
rhythmic augmentation dots. In this example, if the line width is
reduced to 52 LilyPond avoids the collision. Increasing the line width
reduces the severity of the collision by reducing the initial slope of
the tie. (Bug found
Sorry for the vague subject line. Hopefully the picture helps...
\version "2.11.41"
\paper {
ragged-right = ##f
}
<<
{g'4 s2. g'4 s2.} \\
{g'2 s2 g'2. s4}
>>
When the same note appears simultaneously in two voices and the
noteheads are different, they should appear right
True. This has been tagged as bug 570:
http://code.google.com/p/lilypond/issues/detail?id=570
The work around is to increase the padding around the script object
(see LM 4.5.2).
Andrew
On 2/27/08, Thomas Scharkowski <[EMAIL PROTECTED]> wrote:
> Tie an d accent collide.
> --
> \version "2.11.41"
That's great!
"...the bug reporter hadn't realized this fine detail when he wanted
to change the alignment point"
Exactly. Once explained it makes sense. Thanks again!
Andrew
On Fri, Feb 15, 2008 at 8:56 AM, Mats Bengtsson
<[EMAIL PROTECTED]> wrote:
>
>
> [EMAIL PROTECTED] wrote:
> > Issue 579:
This one has me stumped. The initial tempo mark of a piece
should be left-aligned with the time signature. If I comment out the
second Staff context in this example then the alignment is perfect,
but when both staffs are present it shifts the mark to the right
somewhat. (See attached images.)
Any
On Ubuntu, the simplest method is to right-click, go into properties
and under the permissions tab click 'enable execution'. The file can
then be double-clicked to run the install script. I don't know if
Kubuntu is set up exactly the same, though.
Andrew
On Feb 4, 2008 4:38 PM, Jack K Blackhall <
This one's a bit long for a bug report, but only to show the way the
horizontal problem depends on the vertical location of the grace
notes.
-AH
\version "2.11.38"
\paper {
ragged-right = ##t
}
% In groups of grace notes below the staff, it appears
% that the notes are only given enough
I couldn't find this one on the bug list: articulations can collide with ties.
\version "2.11.38"
\paper {
ragged-right = ##t
}
\relative c'' {
f-- f~-- f~
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailma
están disponbiles en
inglés, francés, alemań, y español:
http://lilypond.org/doc/v2.11/Documentation/index.es.html
Si tienes preguntas generales, la mejor lista de correos será
[EMAIL PROTECTED] Ellos pueden ayudar mucho, particularmente si
la pregunta es específica. !Suerte¡
-Andrew Hawryluk
:20: warning: programming error: Spanner `Hairpin' is
not fully contained in parent spanner. Ignoring orphaned part
c1\< R1\! c1
\< \break R1\!
Cheers,
Andrew Hawryluk
___
bug-lilypond mailing list
bug-lilypond@gnu
31 matches
Mail list logo
