Re: What to do when \> and \< produce text

[Reinhold Kainhofer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Mittwoch, 29. Oktober 2008 schrieb George_:
> Well, shouldn't the file be changed for future versions of Lilypond so that
> the \cresc command produces the text crescendo, and the \< \! produces the
> hairpin one? They are separate commands, and in my mind, it seems quite
> logical for the /< to stand for a hairpin and the \cresc to stand for the
> text crescendo. 

Yes, I totally agree, and I was actually thinking about posting that exact 
same proposal. I have some classical scores (Schubert, Mozart, etc.), which 
use both hairpins and text crescendi. Switching is really a pain currently.
So, I would propose:

\>, \< ... Starts a hairpin (de-)crescendo
\cresc ... Starts a text crescendo
\decresc ... Starts a text decrescendo
\dim ... Starts a text diminuendo

This way, the lilypond command would already look like the output is much 
easier to read when cross-checking your score...

All of these would simply be ended by \!. 

Cheers,
Reinhold

- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, Vienna University of Technology, Austria
email: address@hidden, http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/
 * K Desktop Environment, http://www.kde.org, KOrganizer maintainer
 * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFJCOh0TqjEwhXvPN0RAik3AKCKmOyGwvmIMB7V+TIWHWYP+LvLPACeMm4B
sCRrhCM+TqmKkhDLlvQWl3Q=
=YQn0
-----END PGP SIGNATURE-----