Shouldn't be barline numbers larger by default so the choir and
orchestra could read them more easily. I know you can change the barline
number font and size as you want but is there any engraver rule about
how big the barline numbers should actually be or is it just a matter of
taste? IMO, the cur
Hello Lily developers,
I'm writing/extending the LilyPond parser for Canorus. The idea (as
mentioned a few times before on Canorus and LilyPond MLs) is to have a
built-in capabilities in Canorus for editing the current score in
LilyPond syntax as well as importing the external LilyPond file of
cou
Let's have a staff with two voices. The first one has \voiceOne flag set
and the other one \voiceTwo. This way, stem positions are right, etc.
The problem happens when the second voice has invisible rests and the
first voice has visible ones (and this happens many times). The vertical
position of
Graham Percival pravi:
> Han-Wen Nienhuys wrote:
>> Jonathan Henkelman escreveu:
>
>>> I think Eriks point is actually well founded. The discussion
>>> started with my discussion of trying to trim down the grammer
>>> complexity. Adding syntax is not really in that direction.
>>
>> Another option:
gt; ius -- tus, et ne -- mo per -- % 7
>>> ci pit cor -- de et % 10
>>> ne -- mo per -- ci -- pit cor -- % 12
>>> de; vi -- ri ius -- % 14
>>> ti tol -- lun -- tur, et % 16
>>>
Hello,
I'm very excited about the new vertical collision avoiding code in
Lily-2.11.0 - it's something I've been waiting from 2.2. version on (I
had to always set vertical text-padding value manually) :). I have some
question about its implementation and usage:
1) Does this patch removes text coll
Canorus is still in alpha phase. Version 1.0 is planned for the end of
the next year and should implement all of the NoteEdit features. Many
exotic features are there though (like multiple viewports on the same
score, scripting language and plugins support, support for harmonic
function markings, Q
