lilypond-devel
[Top][All Lists]
Advanced

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

Re: convert-ly for note/rest-markup


From: Carl Sorensen
Subject: Re: convert-ly for note/rest-markup
Date: Thu, 11 Feb 2021 22:32:24 +0000
User-agent: Microsoft-MacOutlook/10.10.1b.201012

Oops -- copying to the list.  Sorry about my mistake.  See below.



On 2/11/21, 3:29 PM, "David Kastrup" <dak@gnu.org> wrote:

    Carl Sorensen <c_sorensen@byu.edu> writes:
    
    > On 2/11/21, 3:15 PM, "lilypond-devel on behalf of David Kastrup"
    > <lilypond-devel-bounces+carl.d.sorensen+digest=gmail.com@gnu.org on
    > behalf of dak@gnu.org> wrote:
    >
    >     Michael Käppler <xmichael-k@web.de> writes:
    >     
    >     >
    >     > AFAICT the parser solves this problem by checking the call 
signature of
    >     > the markup command to
    >     > know how many arguments should be there. (and of which type)
    >     > Since \markup commands are user-definable, I don't have any idea 
how to
    >     > solve this in a general way
    >     > within convert-ly.
    >     >
    >     > Cc'ing David, maybe you have some inspiration for us?
    >     
    >     Short of special-patterning the known exceptions...  a bit of a
    >     nightmare.
    >     
    >
    > This seems to me to be an opportunity to use a NOTSMART conversion
    > rule.  Let the user figure it out.
    
    Are we doing the user a favor by refusing to apply a heuristic that will
    work 90% of the time?

No.  Apply the heuristic, but also use a NOTSMART rule.  Fix it where possible, 
but let the user know that the fix is not guaranteed.

Carl
    


reply via email to

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