Hello,
Lilypond is great! I just have one problem I can't resolve:
I would like to change Stereo Position of Staves in Midi-Output:
For Example:
Soprano: Left
Alto: Right
Is there any way to achieve this (besides manual editing of the midi-Output)?
___
On 2010/03/15 09:53:31, marc wrote:
> http://codereview.appspot.com/224082/diff/1012/19
> File ly/chord-repetition-init.ly (right):
>
> http://codereview.appspot.com/224082/diff/1012/19#newcode71
> ly/chord-repetition-init.ly:71: (make-repeat-chord-function '()
'()))
> indent
>
> #(define
>
On Tue, 2010-03-16 at 15:46 +0100, Reinhold Kainhofer wrote:
> In the Figured_bass_engraver, I have a BassFigureAlignment spanner, where
> Align_interface::add_element is used to append new figures. However, with
> extenders turned on, it happens frequently that a new figure needs to be
> insert
On Tue, Mar 16, 2010 at 5:42 PM, Trevor Daniels wrote:
>
> Both look fine in html, and Hebrew also looks fine
> (AFAICT) in pdf, but the Cyrillic is missing in the
> pdf.
...
> it
> seems like documenting this in pdf would be problematic
> unless the missing Cyrillic in pdf can be understood and
>
David Kastrup wrote Tuesday, March 16, 2010 5:02 PM
Mark Polesky writes:
Carl Sorensen wrote:
I'm OK with that, but I still have the concern of
documenting it. What do we need to do to make sure that
the documentation works properly?
I don't think it's worth it. There are too many
docu
James Bailey writes:
> On 16.03.2010, at 18:02, David Kastrup wrote:
>
>> Mark Polesky writes:
>>
>>> Not sure if the gitk issue translates to any real problem,
>>> but the first two are obvious non-starters. I've attached
>>> some images to demonstrate.
>>
>> We will get into trouble with docu
David Kastrup gnu.org> writes:
>
> We will get into trouble with documenting Hebrew lyrics and other things
> at one time then, I guess.
>
Perhaps, but the Hebrew examples work just fine on my system; I haven't done
anything special to make them work.
Thanks,
Carl
__
On 16.03.2010, at 18:02, David Kastrup wrote:
Mark Polesky writes:
Carl Sorensen wrote:
I'm OK with that, but I still have the concern of
documenting it. What do we need to do to make sure that
the documentation works properly?
I don't think it's worth it. There are too many
documentati
Am Freitag, 12. März 2010 14:41:20 schrieb Reinhold Kainhofer:
> Our problems with \RemoveEmptyStaffContext resetting previous context
> modifications highlights one problem we have: So far, it was not possible
> to store a bunch of context modifications into a variable and apply them
> later on.
Mark Polesky writes:
> Carl Sorensen wrote:
>> I'm OK with that, but I still have the concern of
>> documenting it. What do we need to do to make sure that
>> the documentation works properly?
>
> I don't think it's worth it. There are too many
> documentation issues. I made a tiny change to
>
Carl Sorensen wrote:
> I'm OK with that, but I still have the concern of
> documenting it. What do we need to do to make sure that
> the documentation works properly?
I don't think it's worth it. There are too many
documentation issues. I made a tiny change to
tutorial.itely as a test; I just p
In the Figured_bass_engraver, I have a BassFigureAlignment spanner, where
Align_interface::add_element is used to append new figures. However, with
extenders turned on, it happens frequently that a new figure needs to be
inserted into the spanner at some fixed position (e.g. the beginning).
AF
Werner LEMBERG writes:
>>> I'm not a big fan of moving in this direction; your emails with
>>> unicode included don't render properly on my email client.
>>
>> Nor mine. So I can't even understand the point you are trying
>> to make.
>
> Actually, I like David's patch.
Me too (although I pro
Werner LEMBERG writes:
For selfdescribing glyphs, is the following somewhat defensive
approach sensible, or should 𝄞 be equivalent to the whole \clef
"G" sequence?
If the latter, it would need modifying the parser, right? That
would have the advantage that note leng
14 matches
Mail list logo
