On 31/08/14 11:36, Pierre Perol-Schneider wrote:
> Nice ! Plus it's also working for time changes issue :
>
> \version "2.19"
>
> \markup\italic "Ossia staff's too long at time change:"
>
> \new Staff = "main" \relative c'' {
> c4 b d c
> <<
> { c4 b d c }
> \new Staff \with {
>
On 13/09/14 20:13, Dan Eble wrote:
>> I'm not top posting.
> % warning: (De)crescendo with unspecified starting volume in MIDI.
> %
> % In 2.16, both of these scores trigger the warning.
> %
> % In 2.18, only the first scrore triggers the warning. The
> % inconsistency does not seem right; the sta
On 15/09/14 22:56, Knute Snortum wrote:
>> I'm not top posting
>
> The section on the 2.18 version of OttavaBracket...
>
> http://www.lilypond.org/doc/v2.18/Documentation/internals/ottavabracket
>
> ...looks like this:
>
> dash-fraction (number):
> 0.3
> Size of the dashes, relative t
No longer baffling :-) Using the min-systems-per-page option forced LP to
put the systems on the same page and it is clear, when it does so, why its
default fitting algorithm does not! It appears to be the non-musical
elements that are interfering with things. I still had to play with
margins, etc.
Simon,
Thanks for the reply. I apologize for forgetting to rename the "bad" pdf
before futzing with the margins to get the piece back to two systems per
page. You have provided me another option which I will explore. Here is
link to how the piece looks with the original margins:
https://www.drop
>I'm not top posting
The section on the 2.18 version of OttavaBracket...
http://www.lilypond.org/doc/v2.18/Documentation/internals/ottavabracket
...looks like this:
dash-fraction (number):
0.3
Size of the dashes, relative to dash-period. Should be between 0.0 (no
line) and 1.0 (contin
Am 15.09.2014 um 21:41 schrieb Guy Stalnaker:
All,
Sometimes Lilypond changes how it does its "Fitting music on ..."
calculations when it decides what can fit on a page and what cannot.
In this case, after four pages on which the "fitting" process puts two
systems per page, the subsequent pa
All,
Sometimes Lilypond changes how it does its "Fitting music on ..."
calculations when it decides what can fit on a page and what cannot. In
this case, after four pages on which the "fitting" process puts two
systems per page, the subsequent pages *all* have only one system per
page--even t
pls writes:
> Hey all,
>
> there seems to be a bug in LilyPond 2.19.14: in the following example
> the composer is center-aligned instead of right-aligned:
>
> \version "2.19.14"
>
> \header {
> composer = "composer"
> }
>
> \score {
> c'1
> }
Current branch: issue4102
Tracker issue: 4102 (h
2014-09-15 18:06 GMT+02:00 Jakob Schöttl :
>
> Assuming that the english version is correct, here the fixed german version.
Applied in my tree and testing compile. Will push if it succeeds and
will be visible after some paperwork.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbada
> Am 15.09.2014 um 16:48 schrieb Francisco Vila:
>
>> 2014-09-15 16:40 GMT+02:00 Jakob Schöttl :
>>>
>>> Wrong translation for the description of "list" type:
>>>
>>>
>>> http://www.lilypond.org/doc/v2.18/Documentation/learning/types-of-properties.de.html
>>>
Eine eingeklammerte Anzahl von Ein
2014-09-15 16:40 GMT+02:00 Jakob Schöttl :
> Wrong translation for the description of "list" type:
>
> http://www.lilypond.org/doc/v2.18/Documentation/learning/types-of-properties.de.html
>
>> Eine eingeklammerte Anzahl von Einträgen, mit Klammern getrennt und
>> angeführt von einem Apostroph
>
>
>
Wrong translation for the description of "list" type:
http://www.lilypond.org/doc/v2.18/Documentation/learning/types-of-properties.de.html
Eine eingeklammerte Anzahl von Einträgen, mit Klammern getrennt und
angeführt von einem Apostroph
It's space-separeted, not paren-separeted.
_
13 matches
Mail list logo
