bug-lilypond
[Top][All Lists]
Advanced

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

Re: [BUG] Problems in gregorian style lyrics with combination of episem


From: James Lowe
Subject: Re: [BUG] Problems in gregorian style lyrics with combination of episem and melisma
Date: Tue, 17 Jul 2018 16:04:55 +0100 (BST)

Hello,

On Sun, 15 Jul 2018 08:59:01 +0200, "Jaap de Wolff" <address@hidden> wrote:

> Hello,
> 
> About a week ago I did sent the bug report below.
> There was a comment on it on which I replied.
> At this moment it is still not on the bug list, while younger reports are.
> No one told me it was not a proper bug report, or it was not accepted.
> Possible it was not clear that it was intended to be a bug report, so I do
> send it again.
> 
> Jaap de Wolff

> 
> 
> Van: Jaap de Wolff <address@hidden> 
> Verzonden: maandag 9 juli 2018 13:30
> Aan: 'address@hidden' <address@hidden>
> Onderwerp: Problems in gregorian style lyrics with combination of episem and
> melisma 
> 
> In gregorian lyrics the combination of episem with melisma must follow a
> strict order:
> 
> \episemInitium \melisma xxx \episemFinis \melismaEnd  is the only working
> order
> 
> The orders 
> 
> \episemInitium \melisma xxx \melismaEnd \episemFinis 
> 
> \melisma \episemInitium xxx \melismaEnd \episemFinis 
> 
> \melisma \episemInitium xxx \episemFinis \melismaEnd 
> 
> will result in an  unexpected EVENT_IDENTIFIER error
> 
> ===============================
> 
> \version "2.19.62"
> 
> \include "gregorian.ly"
> 
> \new VaticanaVoice {
> 
>   a  \melisma \episemInitium g \melismaEnd \episemFinis 
> 
> }
> 
> ===============================
> 
> Result in error:
> 
> syntax error, unexpected EVENT_IDENTIFIER
>   a  \melisma 
>               \episemInitium g \melismaEnd \episemFinis
> 
> The expected behaviour is that any order is accepted.
> 
> Cheers,
> 
> Jaap


I suppose that it would be helpful if there are any other Ancient Music 
afficionadoes on the list that can comment if 'any order' is really expected to 
work or if this is not just a 'better documentation' issue.

@Jaap

Are there any other valid combinations that *do* work apart from the one you 
gave?

It may give the developers more to work with.

Thank you.

James



reply via email to

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