Hi,
Restarting the staff during the lifespan of a multisystem
DynamicLineSpanner destroys the value of DynamicLineSpanner properties
(like staff-padding) that were set when the DynamicLineSpanner was created.
In the MWE below, the hairpin should exhibit staff-padding equal to 10
staff spaces
> On 6 Mar 2019, at 04:20, Austin Blaser wrote:
>
> Regarding the iOS App Store: Oh yeah I forgot about the licensing: definitely
> a potential deal breaker.
Isn't it enough to distribute the sources along with the app, as with Stockfish
https://stockfishchess.org/download/
On 3/6/2019 12:02 PM, AKSHITA TYAGI wrote:
What I think is that it should work on more languages. Like India,
Chinese etc these are the countries that are really found of music and
use of Lilypond would increase if it is available in more languages.
More translations sounds like a welcome
Hi,
I have been studying about Lilypond and it seems to be a very good program.
But it work for only a limited number of languages.
What I think is that it should work on more languages. Like India, Chinese
etc these are the countries that are really found of music and use of
Lilypond would
Hi Aaron
On Wed, Mar 6, 2019 at 4:11 PM Aaron Hill wrote:
>
> The bug would seem to be that LilyPond is not allowed to increase the
> length of a stem to accommodate StemTremolo grobs with notes that are
> beamed. Or perhaps, it is allowed but is failing to do so. Either way,
> the code that
On 2019-03-06 6:24 am, David Kastrup wrote:
Aaron Hill writes:
On 2019-03-06 4:15 am, N. Andrew Walsh wrote:
Hi Aaron,
here's another example that causes the error:
\version "2.19.82"
\relative c'' {
\time 4/16
gis'32[ e c a \repeat tremolo 8 { fis64] }
}
Again, it seems related to
Aaron Hill writes:
> On 2019-03-06 4:15 am, N. Andrew Walsh wrote:
>> Hi Aaron,
>>
>> here's another example that causes the error:
>>
>> \version "2.19.82"
>>
>> \relative c'' {
>> \time 4/16
>> gis'32[ e c a \repeat tremolo 8 { fis64] }
>> }
>>
>> Again, it seems related to collisions
On 2019-03-06 4:15 am, N. Andrew Walsh wrote:
Hi Aaron,
here's another example that causes the error:
\version "2.19.82"
\relative c'' {
\time 4/16
gis'32[ e c a \repeat tremolo 8 { fis64] }
}
Again, it seems related to collisions between beams and tremolo glyphs.
But
here, the
Hi Aaron,
here's another example that causes the error:
\version "2.19.82"
\relative c'' {
\time 4/16
gis'32[ e c a \repeat tremolo 8 { fis64] }
}
Again, it seems related to collisions between beams and tremolo glyphs. But
here, the 32nd-notes should force the bottom beam low enough that
Hi Aaron
On Wed, Mar 6, 2019 at 11:51 AM Aaron Hill wrote:
> >
> > \mark produces RehearsalMark grobs. These are usually at the \Score
> > level, so you can either \override where you use \mark, or you can do
> > it within \layout:
> >
> >
> > \version "2.19.82"
> > \layout { \context {
On 2019-03-06 2:48 am, Aaron Hill wrote:
On 2019-03-06 2:37 am, N. Andrew Walsh wrote:
Hi List,
also on this issue (I still have Roman numerals, which works fine for
me):
is there a way to format the size/weight of the "\mark \default"
character?
Mine aren't much larger than regular text
On 2019-03-06 2:37 am, N. Andrew Walsh wrote:
Hi List,
also on this issue (I still have Roman numerals, which works fine for
me):
is there a way to format the size/weight of the "\mark \default"
character?
Mine aren't much larger than regular text markups, and I'd like to have
some control
Hi List,
also on this issue (I still have Roman numerals, which works fine for me):
is there a way to format the size/weight of the "\mark \default" character?
Mine aren't much larger than regular text markups, and I'd like to have
some control over the presentation.
Cheers,
A
On Wed, Oct 24,
13 matches
Mail list logo
