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.
Examples
\header{ title = \markup{...} }
\property Staff.instrument = \markup{...}
\lyricsmode{ Here is a flat sym -- bol: \markup{\flat } }
\mark \markup{...}
c4^\markup{...}
/Mats
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{}.
Cheers,
- Graham
_______________________________________________
lilypond-devel mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/lilypond-devel
--
=============================================
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260
Email: address@hidden
WWW: http://www.s3.kth.se/~mabe
=============================================