[Top][All Lists]

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

Re: markup{} vs TextScript

From: Stephen
Subject: Re: markup{} vs TextScript
Date: Wed, 11 May 2005 10:30:03 -0500

Well, I am really just asking whether markup is more than a text script or not. If it would cause less confusion to regularize the terminology than it would to not change it, then it would be a good thing, but I aggree that that would be unlikely.


----- Original Message ----- From: "Mats Bengtsson" <address@hidden>
To: "Graham Percival" <address@hidden>
Cc: "Stephen" <address@hidden>; "lilypond devel" <address@hidden>
Sent: Wednesday, May 11, 2005 4:43 AM
Subject: Re: markup{} vs TextScript

Related to the answer on \mark versus \markup that I just sent,
I don't fully agree on the change below, since \markup can be
used in several different contexts, not just for text scripts.
\header{ title = \markup{...} }

\property Staff.instrument = \markup{...}

\lyricsmode{ Here is a flat sym -- bol: \markup{\flat } }

\mark \markup{...}



Graham Percival wrote:

On 10-May-05, at 10:16 AM, Stephen wrote:

Thinking about it even more, I realise that having a link to TextScript in the programming reference somewhere under 7.4 Text markup instead of just under 5.7.5 Text scripts to make up for the confusion in terminology that Text script and Text markup are two terms that basically describe the same thing.

Thanks, this is a useful report.  Fixed in CVS.

I can (and will) certainly update the docs to reflect this, but would it be possible
to standardize the lilypond internals?  Could "TextScript" be renamed to
"TextMarkup" and "TextScriptEvent" be renamed to "TextMarkupEvent" ?
I think that's a better solution than renaming \markup{} to \script{}.

- Graham

lilypond-devel mailing list

Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
Phone: (+46) 8 790 8463 Fax:   (+46) 8 790 7260
Email: address@hidden

reply via email to

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