This looks right to me, and since nobody has come up with any
better names, let's go with bracketed/quoted/bare.
Unless we want to call the first one "curly text". ;)
Cheers,
- Graham
On Fri, 23 May 2008 21:19:56 +0100
"Trevor Daniels" <[EMAIL PROTECTED]> wrote:
>
> So, in summary, might we have something like this?
>
> Entering text
>
> Text may be entered in three ways:
> o delimited by curly brackets, let's call this "bracketed text"
> o delimited by double quotes, let's call this "quoted text"
> o delimited by spaces, let's call this "bare text"
>
> but there are restrictions on each of these:
>
> o Bracketed text is only valid when preceded by \markup,
> but can contain other commands and even quoted text
> o Quoted text cannot contain other commands, but can
> contain special characters which will be interpreted
> literally as simple characters
> o Bare text must be a single word containing only
> alphabetic characters
> o More?
>
> The \markup command will accept all three forms, and these
> illustrate the increasing facilities available:
> o \markup accelerando
> o \markup "gradually speeding up"
> o \markup {\italic {poco a poco stringendo}}
>
> Other commands are more selective. For example, text for
> ottava brackets can only be entered as quoted text.
>
> etc
>
> Trevor
>
> ----- Original Message -----
> From: "John Mandereau" <[EMAIL PROTECTED]>
> To: "Mats Bengtsson" <[EMAIL PROTECTED]>
> Cc: "lily-devel" <[email protected]>
> Sent: Friday, May 23, 2008 9:43 AM
> Subject: Re: Quoted text (was Re: When is "-" required in
> articulations?)
>
>
> > On 2008/05/23, Mats Bengtsson wrote:
> >> Graham Percival wrote:
> >> >
> >> > *as far as I know*, anything in lilypond that accepts "blah blah"
> >> > also accepts \markup.
> >> >
> >> This is almost true. However, I seem to recall a few exceptions.
> >> For example, you
> >> cannot use a \markup expression as the value when you set a
> >> property in \lyricmode.
> >
> > There is another exception: text for ottava brackets
> > (Staff.ottavation property) can only be a string, not a markup. I
> > guess it should be easy to make it accept a markup, though.
> >
> > Cheers,
> > John
> >
> >
> >
> > _______________________________________________
> > lilypond-devel mailing list
> > [email protected]
> > http://lists.gnu.org/mailman/listinfo/lilypond-devel
> >
>
>
> _______________________________________________
> lilypond-devel mailing list
> [email protected]
> http://lists.gnu.org/mailman/listinfo/lilypond-devel
_______________________________________________
lilypond-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
