[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 1971 in lilypond: Slashed flags no longer work

From: address@hidden
Subject: Re: Issue 1971 in lilypond: Slashed flags no longer work
Date: Mon, 17 Oct 2011 08:22:54 +0200

On Oct 17, 2011, at 12:43 AM, Graham Percival wrote:

> On Sun, Oct 16, 2011 at 11:02:22PM +0200, address@hidden wrote:
>> I think that by running convert-ly via the script in 10.9.4,
>> duplicate Flag #'transparent statements will be issued (every
>> time convert-ly sees a Stem #'transparent, it adds a Flag
>> #'transparent for files created before the existence of a Flag
>> grob).
> ok, so you think there's a bug in convert-ly ?  This is not
> precisely shocking news; let's get a Tiny example and add it to
> the tracker, or...

I think that there is an issue with file-touchability.  Certain snippets in the 
docs are not editable, and the convert-ly rules don't know how to handle this 

With respect to the current issue:

All Flag properties were changed in the docs save the files that have a comment 
saying "Do not change me" because they are part of the LSR.  There was also one 
issue with cary.ly that I just fixed.
All of these files that belong to the LSR are the ones that are causing the 
problem (i.e. the file in the bug report).

So, as I said in my e-mail to Phil, I'm not sure how to proceed w/ fixing this 
and how convert-ly would enter into the equation.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]