Comment #4 on issue 1127 by lemzw...@gmail.com: Piano staff centred dynamics
http://code.google.com/p/lilypond/issues/detail?id=1127
The example in the last comment is extreme IMHO, but it points into the
right direction. Let me formulate a possible algorithm slightly
differently:
1. In t
On 11-10-19 09:45 AM, Patrick Schmidt wrote:
Hey all,
The value 'none' of the element 'group-symbol'
(none) leads to a bus error when the converted
.ly-file is compiled with LilyPond v2.15.14. The compilation fails. There is no problem
with the conversion and compilation of the other group-sy
On 11-10-21 11:00 AM, Reinhold Kainhofer wrote:
Am Thursday, 20. October 2011, 12:15:10 schrieb pls:
Compilation with LilyPond v2.15.14 fails when an element of the score
header of a converted MusicXML-file contained a single word directly
followed by a punctuation mark (I tested it with '.', '!
Status: Accepted
Owner:
Labels: Type-Scripts
New issue 1983 by colinpkc...@gmail.com: musicxml2ly: single words with
punctuation marks in score header lead to compilation failure
http://code.google.com/p/lilypond/issues/detail?id=1983
From bug-lilypond:
Am Thursday, 20. October 2011,
Comment #3 on issue 1127 by ahawry...@gmail.com: Piano staff centred
dynamics
http://code.google.com/p/lilypond/issues/detail?id=1127
Attached is a hand-engraved example of centred dynamics from a piano score
[1]. The individual dynamic marks are centred between the skylines by
shifting t
On Fri, Oct 21, 2011 at 01:58:41PM -0700, -Eluze wrote:
>
> sorry to insist on this topic - but since i could not find any documentation
> about my approach i would like to make sure it will last longer (at least it
> was also working with 2.12.3).
I haven't been following the discussion, but the
"-Eluze" wrote in message
news:32699086.p...@talk.nabble.com...
Phil Holmes-2 wrote:
This looks to me like correct behaviour. You've created extra Lyrics
contexts, and Lilypond stacks them one above the other. This is as
illustrated in the NR. If I was doing what you're showing, I would
Phil Holmes-2 wrote:
>
>
> This looks to me like correct behaviour. You've created extra Lyrics
> contexts, and Lilypond stacks them one above the other. This is as
> illustrated in the NR. If I was doing what you're showing, I would use …
>
hi Phil
sorry to insist on this topic - but s
Am Thursday, 20. October 2011, 12:15:10 schrieb pls:
> Compilation with LilyPond v2.15.14 fails when an element of the score
> header of a converted MusicXML-file contained a single word directly
> followed by a punctuation mark (I tested it with '.', '!', ','. There is
> no problem with question m
Am Wednesday, 19. October 2011, 17:45:23 schrieb Patrick Schmidt:
> Hey all,
>
> The value 'none' of the element 'group-symbol'
> (none) leads to a bus error when the
> converted .ly-file is compiled with LilyPond v2.15.14. The compilation
> fails. There is no problem with the conversion and compi
Comment #1 on issue 1982 by d...@gnu.org: Patch: Allow more argument types,
interpret optional argument predicates syntactically.
http://code.google.com/p/lilypond/issues/detail?id=1982#c1
Allow more argument types, interpret optional argument predicates
syntactically.
This is a patch ser
Am 21.10.2011 um 17:51 schrieb David Kastrup:
> Neil Puttock writes:
>
>> On 21 October 2011 16:24, pls wrote:
>>
>>> It's not that it isn't documented. I found it eventually but it's
>>> neither included here
>>>
>>> http://lilypond.org/doc/v2.15/Documentation/notation/lilypond-command-inde
On Fri, Oct 21, 2011 at 5:03 PM, Neil Puttock wrote:
> On 21 October 2011 16:51, David Kastrup wrote:
>
>> Wouldn't it make more sense to have the index entries escaped, but
>> sorted under the respective first letter instead of \ ?
>
> Sounds eminently sensible to me. :)
>
http://code.google.co
commit 1d9a73b13ee576d28c0f41f5b243f2ebb1ff9fcf
Author: Mike Solomon
Date: Fri Oct 21 09:03:43 2011 +0200
Implements consistent beam slopes across line breaks.
says
To turn on this feature, use \override Beam #'consistent-slope = ##t.
I think that is a mistake: unbroken beams natura
On 21 October 2011 16:51, David Kastrup wrote:
> Wouldn't it make more sense to have the index entries escaped, but
> sorted under the respective first letter instead of \ ?
Sounds eminently sensible to me. :)
Cheers,
Neil
___
bug-lilypond mailing li
Neil Puttock writes:
> On 21 October 2011 16:24, pls wrote:
>
>> It's not that it isn't documented. I found it eventually but it's
>> neither included here
>>
>> http://lilypond.org/doc/v2.15/Documentation/notation/lilypond-command-index#lilypond-command-index_ky_letter-E
>>
>> nor here
>>
>> ht
On 21 October 2011 16:24, pls wrote:
> It's not that it isn't documented. I found it eventually but it's neither
> included here
>
> http://lilypond.org/doc/v2.15/Documentation/notation/lilypond-command-index#lilypond-command-index_ky_letter-E
>
> nor here
>
> http://lilypond.org/doc/v2.15/Docum
Am 21.10.2011 um 16:58 schrieb Neil Puttock:
> On 21 October 2011 15:48, pls wrote:
>
>> the command \eyeglasses is neither part of the command index nor of the
>> general index.
>
> It's documented automatically as a slashed command in both indices:
>
> http://lilypond.org/doc/v2.15/Documen
On 21 October 2011 15:48, pls wrote:
> the command \eyeglasses is neither part of the command index nor of the
> general index.
It's documented automatically as a slashed command in both indices:
http://lilypond.org/doc/v2.15/Documentation/notation/other#index-_005ceyeglasses
Cheers,
Neil
__
Hey all,
the command \eyeglasses is neither part of the command index nor of the general
index.
hth
patrick
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 1982 by d...@gnu.org: Patch: Allow more argument types, interpret
optional argument predicates syntactically.
http://code.google.com/p/lilypond/issues/detail?id=1982
Allow more argument types, interpret optional argument pre
David Kastrup writes:
> Nick Payne writes:
>
>> This creates the error:
>>
>> \version "2.15.14"
>>
>> \paper {
>> first-page-number = -1
>> }
>>
>> \relative c {
>> c1
>> }
>>
>> Setting first page number to -1 seems to be the problem. In the actual
>> score, I set this, in conjunction
David Kastrup writes:
> Nick Payne writes:
>
>> This creates the error:
>>
>> \version "2.15.14"
>>
>> \paper {
>> first-page-number = -1
>> }
>>
>> \relative c {
>> c1
>> }
>>
>> Setting first page number to -1 seems to be the problem. In the actual
>> score, I set this, in conjunction
Nick Payne writes:
> This creates the error:
>
> \version "2.15.14"
>
> \paper {
> first-page-number = -1
> }
>
> \relative c {
> c1
> }
>
> Setting first page number to -1 seems to be the problem. In the actual
> score, I set this, in conjunction with custom headers and footers, to
> sta
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 1981 by mts...@gmail.com: Patch: Adds Scheme function for spring
constructor.
http://code.google.com/p/lilypond/issues/detail?id=1981
Adds Scheme function for spring constructor.
http://codereview.appspot.com/5306050
Updates:
Labels: -Patch-push fixed_2_15_15
Comment #9 on issue 1952 by tdaniels...@gmail.com: Patch: Sketch for broken
beams with consistent slopes
http://code.google.com/p/lilypond/issues/detail?id=1952
(No comment was entered for this change.)
_
Updates:
Labels: -Patch-countdown fixed_2_15_15
Comment #16 on issue 1951 by tdaniels...@gmail.com: Scripts collide with
accidentals
http://code.google.com/p/lilypond/issues/detail?id=1951
(No comment was entered for this change.)
___
bug-
Updates:
Status: Fixed
Comment #15 on issue 1951 by mts...@gmail.com: Scripts collide with
accidentals
http://code.google.com/p/lilypond/issues/detail?id=1951
Fixed with f1bb461ca8037b12343479b22d56bf96abe238b6
___
bug-lilypond mailing lis
Updates:
Status: Fixed
Comment #8 on issue 1952 by mts...@gmail.com: Patch: Sketch for broken
beams with consistent slopes
http://code.google.com/p/lilypond/issues/detail?id=1952
Implemented with 1d9a73b13ee576d28c0f41f5b243f2ebb1ff9fcf.
_
29 matches
Mail list logo
