On Thu, Mar 22, 2012 at 8:03 PM, Jean-Charles Malahieude
wrote:
> Le 22/03/2012 13:00, Janek Warchoł disait :
>>
>> On Thu, Mar 22, 2012 at 12:37 PM, Francisco Vila wrote:
>>> Melismas are indicated in the score by slurs, so slur
>>> equals melisma.
>>
>> Not always. Sometimes they're also used
Le 22/03/2012 20:20, Jean-Charles Malahieude disait :
Le 22/03/2012 20:08, David Kastrup disait :
Jean-Charles Malahieude writes:
The main problem in this case, in my opinion, is that you can't even
build a shortcut for combining melisma and autobeaming, since beaming
is *prefix* and melisma *
Le 22/03/2012 20:08, David Kastrup disait :
Jean-Charles Malahieude writes:
The main problem in this case, in my opinion, is that you can't even
build a shortcut for combining melisma and autobeaming, since beaming
is *prefix* and melisma *postfix*.
Beaming is prefix?
just tried :
mbY =
Jean-Charles Malahieude writes:
> The main problem in this case, in my opinion, is that you can't even
> build a shortcut for combining melisma and autobeaming, since beaming
> is *prefix* and melisma *postfix*.
Beaming is prefix?
--
David Kastrup
Le 22/03/2012 13:00, Janek Warchoł disait :
On Thu, Mar 22, 2012 at 12:37 PM, Francisco Vila wrote:
2012/3/22 Janek Warchoł:
What i suggest would be quite the opposite: every melisma should be
indicated using a melisma command, and *then* user can decide how he
wants melismas to look like: sho
2012/3/22 Janek Warchoł :
> well, we don't have a \slur and \slurEnd commands. Aslo, melismas
> appear so often that i think the syntax should be standarized.
> But i'm not at all against having both full name and shortcut,
> similarly to -\staccato and -.
Totally agreed.
--
Francisco Vila. Bad
On Thu, Mar 22, 2012 at 12:37 PM, Francisco Vila wrote:
> 2012/3/22 Janek Warchoł :
>> What i suggest would be quite the opposite: every melisma should be
>> indicated using a melisma command, and *then* user can decide how he
>> wants melismas to look like: should every melisma be automatically
>
2012/3/22 Janek Warchoł :
> The current behavior is bad, because it mixes two different things:
> melismas themselves and how they are represented. If i use either slurs or
> manual beams for melismas, i'm hardcoding some redundant (or at least
> partially redundant) information into my source fil
Moving from -user.
On Wed, Mar 21, 2012 at 1:50 PM, Kieren MacMillan
wrote:
> Here's my opinion:
>
> 1. The default auto-beaming should produce scores which represent
> the current best practice in the engraving industry, which is to ignore lyrics
> (inside and outside melismas) and beam as if it