On Tue, Sep 11, 2012 at 10:12 AM, Janne Uusitalo
wrote:
> On Sat, Sep 8, 2012 at 1:03 AM, Thomas Morley
> wrote:
>
at the end of a line I'd change the order in which KeyCancellation and
KeySignature appears. This requires some new settings in KeySignature
>
> Thanks for this suggestion
Hi,
On Sat, Sep 8, 2012 at 1:03 AM, Thomas Morley
wrote:
>>> at the end of a line I'd change the order in which KeyCancellation and
>>> KeySignature appears. This requires some new settings in KeySignature
>>> 'space-alist and BreakAlignment 'break-align-orders.
Thanks for this suggestion. I ap
2012/9/7 David Kastrup :
> Thomas Morley writes:
>
>> 2012/9/6 Janne Uusitalo :
>>> Hi,
>>>
>>> if I typeset a key change from b major to g major, f remains sharp and
>>> LilyPond prints out the naturals necessary for c, g, d, and a. Makes
>>> perfect sense, but the standard I'm required to follow
Thomas Morley writes:
> 2012/9/6 Janne Uusitalo :
>> Hi,
>>
>> if I typeset a key change from b major to g major, f remains sharp and
>> LilyPond prints out the naturals necessary for c, g, d, and a. Makes
>> perfect sense, but the standard I'm required to follow has it that an
>> extra # for fis
2012/9/6 Janne Uusitalo :
> Hi,
>
> if I typeset a key change from b major to g major, f remains sharp and
> LilyPond prints out the naturals necessary for c, g, d, and a. Makes
> perfect sense, but the standard I'm required to follow has it that an
> extra # for fis should precede the group of nat
Hi,
if I typeset a key change from b major to g major, f remains sharp and
LilyPond prints out the naturals necessary for c, g, d, and a. Makes
perfect sense, but the standard I'm required to follow has it that an
extra # for fis should precede the group of naturals. Is there a way
to achieve this
