Hello David,
why do you think it is too hackish? If it gets lily-standard, all visible to
the user is something like this:
If he wants a non-pre-defined lyric-markup:
lyrcaps = #(define-lyric-markup (markup #:recaps #:fromproperty 'lyric:text))
and then \addlyrics/\lyricmode { sing \lyrcaps { sing sing sing } }
Most of the scheme stuff is to overcome the issue with caps and fromproperty.
It is a workaround to get the desired result in the current stable version.
Cheers,
Jan-Peter
Am 06.10.2011 um 16:12 schrieb David Kastrup:
> Vaughan McAlley <[email protected]> writes:
>
>> On 7 October 2011 00:12, Jan-Peter Voigt <[email protected]> wrote:
>>> Hi Vaughan,
>>>
>>> I introduced the define-lyric-markup method a few mails ago, so it is no
>>> lilypond standard.
>>> Here I added methods to your file and used the recaps command, I introduced
>>> in a revious mail, to capsify markups recursively whatching out for
>>> \fromproperty.
>
>> Thank you! It worked first time! I hope it becomes part of standard
>> Lilypond...
>
> Personally, I think this is far too hackish for a user interface. It
> would make more sense to create a music function that just converts a
> markup list into lyric events, then use \lyricsto or \addlyrics for
> tacking the rhythm on.
>
> --
> David Kastrup
>
>
> _______________________________________________
> lilypond-user mailing list
> [email protected]
> https://lists.gnu.org/mailman/listinfo/lilypond-user
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user
